Range holder · London

Spitfire Network Services Limited in London

020 numbering ranges allocated by Ofcom

About Spitfire Network Services Limited’s London allocation

When Spitfire Network Services Limited is the range holder for +44 20 it means Ofcom recorded Spitfire Network Services Limited as the provider entitled to issue numbers from these blocks when they were first allocated under the UK National Telephone Numbering Plan. 12 London-facing blocks sit against Spitfire Network Services Limited in the current Ofcom snapshot, each of which can carry up to ten thousand individual digits available for assignment to end customers.

London’s Greater London telecoms estate is shaped by London's catchment of roughly 8,982,000 residents: a dense urban exchange typically hosts allocations from several national operators in parallel, which is why you see Spitfire Network Services Limited’s blocks alongside other range holders on the same 020 code. Local switching capacity, historic Openreach exchange footprints, and Spitfire Network Services Limited’s wholesale routing arrangements all influence which blocks land in London rather than elsewhere on the national plan.

Treat this allocation as a starting point, not a verdict on any specific caller. UK numbers are portable, so the current carrier on a given 020 digit string may differ from the range holder shown — read Range Holder vs current provider for the distinction, and How Ofcom allocates UK phone numbers for the wider context behind the table below.

Spitfire Network Services Limited on 020: by the numbers

London blocks
12
In active service
100%
Share of 020
0%
Holders on code
246

Of the 12 blocks Spitfire Network Services Limited runs on the 020 code, 12 (100%) are marked as actively allocated in the current Ofcom snapshot.

By number family these blocks are 100% geographic (01 / 02) — a profile that tells you what kind of caller a London Spitfire Network Services Limited number is likely to be before you even dial it back.

Spitfire Network Services Limited runs 12 of the 10,402 allocated blocks on the 020 dialling code — roughly 0% of London’s mapped allocation, shared with 245 other range holders. Most are listed as "Allocated", which means the block is currently in active service with a communications provider.

Allocated ranges

Spitfire Network Services Limited blocks on the 020 (London) dialling code.

PrefixStatus
+44 203141Allocated
+44 203141Allocated
+44 203696Allocated
+44 203696Allocated
+44 203848Allocated
+44 203848Allocated
+44 204546Allocated
+44 204546Allocated
+44 207036Allocated
+44 207036Allocated
+44 207042Allocated
+44 207042Allocated

FAQs about Spitfire Network Services Limited on 020

Why does Spitfire Network Services Limited appear on London (020) numbers?

Spitfire Network Services Limited is listed in Ofcom's UK Numbering Data feed as the originally-allocated range holder for 12 number blocks on the 020 dialling code, which covers London. That allocation pre-dates any individual customer — it simply means Ofcom recognised Spitfire Network Services Limited as the wholesale operator entitled to issue those digits when the block was first allocated.

Are calls from a London Spitfire Network Services Limited-allocated number safe?

An Ofcom allocation only tells you which provider the block was issued to; it is not a safety verdict. UK numbers can be ported between networks, and any UK area code can be spoofed by an overseas caller. Paste the specific 020 number into the lookup above to combine the Spitfire Network Services Limited range data with a live AI internet check for forum reports, scam databases, and business listings.

Has Spitfire Network Services Limited's 020 block been updated recently?

Yes — the table above is sourced from Ofcom's public UK Numbering Data feed, which we re-ingest every week (typically Wednesday). Any block that has been re-assigned, withdrawn or marked free will appear with its new status on the next refresh. Numbers within an allocated block can still be ported to another carrier in between Ofcom updates; see our range-holder-vs-current-provider guide for the distinction.