Why does an international code not always identify a country?
E.164 is the public international numbering plan, not only a list of nations. Its current structure covers geographic areas, global services, other global services, global satellite services, networks, groups of countries, trial resources and IoT/M2M services. A leading code can therefore route a call or message towards a service or network whose users move across borders.
This is different from a shared geographic numbering plan. With +1, the following area code distinguishes countries and territories inside the North American Numbering Plan. With +881, the following identification digit distinguishes an assigned satellite network. Neither case can be resolved from the first country-code digits alone, but the administrative structures are different.
Satellite, network and global-service code families
The table describes code categories, not a promise that every origin carrier supports or prices them in the same way. Assignment status can change, so systems that route or classify these ranges should use current ITU data rather than a permanent hard-coded provider list.
| Code | E.164 category | Example use | How to interpret it |
|---|---|---|---|
| +800 | Global service | Universal International Freephone Number (UIFN) | A fixed +800 plus eight-digit subscriber-number structure; access still depends on participating origin networks. |
| +808 | Global service | International shared-cost service | A service code, not the geographic calling code for a country or territory. |
| +870 | Global satellite service | Inmarsat single network access code | The digits after +870 identify an Inmarsat destination rather than a national area. |
| +881 | Shared global satellite code | Global Mobile Satellite System (GMSS) | One identification digit follows +881 before the subscriber portion. |
| +882 | Shared network code | International networks | A two-digit identification code follows +882 and identifies the assigned network. |
| +883 | Shared service/network code | IoT/M2M and some historical network uses | A three- or four-digit identification code follows +883; voice capability must not be assumed. |
| +979 | Global service | International premium-rate service | The service category signals premium-rate treatment, not a geographic destination. |
How are +870, +881, +882 and +883 numbers structured?
The international code is only the first routing layer. Shared resources add an identification code before the remaining subscriber digits. The placeholders below show the hierarchy and are intentionally not callable numbers.
| Example | Safe pattern | E.164 code | Remaining structure |
|---|---|---|---|
| Inmarsat pattern | +870 XXX XXX XXX | +870 | Subscriber digits allocated inside the Inmarsat numbering scheme |
| Iridium pattern | +881 6 XXX XXXXX | +881 | Identification code 6, followed by provider-assigned subscriber digits |
| Globalstar pattern | +881 8 XXX XXXXX | +881 | Identification code 8, followed by provider-assigned subscriber digits |
| International network pattern | +882 NN … | +882 | Two-digit network identification code, then the assigned subscriber structure |
| IoT/M2M pattern | +883 NNN … | +883 | Three- or four-digit identification code, then the assigned resource |
The live ITU shared-code database lists +881 6 and +881 7 as assigned to Iridium, and +881 8 and +881 9 as assigned to Globalstar at this guide's review date. That assignment data explains routing; it does not establish a device's owner, activity, location or service plan.
How do you call a satellite or non-geographic number?
1. Verify the complete service number
Obtain the number from the subscriber or service provider. Do not infer missing identification or subscriber digits from a country-code directory.
2. Keep the international code
A +870 or +881 number is already international. Do not add the country code for the subscriber’s current physical location.
3. Use + or the origin exit prefix
On a compatible mobile, keep the + form. On an all-digit service, replace + with that origin carrier’s international prefix, just as you would for a geographic E.164 number.
4. Check carrier access and price
Confirm that the originating plan permits the service range and read the published rate. A valid E.164 structure does not guarantee reachability or ordinary international-call pricing.
5. Follow the terminal provider’s instructions
Satellite devices may need registration, network visibility, antenna orientation or another provider-specific state before they can receive a call.
Access, cost and validation pitfalls
Country lookup mismatch
Do not label every E.164 code as a country. A data model should support geographic area, shared plan, global service, satellite service and network resource types.
Prefix-to-provider drift
Use the current ITU assignment record and a verification date. Reclaimed or reassigned identification codes make an undated static mapping unsafe.
Unexpected call price
International, satellite, shared-cost and premium-rate categories can be billed differently. Displaying a code is not a price quote.
Blocked origin network
A carrier can restrict a valid global-service or satellite range. Try the provider’s approved alternative only after confirming both access and charges.
False location inference
A non-geographic number does not reveal where the terminal is now. Even a geographic mobile number may be roaming elsewhere.
Voice capability assumption
Some +883 resources support IoT/M2M applications rather than unlimited voice telephony. Number shape alone does not prove the supported channel.
How should software store and classify these numbers?
Preserve the canonical +digits value under the ordinary 15-digit E.164 limit, but do not force a country field when the code identifies a global service or network. Store the matched code family, identification code, assignment source and verification timestamp separately. If a product must quote price or availability, query the actual originating carrier or service provider instead of deriving those facts from the number.
Syntax validation can confirm a known structure. Assignment data can show which organisation currently holds a code block. Neither step proves that a subscriber number is allocated, active, reachable or controlled by a particular person. Use the layered phone validation workflow when those distinctions matter.
Choose the right numbering explanation
Use the toll-free guide for +800 access, the shared-code guide for geographic overlaps, and the routing guide for portability and carrier hand-off.
Standards and allocation sources
- ITU-T E.164: The international public telecommunication numbering planInternational Telecommunication Union. Verified 2026-07-19.
- ITU-T E.164 international shared country codes databaseInternational Telecommunication Union. Verified 2026-08-29.
- ITU-T E.164.1: Assignment of country codes and identification codesInternational Telecommunication Union. Verified 2026-08-29.
- Universal International Freephone Number formatInternational Telecommunication Union. Verified 2026-08-29.
- FleetBroadband Multi-Voice service informationInmarsat. Verified 2026-08-29.
See our editorial and sourcing methodology.