Range holder · Bristol
RingGo Limited in Bristol
0117 numbering ranges allocated by Ofcom
About RingGo Limited’s Bristol allocation
When RingGo Limited is the range holder for +44 117 it means Ofcom recorded RingGo Limited as the provider entitled to issue numbers from these blocks when they were first allocated under the UK National Telephone Numbering Plan. 2 Bristol-facing blocks sit against RingGo Limited in the current Ofcom snapshot, each of which can carry up to ten thousand individual digits available for assignment to end customers.
Bristol’s South West telecoms estate is shaped by Bristol's catchment of roughly 467,000 residents: a dense urban exchange typically hosts allocations from several national operators in parallel, which is why you see RingGo Limited’s blocks alongside other range holders on the same 0117 code. Local switching capacity, historic Openreach exchange footprints, and RingGo Limited’s wholesale routing arrangements all influence which blocks land in Bristol 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 0117 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.
RingGo Limited on 0117: by the numbers
- Bristol blocks
- 2
- In active service
- 100%
- Share of 0117
- 0%
- Holders on code
- 160
Of the 2 blocks RingGo Limited runs on the 0117 code, 2 (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 Bristol RingGo Limited number is likely to be before you even dial it back.
RingGo Limited runs 2 of the 2,000 allocated blocks on the 0117 dialling code — roughly 0% of Bristol’s mapped allocation, shared with 159 other range holders. Most are listed as "Allocated", which means the block is currently in active service with a communications provider.
Allocated ranges
RingGo Limited blocks on the 0117 (Bristol) dialling code.
| Prefix | Status |
|---|---|
| +44 117393 | Allocated |
| +44 117393 | Allocated |
Quick links
- RingGo LimitedAll RingGo Limited ranges
- 0117 BristolAll numbers on 0117
- BristolMore on Bristol
- (AQ) LIMITEDAlso allocated on 0117
- 24 Seven Cloud Communications LtdAlso allocated on 0117
- 8x8 UK LimitedAlso allocated on 0117
- RingGo Limited in LeedsRingGo Limited ranges in Leeds
- RingGo Limited in LondonRingGo Limited ranges in London
- RingGo Limited in ManchesterRingGo Limited ranges in Manchester
- All range holdersEvery Ofcom-listed provider
- Lookup any UK numberFree reverse phone lookup
FAQs about RingGo Limited on 0117
Why does RingGo Limited appear on Bristol (0117) numbers?
RingGo Limited is listed in Ofcom's UK Numbering Data feed as the originally-allocated range holder for 2 number blocks on the 0117 dialling code, which covers Bristol. That allocation pre-dates any individual customer — it simply means Ofcom recognised RingGo Limited as the wholesale operator entitled to issue those digits when the block was first allocated.
Are calls from a Bristol RingGo 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 0117 number into the lookup above to combine the RingGo Limited range data with a live AI internet check for forum reports, scam databases, and business listings.
Has RingGo Limited's 0117 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.