How to Link NIN to a 9mobile SIM in Nigeria (2026)

9mobile is the smallest of the four Nigerian telcos by subscriber base. The carrier's market share moved from over 22 million subscribers at its early Etisalat peak to about 3.2 million in January 2025, and to roughly 2.7 million after the August 2025 rebrand to T2. The smallness of the network is the spine of this article — not because the underlying NIN-SIM linkage is fundamentally different from Glo's batch flow, but because the operational consequences of being the smallest network in Nigeria shape every part of the customer experience.

This article is not a Glo article with the carrier name swapped. The batch verification architecture is the same — submission queue, dispatch to NIMC, response cycle, 24-to-72-hour typical lag. What differs is everything around that core: the channel mix is web-app-first rather than SMS-first; the retail footprint is materially thinner; the brand has changed twice in the operator's lifetime and the second rebrand is still recent enough to confuse some workflows; and a national roaming agreement with MTN affects how the SIM behaves on the day-to-day.

The most useful framing is this. On Glo, the question is "how do I navigate the batch lag?" — because Glo's volume and channel maturity are not the problem; the architecture is. On 9mobile/T2, the question is "how do I link NIN given the smaller operational footprint?" — the batch architecture is shared with Glo, but the carrier's scale changes which channels work best and what to do when they do not. The two situations look similar from a distance and are different up close.

Before the linkage walkthrough, the rebrand needs a moment because it is the freshest operational reality on this network and the reason some search results in 2026 still surface old 9mobile content alongside new T2 material.

The historical context — for older customers whose records may still appear under earlier names — is that the carrier launched as Etisalat Nigeria in 2008, rebranded to 9mobile in 2017 when Etisalat UAE exited following a parent-company debt crisis, and rebranded again to T2 in 2025 after Lighthouse Telecoms acquired a 95.5 percent stake in 2023. Some legacy NIMC records and older bank KYC files reference the EMTS or Etisalat name; the customer should not need to update these, as the underlying NIN-SIM linkage is unaffected by the brand surface, but the legacy names occasionally surface in customer-care diagnostics.

The implication for the NIN linkage: submit through the current channels; the rebrand changed marketing, not architecture.

The 9mobile/T2 NIN linkage in 2026 leans on two channels.

The eKYC web app at 9mobile.com.ng/NIN is T2's flagship submission surface — Nigeria Communications Week reported it as the country's first eKYC SIM-registration web app at launch. The web app handles the submission entirely in a browser, with the phone number entered up front, an OTP sent to that number to confirm ownership, and then the NIN entered on the next screen. Identity capture (a selfie, sometimes a document photograph) lives in the same flow for first-time registrations; for an existing customer linking a NIN to an already-active SIM, the document-capture step is skipped.

*The 996# USSD is the route for customers without a smartphone or data plan. *996# is the NCC universal verification short code; on T2 the menu also exposes the linkage submission flow alongside the status check.

1. 1
   Choice 1 — open 9mobile.com.ng/NIN on a browserDesktop or mobile. The page loads the T2mobile eKYC web app. Enter the 9mobile/T2 phone number and request the OTP.
2. 2
   Or — dial *996# from the 9mobile/T2 SIMThe menu opens. Select the option for NIN submission (typically option 1 or 2 depending on the menu version).
3. 3
   Enter the OTP (web) or the 11-digit NIN (USSD)The web app sends an OTP to confirm the line is in your possession before accepting the NIN. The USSD route skips OTP and asks for the NIN directly.
4. 4
   Submit the NIN11-digit number, no spaces, no hyphens. The submission enters T2's batch queue.
5. 5
   Wait the batch window24 to 72 hours typical, sometimes longer. T2's batch dispatcher runs on a similar cadence to Glo's; weekends and public holidays push the window out.
6. 6
   Check via *996#After 24 to 72 hours, dial *996# from the linked SIM. The response should confirm 'linked'. If still 'pending' after 5 working days, escalate.

If both channels are unavailable — no data and no airtime on the SIM — the third route is customer care on 200 from a T2 line (or +234 809 0200 200 from any line). The agent can take the submission verbally after verifying identity. This is slower than the digital channels but works as a fallback.

The most operationally significant difference between linking NIN to 9mobile/T2 and linking it to MTN or Airtel is the retail footprint. MTN has stores in every state capital and accredited points in most LGAs. Airtel's footprint is concentrated in major cities but still substantial. Glo's retail has thinned since 2017 but remains present in state capitals. T2's footprint is the smallest — T2 Experience Centres in Lagos, Abuja, Port Harcourt, and a handful of other state capitals; outside those, dedicated walk-in support is limited.

