How to Check if Your NIN Is Linked to Your SIM in Nigeria (2026)

The single most useful tool for checking a NIN-SIM link in Nigeria is *996#, the NCC-standardised universal verification short code. It works on every Nigerian network without exception. It is free of airtime. The response arrives within seconds. And it reads the operational link state directly from the network record, which is the same state the bank, the employer, and the government scheme will see when they verify against the SIM.

The architecture The NCC-standardised universal status check is *996#. Dial it from any active Nigerian SIM (MTN, Airtel, Glo, or 9mobile/T2), select 'View NIN Status' (typically option 4 on the menu), and the response confirms whether the SIM is linked, pending, not linked, or in a validation-failed state. The check is free of airtime. Telco-specific status surfaces also exist: MTN's NIN Status Portal at mtn.ng/helppersonal/nin-status-portal and the dedicated nin.mtn.ng/status page, Airtel via *121# with prompts at airtel.com.ng/NIN_information, Glo via the gloworld.com/ng/nin page, and 9mobile/T2 via *996# with prompts on the T2mobile help centre. The retrieval code *346# returns the NIN itself if the SIM-to-NIN link is live; the airtime fee is ₦50 for retrieval.

The flow is short enough to fit on one screen:

1. 1
   Dial *996# from the SIM you want to checkThe SIM must be inserted in the handset you are dialling from. Any signal works; no data plan is needed. The check costs nothing in airtime.
2. 2
   Select 'View NIN Status' on the menuTypically option 4, occasionally option 3 depending on the telco's menu version. The wording is consistent across all four networks per NCC's harmonisation.
3. 3
   Wait for the SMS responseUsually instant. The response confirms the SIM is linked, pending, not linked, or in a validation-failed state. The exact wording is operator-specific but the four states are universal.
4. 4
   If you want the list of all linked SIMsFrom the same menu select 'View Numbers Linked to NIN'. The network returns the full list of phone numbers linked to your NIN by SMS. Useful when checking for an unfamiliar registration.

That is the entire universal check. The remaining sections of this article cover how to read the response correctly, when the telco-specific portals matter as fallbacks, and what to do when *996# itself misbehaves.

*996# returns one of four states, and the right reaction depends on which one.

The four states map cleanly to four next steps. Where the response is ambiguous (some telco menus return "Status: unknown" or "Verification incomplete" on transient platform errors), the right move is to retry the check fifteen minutes later before treating it as a real result.

The most common error in this flow is treating the status check as the linkage itself. They are different acts.

A status check is a read of the current network record. It costs nothing, returns in seconds, and tells you what the verification platform sees right now. *996# is the check.

A linkage submission is a write to the network record — a request that the SIM be bound to a NIN, dispatched to NIMC for verification, and reconciled into the operational state that the next status check will read. Linkage submissions take longer (seconds to days depending on the architecture Third-party verification of a NIN passes through one of three paths. Banks query NIMC through the Nigeria Inter-Bank Settlement System (NIBSS), which is shared infrastructure owned by all licensed banks and the Central Bank of Nigeria. Telecommunications operators query NIMC directly through the NIMC Verification Service: MTN and Airtel run on the real-time path while Glo and 9mobile run batches. Government schemes (JAMB, NYSC, NIS passport processing) and large employers query through their own integration against the NIMC API. In every case NIMC holds the canonical record; verifiers maintain their own cached copies that refresh on different schedules.), happen through telco-specific channels, and only complete when the SMS confirmation arrives.

The practical consequence:

• If *996# returns "not linked", do not keep dialling it; dial it once, then go and submit a linkage on the right telco channel. See how to link NIN to SIM.
• If *996# returns "pending" on a batch network (Glo, 9mobile/T2), do not assume the link failed. Check again after the batch window. The cache-refresh and verification timings are in After NIMC issues an updated NIN record, downstream verifiers refresh their cached copies on independent schedules. Banks pulling through NIBSS typically reflect the change within 24 to 72 hours. Telcos on the real-time path (MTN, Airtel) often refresh same-day after a new slip is issued; batch-path telcos (Glo, 9mobile) can take several working days. The Nigeria Immigration Service re-verifies on demand when a NIS support ticket asks for it. JAMB and NYSC typically refresh per registration cycle rather than continuously.
• If *996# returns "pending" on a real-time network (MTN, Airtel) for more than a working day, the submission did not stick. Resubmit through a different channel rather than waiting.

The status check answers a different question from the linkage submission. The one signal both share is the operator's confirmation SMS — when the link reconciles, both the customer-facing SMS and the next *996# check should flip to "linked" within minutes of each other.

