Skip to content
Nepal Docs Guide

Nepal Docs Guide is an independent educational website. We are not affiliated with the Government of Nepal, any ministry, department, office, or official portal. Always verify final rules, fees, forms, and deadlines on official government sources.

Nagarik App and Digital Services
Medium
High priority update

MDMS Registration Nepal: IMEI Check and Personally Imported Phone Documents

Check a phone's IMEI before applying, choose NTA's individual import route, prepare matching travel evidence, and track an MDMS approval or correction request.

Last updated Oct 8, 2026
EmailShare

Independent guide, not an official website

Nepal Docs Guide is not affiliated with the Government of Nepal. This guide helps you prepare, but official portals and offices control final rules, fees, forms, and timelines.

Quick answer

Start with the Nepal Telecommunications Authority's MDMS public portal and check the phone's IMEI. If the device still needs individual registration and fits the personally imported-phone route, open Individual Registration. The current form separates device details, your own email verification, personal/travel information and document review. Enter the correct IMEI or IMEIs, match the applicant and arrival details to genuine evidence, upload the documents requested and keep the acknowledgement. Submission is not approval: check the individual-registration status with the IMEI and the same email used in the form. Customs treatment and NTA device registration are separate questions.

Eligibility

  • A person using NTA's current individual route for a phone personally brought into Nepal, with truthful importer and travel evidence.
  • A person who has first checked whether the device is already registered. A phone already recorded in MDMS does not need another application simply because its owner changed.
  • A locally purchased phone, commercial shipment, courier delivery or unusual importer case should be resolved through its appropriate seller, customs or NTA route. A visible individual form does not establish eligibility for every import.
  • A traveller whose citizenship or travel situation does not fit the fields should ask NTA which route applies rather than borrowing another person's identity or arrival record.

Required documents checklist

  • □ Each IMEI shown by the device. NTA's public checker instructs users to obtain the 15-digit IMEI with *#06#. Compare it with the device settings and packaging; dual-SIM devices can show more than one IMEI.
  • □ The phone's brand and model, plus the mobile number in use where the current device form requests it. Do not enter the SIM number in an IMEI field.
  • □ An email account belonging to the applicant and accessible for the portal's verification code. Use the same address for the later registration-status enquiry.
  • □ Clear identity and travel evidence requested by the live form. NTA's instructions refer to passport or citizenship details and arrival/departure immigration evidence or a boarding pass; follow the exact uploads applicable to your route.
  • □ The return country, arrival date, address and contact details that match the applicant's records. If the phone user differs from the person who brought it, prepare the truthful user details requested by the form.
  • □ Any relevant purchase and customs records you hold, for resolving ownership or import questions if the authority asks. This is preparation advice, not a claim that every file is a compulsory portal upload.
  • □ The submitted acknowledgement, entered IMEIs and approval or rejection email. These help distinguish a device-registration problem from a SIM or network fault.

Step-by-step process

  1. Open https://mdms.nta.gov.np/public and check the device's registration status first. Copy the actual IMEI from the handset and preserve all 15 digits, including any leading zero. Compare each relevant IMEI instead of checking only the one printed on an old invoice.
  2. Decide whether individual registration is the correct route. A phone bought from a Nepal retailer should first be checked with the seller. Commercial and courier imports should not be presented as personal travel baggage to make a form accept them.
  3. Open the official Registration Options page and choose the individual, personally imported-device route. Confirm the mdms.nta.gov.np address before providing passport scans or other identity evidence. You do not need an unofficial agent merely to find the form.
  4. Complete Step 1, Mobile Device Details, with the IMEI information, brand, model and current mobile-use information requested. Read the labels for a second IMEI when the handset has one. Resolve a mismatch on the actual device before carrying a wrong number through the application.
  5. Complete the email-verification stage with the applicant's own email. Receive and enter the code only inside the official service. If the message is delayed, check the address and spam folder before requesting another code; do not share it with a seller or social-media helper.
  6. Enter the personal and travel information in the next stage from your evidence. Review the address, return country and arrival date carefully. The form has separate information for a phone user who is someone else; answer that truthfully rather than changing the importer to match the eventual user.
  7. Prepare the final uploads at normal reading size. The identity details, stamps and relevant travel information must be legible. Upload the file types and sizes the live screen accepts. Do not invent a passport page, edit an arrival date or crop away information needed to reconcile the journey.
  8. Review the final summary against the phone and source records before submitting. Save the acknowledgement and a private copy of what you supplied. A form submitted with the right IMEI but mismatched travel details can still require correction or be rejected.
  9. Check the individual-registration status with the IMEI and the same email address used to apply. The current status page accepts IMEI 1 or IMEI 2 and explains that rejected applications can be edited. Follow the actual reason and permitted correction process rather than sending another conflicting application.
  10. After NTA records the outcome, verify the relevant IMEIs again. If the phone is registered but cannot use a network, separate that from registration: check the SIM and ask the mobile operator or NTA about the device's actual status. An MDMS acknowledgement alone does not diagnose a hardware or operator issue.