The practical consequence: a 9mobile/T2 customer in a secondary town who cannot get the linkage to clear through the digital channels has a longer journey to retail than a customer on any other Nigerian network. The right preparation:

• Resolve everything that can be resolved remotely first. Call customer care on 200 before travelling to retail. Many cases the customer might assume need a physical visit can be cleared on the phone.
• If a visit is needed, batch it. A trip to a T2 Experience Centre is also the right time to update KYC details that have been pending, lift any residual SIM blocks, or replace a damaged SIM. Going once for the NIN linkage and then again three weeks later for a swap is a wasted journey.
• Bring more than you think you need. Original NIN slip, government-issued ID, a backup mobile number (preferably MTN or Airtel, since those work everywhere), and a copy of any prior correspondence with customer care. The desk officer can resolve more in one visit when documentation is comprehensive.

For customers in cities where no T2 Experience Centre is nearby, the eKYC web app is the principal path. T2's design choice to lead with a web app rather than with retail or with SMS is partly a response to this retail-footprint reality.

The customer-care surface is more central to NIN linkage on 9mobile/T2 than on the other networks, given the retail thinness. The published channels:

• Voice: 200 from a T2 line, or +234 809 0200 200 from any line. Open extended hours; agents have access to back-end NIN-linkage status that the customer-facing *996# does not expose.
• Email: [email protected] (also [email protected] during the rebrand transition). Slower than voice but useful when documents need to be attached (e.g., a scanned NIN slip to support a manual linkage request).
• Social handles: @T2mobileNG on X (formerly Twitter), the T2 Facebook page, and the T2 Instagram account. Direct-message support is responsive during business hours; useful when the voice line is congested.
• The T2 community / support page at 9mobile.com.ng/support. Self-service troubleshooting and a ticket-raising form.

When escalating a stuck NIN linkage, the voice channel is normally the right first contact. The agent can confirm whether the submission reached T2's queue, whether the batch has dispatched, and whether NIMC has returned a response. This visibility is what the customer-facing *996# response does not give, and it is what turns a stuck "pending" status from a mystery into a diagnosable case.

The 24-to-72-hour batch window is the typical case. Three edge cases push beyond it on 9mobile/T2 specifically.

• The August 2025 rebrand cutover. Customers who submitted linkages during the rebrand week saw extended lags as T2's back-end systems were reconfigured. Submissions from 8-15 August 2025 in particular took up to two weeks to confirm. This cohort effect is now resolved, but customer-care records still reference rebrand-era cases.
• A legacy Etisalat or EMTS-era customer record. A small minority of long-tenure customers have records carrying older brand identifiers. The NIN linkage normally resolves cleanly against the current MSISDN, but the back-end name fields occasionally lag, producing a "verification failed" response. The fix is a customer-care escalation to refresh the SIM-side record.
• The smallest-batch-volume effect. Because T2's verification volume is the lowest of the four telcos, T2's batch dispatcher runs less frequently than Glo's. Submissions sometimes wait for the next batch in a way that Glo customers do not experience. Five working days is still the threshold for treating a delay as a problem; expect to be closer to the upper end of the 24-to-72-hour window more often than a Glo customer would be.

If a submission has not cleared after five working days and customer care does not resolve it remotely, the diagnostic flow is the same as for any verification failure: check whether the NIN itself is the issue (see NIN validation failed) or whether a NIMC-side outage is at play (see NIN verification for the architecture context).

Glo and 9mobile/T2 share the batch verification architecture but the customer experience differs.

• Glo's primary channel is SMS to 109. 9mobile/T2's primary channel is the eKYC web app. Both networks expose USSD as a fallback, but the leading surface differs.
• Glo has a larger retail footprint. Gloworld outlets exist in most state capitals and many secondary cities. T2 Experience Centres are concentrated in a handful of major cities.
• Glo's subscriber base is larger than 9mobile/T2's, which means Glo's batch runs more frequently. 9mobile/T2 customers more often see the upper end of the 24-to-72-hour window.
• 9mobile/T2 has a national roaming agreement with MTN since August 2025. Glo does not have an equivalent roaming arrangement. This affects coverage day-to-day but not the NIN linkage itself.
• 9mobile/T2 has rebranded twice in its operational lifetime (Etisalat → 9mobile → T2). Glo has been Glo since 2003. Legacy-name effects on customer records are a 9mobile/T2-specific reality.

See how to link NIN to Glo SIM for the Glo walkthrough. If you are on MTN or Airtel, the architecture is real-time and the flow is materially faster; see how to link NIN to MTN SIM or how to link NIN to Airtel SIM for those.

The hub at how to link NIN to SIM covers the universal flow and the cross-telco context.