*996# is the right first check. Four telco-specific surfaces are useful as fallbacks, mostly when the universal response is unclear or when you need a written record for an escalation.

• MTN — the NIN Status Portal. The URL is mtn.ng/helppersonal/nin-status-portal, with a dedicated check page at nin.mtn.ng/status. Enter the MTN number, receive an OTP at that number, type the OTP back, and the page returns the linkage status as a written confirmation. The portal route is the right channel when an escalation needs an in-writing artefact rather than just the SMS receipt.

• Airtel — *121# with the NIN sub-menu. Dial *121# from the Airtel line and select the NIN option (the position in the menu drifts between Airtel's menu revisions; look for "NIN" in the option list). The flow surfaces the same linkage status that *996# returns. The airtel.com.ng/NIN_information page also exposes a portal-based check for customers who prefer a browser.

• Glo — the Glo Café app and the gloworld.com/ng/nin page. Both surface the linkage status. Because Glo runs batch verification, the network-side state in the app reflects the most recent batch reconciliation, which can lag a fresh submission by 24 to 72 hours. The app is the most useful fallback when the linkage was submitted via the SMS-to-109 route, because the app gives a single dashboard view of the SIM's current registration state.

• 9mobile/T2 — the T2mobile Help Centre and the same *996# menu. The eKYC web app at 9mobile.com.ng/NIN surfaces the linkage status alongside the linkage submission flow. Customer care on 200 (from a T2 line) or +234 809 0200 200 (from any line) has back-end visibility into the queue state that the customer-facing *996# does not expose; this is the right channel when a submission has been pending unusually long.

The telco-specific surfaces add detail (a written record, a queue-state diagnostic) that the universal *996# does not. They are fallbacks, not replacements — the universal check should be the first tool for almost every case.

Three failure modes are worth knowing.

• Network busy or USSD session ended unexpectedly. The most common failure. The telco's USSD gateway has a daily capacity limit, and during peak hours a fresh session can drop before the menu loads. Wait fifteen minutes and retry. If three retries fail, switch to the telco-specific portal (MTN's NIN Status Portal, Airtel's *121# menu, the Glo Café app, or the T2 help centre).

• No response at all. The dialer reports "USSD code error" or similar and no SMS arrives. This is usually a SIM-side issue — the SIM is not provisioned for USSD, the line is partially barred (outgoing data calls allowed but signalling blocked), or the network slot is degraded. Try another SIM on the same network from the same handset to isolate; if the second SIM also fails, the network is the problem.

• NIMC platform outage. Rare since the July 2025 vendor switch stabilised, but recurring. During an outage *996# may return "verification unavailable" or "service temporarily down". The architecture background is in NIN verification; the right response is to wait, because no operator-level fix will help while NIMC's verification platform is offline.

If *996# fails repeatedly on every network and the news is reporting an NIMC outage on the day, the answer is patience. If *996# fails only on one of your SIMs and works on others, the issue is operator-side.

A related but distinct flow is retrieving the NIN from the SIM. The two are easily confused but answer different questions.

• *996# checks whether the SIM is linked to a NIN — yes or no.
• *346# retrieves the actual NIN from the SIM if a link exists.

The retrieval costs ₦50 in airtime (the NIMC retrieval fee, deducted from the SIM's balance). The status check is free. A working *346# response is also a strong implicit signal that the linkage is operational end-to-end — if the network can return the NIN, it knows the SIM-to-NIN bond exists at NIMC's retrieval service.

The full retrieval walkthrough is in how to check your NIN. The deeper context — what NIMC actually knows, how the telcos and banks read from it — is in NIN verification.

Pick the row matching your response.

• 'Linked' and records valid. Nothing further. The SIM is operational. Re-check after any future SIM swap, NIN modification, or apparent verification failure at a bank or employer.
• 'Pending' on Glo or 9mobile/T2 within 72 hours of submission. Wait. Recheck at 24, 48, and 72 hours. Treat as normal until the five-working-day threshold.
• 'Pending' on MTN or Airtel beyond 30 minutes, or on Glo/9mobile/T2 beyond five working days. The submission has stalled. See how to fix NIN-SIM linking error for the diagnostic decision tree.
• 'Not linked'. Submit the link via your telco's channels. The hub at how to link NIN to SIM covers the cross-network overview; the per-telco articles cover the channel-by-channel walkthrough.
• 'Validation failed' or 'NIN does not match'. Diagnose the underlying mismatch. The cross-surface flow is in NIN validation failed; the SIM-specific decision tree is in how to fix NIN-SIM linking error.
• Line blocked at the same time as 'validation failed' or 'not linked'. The block is the symptom; the linkage is the underlying fix. See SIM blocked due to NIN for the recovery flow that handles both at once.