065 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.
Why 065 needs more than a broad label
The reviewed provider reference lists MTN for 0655,0656 and 0657. It does not establish every 065 subrange. Read the fourth digit and preserve the distinction between a documented entry and a missing entry. An omitted subrange is unverified in this source, not proof that a number is invalid.
| Documented prefix/subrange | Provider label as published |
|---|---|
0655 | MTN |
0656 | MTN |
0657 | MTN |
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
No observed-network percentage is published on this page. Use the documented subranges and a current full-number check rather than manufacturing a percentage for the missing reference coverage.
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.
Source gaps versus number validity
This is an illustrative situation, not a reported customer case: A supplier asks you to recharge an 065 number, but a quick search gives a single provider for the entire prefix. Check the complete number and the specific product instead of filling the source gaps with a guessed network. If the lookup is unavailable, ask the recipient to confirm the current retail provider before paying.
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 065 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.
065 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.