Fees and timelines

  • The current individual-registration screens reviewed do not publish one universal portal fee or guaranteed approval time. This guide therefore quotes neither a fixed MDMS charge nor a number of processing days.
  • Customs duty, baggage allowances and import eligibility are separate from submitting NTA's form. Confirm the current customs treatment for your actual journey and device count; registration is not proof that duty was paid or waived.
  • NTA's public portal carries notices with historical dates. Do not treat a past implementation notice as a new nationwide blocking deadline or a current travel allowance.
  • The form's acknowledgement and NTA's reviewed approval are different stages. Wait for the recorded outcome and correct a rejection through the route provided; email verification by itself does not register the phone.
  • Keep purchase, travel and customs evidence after registration in case a later discrepancy needs investigation. No fixed evidence-retention period is asserted by this guide.

Common mistakes

  • Submitting a second application before checking whether the device is already registered.
  • Using a phone number, serial number or a mistyped 15-digit value as the IMEI.
  • Registering only one device IMEI without checking what the current form requires for the other.
  • Using another person's travel record to disguise who actually brought the phone.
  • Uploading an unreadable passport, stamp or boarding pass and assuming an email code proves approval.
  • Reading a dated NTA implementation notice as a current customs rule or a promise that every unregistered device will be blocked on the same day.

Choose the next action before applying

SituationNext stepWhat it does not prove
IMEI is already recordedRetain the check; investigate the actual problemThe handset or SIM cannot have another fault
Personally brought phone still needs registrationUse the individual route if your case fitsEvery import automatically meets customs rules
Phone bought from a Nepal retailerCheck IMEI and ask the seller about the import recordA customer's borrowed passport repairs a seller's record
Application rejectedRead the reason and use permitted edits on the status serviceAnother email or duplicate application resolves the mismatch

Keep a small application record

Record the handset model, IMEI 1 and any IMEI 2, applicant email, arrival date and acknowledgement together. When a status enquiry fails, compare those entries with the submitted form before resubmitting. Keep passport and travel files in private storage, not in a public shared folder.

Independent device-registration guide

NepalDocsGuide is independent of NTA and Nepal Customs. It cannot approve a device, waive import tax or change an IMEI. Use genuine identity and travel records and the current official form. Never publish your complete passport, OTP or application evidence to get informal help.

Printable checklist

MDMS Registration Nepal: IMEI Check and Personally Imported Phone Documents

  • Actual handset IMEI or IMEIs recorded
  • Existing registration checked
  • Correct import route confirmed
  • Brand/model matched
  • Own email accessible
  • Applicant and phone-user details truthful
  • Travel date matches evidence
  • Uploads legible
  • Acknowledgement saved
  • NTA outcome checked

FAQ

Official sources

Use these references for final confirmation before applying. Nepal Docs Guide is independent and does not replace official instructions.

  • NTA MDMS public portal

    Nepal Telecommunications Authority

    Public IMEI checker, 15-digit identifier guidance and dated NTA notices; historic enforcement text was not asserted as a fresh deadline.

  • NTA registration options

    Nepal Telecommunications Authority

    Current distinction between individual registration and other MDMS services.

  • NTA individual registration

    Nepal Telecommunications Authority

    Current four stages, device/email/personal and travel fields, evidence uploads, acknowledgement and review distinction.

  • NTA individual-registration status

    Nepal Telecommunications Authority

    IMEI and matching-email enquiry, including the permitted editing route for rejected applications.

Need official confirmation?

If your case involves corrections, deadlines, legal use, foreign submission, or a rejected application, contact the relevant official office before paying fees or submitting documents.

Author

Nepal Docs Guide Editorial Desk

Citizen services research team

The editorial desk prepares independent, plain-language summaries from cited official sources and reader correction reports. It does not claim government affiliation, professional credentials, or field testing.

Found this guide helpful?

NepalDocsGuide keeps its guides free for everyone. If you'd like to support the website's maintenance and future guides, you can make a voluntary contribution.

Support NepalDocsGuide

Related guides

Prepare a federal Public Service Commission online profile and a traceable vacancy application without copying an old deadline, fee or document list into a new notice.

Preparation depends on the notice and your records; PSC publishes the application and payment deadlinesUpdated Oct 7, 2026Save-ready
Read guide
Nagarik App and Digital Services
Priority update

How to Reset a Nagarik App Web Portal Password

A cautious account-recovery guide for users who can reach the official Nagarik App citizen web portal but cannot sign in with their password.

About 10-20 minutes if the registered contact works; support time variesUpdated Sep 6, 2026Save-ready
Read guide
Nagarik App and Digital Services
Priority update

Nagarik App Citizenship Not Verified: Causes and Safe Fixes

A safe troubleshooting guide for Nagarik App citizenship verification: separate account and OTP failures from citizenship matching, copy source fields exactly, fix the responsible record, and use official support without exposing identity data.

10-30 minutes for safe field and app checks; telecom KYC or citizenship-record updates and support review can take longerUpdated Sep 1, 2026Save-ready
Read guide
Browse all services