081 needs a subrange check: the reviewed source does not support one universal network label for all numbers beginning with it. Confirm the complete number before selecting airtime or data. Mobile number portability means the number can remain unchanged when its service arrangement changes.
The fourth digit changes the 081 reference
The source separates 0810 as MTN,0811–0815 and 0817 under the legacy label 8ta, and 0818 as Vodacom. It does not fill every possible 081 subrange. Keep the source labels and gaps visible; do not collapse them into a single current-network promise.
| Documented prefix/subrange | Provider label as published |
|---|---|
0810 | MTN |
0811 | 8ta |
0812 | 8ta |
0813 | 8ta |
0814 | 8ta |
0815 | 8ta |
0817 | 8ta |
0818 | Vodacom |
The source is the provider-published coverage reference, checked 1 November 2026. It is undated, uses some legacy names and is not an ICASA allocation register. A source label is not a live subscriber lookup. See the hub's detailed subrange explanation.
What the lookup observation means
In the defined SIMcloud lookup observations, Telkom was the most observed network for 081, at 64.0%. This describes a lookup dataset, not every active 081 number or the current status of your recipient.
The method uses successful lookup observations over 1 November 2025 to before 1 November 2026, with the latest qualifying result per normalised number. The hub's methodology explains the scope. The remainder is not a measured porting rate: a broad source association is insufficient to reconstruct every number's original assignment and subsequent history.
Subranges, legacy labels and retail-provider compatibility
This is an illustrative situation, not a reported customer case: An 081 contact tells you that an account belongs to a retail brand different from the network name returned by a lookup. Ask which product the retail service accepts. The host, retail brand and source label can describe different layers; selecting a bundle still needs compatibility confirmation.
Keep the original recipient confirmation and the purchase reference together. If an order is uncertain, trace its existing result before submitting another. Prefix knowledge cannot resolve a pending transaction or prove that a specific bundle accepts the recipient's retail service.
Check the complete 081 number
- Obtain the complete intended recipient number through an authorised source.
- Check local and +27 formatting without changing the underlying number.
- Use the protected network-confirmation workflow where supported.
- Read the returned network for its stated purpose and confirm retail-provider/product compatibility.
- Review the recipient, product and total before placing an order.
For a number you control, the own-number guide provides documented methods. If investigating an unknown caller, use Who called me? instead of treating a prefix or lookup result as identity proof.
Choose a compatible product
The dynamic data-price article describes catalogue allowances and comparison limits. A network result does not establish the customer's tariff, bundle eligibility, owner name or wallet balance. Ask the provider for account-specific questions.
Use the USSD finder for the actual retail provider's supported commands. An old prefix association or a host-network label does not automatically establish which menus work on a virtual operator.
081 questions
Can the prefix identify the owner?
No. This reference and SIMcloud's network lookup do not provide subscriber identity or RICA records.
Does the observed leading network guarantee my number?
No. Use the complete number and current supported check. An aggregate percentage describes the reviewed dataset.
Reference and observation method reviewed 1 November 2026.