A software engineer from Karachi called me last week, frustrated and confused. “I checked my SIM with 667 and it showed my name. Then I checked with 668 and it showed I have 5 SIMs. But I only own 2! Which one is lying?”
Neither was lying. He was simply using the wrong tool for the wrong purpose.
667 and 668 are Pakistan’s two most powerful free SIM verification tools — but they serve completely different purposes. Using the wrong one at the wrong time gives you incomplete information, creates confusion, and leaves you vulnerable to fraud.
This complete comparison guide will teach you exactly when to use 667, when to use 668, and how to combine both for maximum security. By the end, you’ll know more about SIM verification than 99% of Pakistanis.
Quick Answer: 667 vs 668 — What’s the Difference?
| Feature | 667 (MNP Method) | 668 (CNIC Method) |
|---|---|---|
| What You Send | Type “MNP” | Your 13-digit CNIC |
| What You Get | Owner name of SPECIFIC SIM in your phone | COUNT of ALL SIMs on your CNIC |
| Scope | Only the inserted SIM | All networks, all SIMs |
| Shows Owner Name | ✅ Yes — full name | ❌ No — only counts |
| Shows CNIC | ✅ Yes — partially masked | ❌ No |
| Shows Network | ✅ Yes | ✅ Yes — per operator |
| Shows BVS Status | ✅ Yes | ❌ No |
| Internet Required | ❌ No | ❌ No |
| Cost | ✅ Free | ✅ Free |
| Response Time | 5-10 seconds | 10-30 seconds |
| Best For | Verifying who owns a specific SIM | Auditing all SIMs on your CNIC |
Simple Rule:
Use 667 to check “WHO owns THIS SIM?”
Use 668 to check “HOW MANY SIMs are on MY CNIC?”
What Is 667? Complete Explanation
667 is the MNP (Mobile Number Portability) shortcode that PTA expanded to include instant SIM ownership verification. When you send “MNP” to 667, the system identifies the SIM currently in your phone and returns the registered owner’s information from PTA’s central database.
667 Returns:
- Registered owner’s full name
- CNIC number (partially masked: 35201-XXXXXX-1)
- Current network operator
- SIM registration status (Active/Suspended/Blocked)
- Biometric Verification Status (BVS)
667 Example Result:
Dear Customer,
SIM 03001234567 is registered as:
Name: Ahmed Hassan Khan
CNIC: 35201-XXXXXX-1
Network: Jazz/Mobilink
Status: Active
BVS: VerifiedHow to Use 667:
Step 1: Insert the SIM you want to verify into your phone
Step 2: Type exactly: MNP (capital letters)
Step 3: Send to 667
Step 4: Receive results in 5-10 seconds
667 Works Best When:
- You found a SIM card and want to know the owner
- You’re buying a used phone and want to verify the seller
- You want to confirm your own SIM registration is correct
- You need to check biometric verification status
- You’re verifying a family member’s SIM ownership
For the complete 667 guide, read our detailed MNP 667 SIM Owner Check Pakistan 2026 article.
What Is 668? Complete Explanation
668 is PTA’s official shortcode for CNIC-based SIM verification. When you send your 13-digit CNIC number to 668, PTA’s DIRBS system queries all five mobile operators and returns a complete count of every SIM registered under your identity.
668 Returns:
- Total number of SIMs on your CNIC
- Breakdown by operator (Jazz, Zong, Telenor, Ufone, SCO)
- Overall count across all networks
668 Example Result:
Dear Customer,
SIMs registered on CNIC 3520112345671:
Total: 7
Jazz: 3
Zong: 2
Telenor: 1
Ufone: 1
SCO: 0How to Use 668:
Step 1: Type your 13-digit CNIC without dashes: 3520112345671
Step 2: Send to 668
Step 3: Receive results in 10-30 seconds
668 Works Best When:
- You want to know total SIMs on your CNIC
- You’re doing monthly CNIC security monitoring
- You suspect unauthorized SIM registrations
- You need to check if you’re near the 25 SIM limit
- You want operator-wise breakdown of your registrations
For the complete 668 guide, read our detailed 668 SIM Check Pakistan 2026 article. Or How Many SIMs on My CNIC — NADRA vs PTA vs 668 Which Is Most Accurate Pakistan 2026
Side-by-Side Technical Comparison
| Technical Aspect | 667 | 668 |
|---|---|---|
| System Used | MNP database + DIRBS | DIRBS only |
| Query Method | SIM-based (device must have SIM) | CNIC-based (no SIM needed) |
| Database Scope | Single SIM record | All SIMs across all operators |
| Information Depth | Deep (full owner details) | Shallow (counts only) |
| Verification Level | Individual SIM | CNIC-level overview |
| Update Frequency | Real-time | Real-time |
| Networks Covered | Current SIM’s network | All 5 operators simultaneously |
| Can Check Others | ❌ No — only inserted SIM | ⚠️ Technically yes (ethical concerns) |
| Privacy Level | High — need physical SIM | Lower — only need CNIC number |
| Legal Use | Personal verification | Personal CNIC monitoring |
When to Use 667 — 15 Real Scenarios
Scenario 1: Buying a Used Phone
Situation: Someone is selling you an iPhone for Rs. 80,000. Price seems too good.
Action:
Ask seller to insert their SIM → Send MNP to 667 → Check if the name matches seller’s CNIC/identity → If different name appears = stolen phone → Walk away
Why 667, Not 668:
You need to verify THIS specific SIM, not count all SIMs on seller’s CNIC.
Scenario 2: Found a Lost SIM
Situation: You found a SIM card on the street or in a taxi.
Action:
Insert SIM → Send MNP to 667 → Get owner’s name and masked CNIC → Contact them or submit to police with verified owner info
Why 667, Not 668:
You need identity of THIS specific SIM’s owner, not a CNIC audit.
Scenario 3: Verifying Your Own SIM Registration
Situation: You registered a new SIM at a franchise. Want to confirm it’s under YOUR name.
Action:
Insert new SIM → Send MNP to 667 → Verify YOUR name appears → Check BVS status is “Verified”
Why 667, Not 668:
You need detailed registration info for this specific SIM, including biometric status.
Scenario 4: Employee Phone Verification
Situation: You gave a company SIM to an employee. Want to confirm it’s still registered to company CNIC.
Action:
Take phone → Send MNP to 667 → Verify company registration details appear → Confirm not transferred
Why 667, Not 668:
Need to verify THIS specific SIM hasn’t been transferred to employee’s personal CNIC.
Scenario 5: Checking Biometric Status
Situation: You heard about SIM blocking. Want to check if your biometric verification is complete.
Action:
Insert SIM → Send MNP to 667 → Check “BVS: Verified” appears → If shows “Not Verified” = urgent action needed
Why 667, Not 668:
Only 667 shows BVS status. 668 doesn’t provide biometric information.
Scenario 6: Child’s SIM Verification
Situation: Registered a SIM for your 12-year-old under your CNIC. Want to confirm registration.
Action:
Insert child’s SIM → Send MNP to 667 → Confirm YOUR name appears as registered owner
Why 667, Not 668:
Need to verify this specific SIM shows correct parent registration.
Scenario 7: SIM Swap Suspicion
Situation: Your mobile banking stopped working suddenly. Suspect SIM swap fraud.
Action:
Immediately send MNP to 667 → Check if YOUR name still appears → If different name = SIM swapped = emergency action
Why 667, Not 668:
Need instant verification of THIS SIM’s current owner to detect swap.
Scenario 8: Second-Hand Device from OLX
Situation: Buying a used tablet with built-in SIM from OLX.
Action:
Before payment → Insert SIM → Send MNP to 667 → Verify seller identity → Check for stolen device indicators
Why 667, Not 668:
Need to verify the specific SIM in this device.
Scenario 9: Rental Property Tenant Verification
Situation: Tenant provided CNIC copy. Want to verify their contact SIM is genuine.
Action:
Ask to borrow phone briefly → Send MNP to 667 → Confirm name matches CNIC copy provided
Why 667, Not 668:
Need to verify THIS specific SIM belongs to the person claiming to be tenant.
Scenario 10: Family Member SIM Check
Situation: Your elderly mother has a SIM. Want to confirm it’s properly registered under her CNIC.
Action:
Take her phone → Send MNP to 667 → Verify her name appears → Check BVS verified
Why 667, Not 668:
Need detailed info for this one SIM, not all SIMs on her CNIC.
Scenario 11: Network Operator Verification
Situation: Franchise told you they registered your SIM on Jazz, but you’re getting Zong signals.
Action:
Send MNP to 667 → Check which operator name appears in result → Confirm actual network
Why 667, Not 668:
Need to know THIS SIM’s actual operator. 668 only gives counts, not SIM-specific operator.
Scenario 12: Post-Transfer Confirmation
Situation: You transferred SIM ownership at franchise yesterday. Want to confirm transfer completed.
Action:
Insert transferred SIM → Send MNP to 667 → Check if NEW owner’s name appears → If old name still shows = transfer pending
Why 667, Not 668:
Need to verify ownership status of this specific transferred SIM.
Scenario 13: Corporate SIM Audit
Situation: Your company has 50 SIMs. Need to verify each one is registered to company CNIC.
Action:
Insert each SIM → Send MNP to 667 → Document registered name for each → Flag any personal registrations
Why 667, Not 668:
Need individual verification of each specific SIM. 668 would only give total count.
Scenario 14: Suspicious Call Investigation
Situation: Receiving harassing calls from a specific number. Want to identify owner.
Action:
If you can access that SIM → Send MNP to 667 → Get masked CNIC and owner name → Report to authorities
Why 667, Not 668:
Need identity information for THIS specific number, not CNIC audit.
Scenario 15: Marriage Verification
Situation: Arranged marriage proposal. Want to verify person’s identity through their SIM.
Action:
(With permission) Take their phone → Send MNP to 667 → Verify name matches proposal documents
Why 667, Not 668:
Need to verify THIS person’s SIM ownership, not conduct full CNIC investigation.
When to Use 668 — 15 Real Scenarios
Scenario 1: Monthly CNIC Security Audit
Situation: First day of every month. Routine security check.
Action:
Send CNIC to 668 → Compare result with your personal SIM list → If count matches = safe → If higher = investigate
Why 668, Not 667:
Need complete overview of ALL SIMs on your CNIC across all operators.
Scenario 2: After Losing Your Wallet
Situation: Lost wallet containing CNIC card, driving license, and bank cards.
Action:
Immediately send CNIC to 668 → Note current counts → Check again weekly for 1 month → Any increase = unauthorized registration
Why 668, Not 667:
Need to monitor ALL operators for new unauthorized registrations, not check individual SIMs.
Scenario 3: Pre-Employment Background Check
Situation: You’re hiring someone. Want to verify their CNIC isn’t flagged with excessive SIMs.
Action:
(With written permission) Get their CNIC → Send to 668 → Check if count is suspiciously high (15+ SIMs = red flag)
Why 668, Not 667:
Need overview of their CNIC’s total SIM registrations, not individual SIM verification.
Scenario 4: Approaching SIM Limit
Situation: You have multiple business SIMs and personal SIMs. Want to know if you’re near the 25 limit.
Action:
Send CNIC to 668 → Check total count → If 20+ = stop registering new SIMs → Plan which to deactivate
Why 668, Not 667:
Need total count across all operators to monitor limit, not individual SIM details.
Scenario 5: Suspecting Identity Theft
Situation: Getting strange calls about loans/debts you never took. Suspect CNIC misuse.
Action:
Send CNIC to 668 → Count total SIMs → Compare with your actual SIM count → Large discrepancy = identity theft
Why 668, Not 667:
Need to discover TOTAL unauthorized registrations across all networks.
Scenario 6: After Data Breach News
Situation: News reports NADRA data breach. Worried your CNIC data leaked.
Action:
Send CNIC to 668 immediately → Note counts → Re-check weekly for 2 months → Monitor for unexpected increases
Why 668, Not 667:
Need to monitor all operators for fraudulent registrations, not check individual SIMs.
Scenario 7: Deceased Relative’s CNIC
Situation: Your father passed away. Need to identify and deactivate all his SIMs.
Action:
Send his CNIC to 668 → Get operator-wise counts → Visit each operator → Request deactivation with death certificate
Why 668, Not 667:
Need complete operator-wise breakdown to plan deactivation visits.
Scenario 8: Before International Travel
Situation: Going abroad for 6 months. Want to secure your CNIC before leaving.
Action:
Send CNIC to 668 → Document exact counts → Give copy to trusted family member → They check monthly while you’re away
Why 668, Not 667:
Need baseline CNIC snapshot for monitoring during absence.
Scenario 9: After Franchise Visit
Situation: Registered 2 new business SIMs at Jazz franchise yesterday.
Action:
Send CNIC to 668 today → Check Jazz count increased by exactly 2 → Confirms both registered correctly
Why 668, Not 667:
Need to verify total registrations processed correctly across operator.
Scenario 10: Divorce/Separation Situation
Situation: Recently separated. Spouse had access to your CNIC. Want to check for unauthorized registrations.
Action:
Send CNIC to 668 → Compare with pre-separation counts you documented → Any increase = investigate immediately
Why 668, Not 667:
Need complete CNIC audit to detect any misuse during relationship.
Scenario 11: Rental Agreement Verification
Situation: Landlord kept CNIC copy 3 months ago. Want to ensure no misuse.
Action:
Send CNIC to 668 now → Compare with counts from 3 months ago (if documented) → Check for unexpected registrations
Why 668, Not 667:
Need to monitor if CNIC copy led to unauthorized registrations across any operator.
Scenario 12: Teenager’s CNIC First Issue
Situation: Your 18-year-old just got their first CNIC. Want to ensure clean slate.
Action:
Send their CNIC to 668 → Should show 0 or only parent-registered SIMs → Any unexpected count = investigate
Why 668, Not 667:
Need to verify no one registered SIMs on their CNIC before they received it.
Scenario 13: Business Partnership Due Diligence
Situation: Considering business partnership. Want to verify partner’s CNIC health.
Action:
(With permission) Get CNIC → Send to 668 → Normal count 1-8 SIMs = okay → 15+ SIMs = red flag for investigation
Why 668, Not 667:
Need overall CNIC health assessment, not individual SIM details.
Scenario 14: Bank Loan Application
Situation: Applying for large bank loan. Bank may check your CNIC. Want to verify yourself first.
Action:
Send CNIC to 668 → Ensure count is normal (under 10) → If high, deactivate unused SIMs before application
Why 668, Not 667:
Banks check total CNIC registrations. You need same overview they’ll see.
Scenario 15: After Receiving Suspicious SMS
Situation: Received SMS: “Your CNIC has been used to register new SIM” but you didn’t register any.
Action:
Immediately send CNIC to 668 → Compare with your known count → If increased = unauthorized SIM = block immediately
Why 668, Not 667:
Need to identify which operator has the new unauthorized registration.
The Power Strategy: Using 667 AND 668 Together
The most powerful SIM verification strategy uses BOTH methods in sequence. Here’s the professional approach:
Monthly Security Routine (First Sunday of Every Month):
Step 1: CNIC Audit (668)
9:00 AM → Send CNIC to 668 → Document counts in spreadsheet
Step 2: Individual Verification (667)
9:05 AM → Insert each of your SIMs one by one → Send MNP to 667 for each → Verify your name appears on all → Check BVS status on all
Step 3: Cross-Verification
9:15 AM → Count your physical SIMs → Compare with 668 total → Numbers should match exactly
Step 4: Documentation
9:20 AM → Update your security spreadsheet:
| Date | 668 Total | Jazz | Zong | Telenor | Ufone | My Actual SIMs | Status |
|---|---|---|---|---|---|---|---|
| Mar 1, 2026 | 4 | 2 | 1 | 1 | 0 | 4 | ✅ Match |
| Apr 1, 2026 | 4 | 2 | 1 | 1 | 0 | 4 | ✅ Match |
| May 1, 2026 | 5 | 3 | 1 | 1 | 0 | 4 | 🚨 ALERT |
Discrepancy Investigation Protocol:
When 668 and 667 Don’t Match:
Example: 668 shows Jazz: 3, but you only have 2 Jazz SIMs and both show your name via 667.
Investigation Steps:
- Re-check 668 immediately → Confirm count still shows 3
- Visit Jazz service center same day → Request “CNIC SIM Registration Printout”
- Get all 3 Jazz numbers → They’ll print actual numbers
- Identify the unauthorized number → The one you don’t recognize
- Submit SIM Disowning Request → Fill franchise form
- Confirm blocking → Send CNIC to 668 after 48 hours → Jazz count should drop to 2
For complete blocking procedures, read our guide: How to Block Unauthorized SIMs on CNIC Pakistan 2026.
Common Mistakes People Make
Mistake 1: Using Only One Method
Wrong Approach:
“I only use 668 every month. That’s enough.”
Problem:
668 gives counts, not verification. You don’t know if YOUR name is on each SIM. Someone could transfer your SIM to their CNIC and register a replacement on yours. Same count, different owner.
Right Approach:
Use 668 for counts + 667 for individual SIM ownership verification.
Mistake 2: Trusting 668 Count Without Verification
Wrong Approach:
“668 shows 4 SIMs, I have 4 SIMs, everything is fine.”
Problem:
Your 4 SIMs could have been swapped with 4 different SIMs. Count matches but ownership changed.
Right Approach:
Check 668 count PLUS send MNP to 667 from each SIM to verify your name.
Mistake 3: Using 667 for CNIC Monitoring
Wrong Approach:
“I check each SIM with 667 monthly. I’m secure.”
Problem:
667 only checks SIMs you insert. Unauthorized SIMs on your CNIC that you don’t physically have won’t be detected.
Right Approach:
Use 668 monthly to catch unauthorized SIMs you don’t have physical access to.
Mistake 4: Not Documenting Results
Wrong Approach:
“I checked last month, everything was fine. I remember the count.”
Problem:
Memory fades. When count increases from 4 to 5, you won’t remember when it changed or investigate properly.
Right Approach:
Maintain monthly spreadsheet with dated 668 results.
Mistake 5: Checking Only After Problems
Wrong Approach:
“I’ll check when I face issues.”
Problem:
By then fraud may have occurred. Mobile loans taken, accounts opened, criminal activities conducted.
Right Approach:
Check BEFORE problems. Monthly prevention is better than crisis reaction.
667 vs 668: Which One Is More Important?
Short Answer: Both are equally critical. Neither replaces the other.
Long Answer:
668 is your radar → It shows you the complete picture of what’s on your CNIC. Without 668, you’re blind to unauthorized registrations you don’t physically hold.
667 is your microscope → It verifies individual SIM ownership and status. Without 667, you can’t confirm your actual SIMs are still registered to you.
Think of it like home security:
- 668 = Security camera showing ALL people on your property
- 667 = Face recognition verifying identity of each specific person
You need BOTH for complete security.
Technical Differences Explained
Database Architecture:
667 Workflow:
Your Phone → SIM Card → IMSI Number → MNP Database Query
→ DIRBS Cross-Reference → Owner Details Retrieved → SMS Sent668 Workflow:
Your CNIC → DIRBS Database → Multi-Operator Query (Jazz + Zong + Telenor + Ufone + SCO)
→ Count Aggregation → SMS SentQuery Complexity:
667: Simple single-record lookup (fast, 5-10 seconds)
668: Complex multi-operator aggregation (slower, 10-30 seconds)
Data Freshness:
Both: Real-time queries against live database
Update Lag: 24-48 hours after franchise registration
Real User Stories: 667 vs 668 in Action
Story 1: The Mobile Loan Fraud (668 Saved Her)
Ayesha, a teacher from Faisalabad, received calls about a Rs. 40,000 JazzCash loan default. She never took any loan.
She used 667 first:
Checked her 2 SIMs → Both showed her name → Thought everything was fine
Then used 668:
CNIC showed Jazz: 4 (she only owned 2 Jazz SIMs)
Result:
Found 2 unauthorized Jazz SIMs on her CNIC. One had the fraudulent loan. 667 alone wouldn’t have found them because she didn’t have physical access to those SIMs.
Lesson: 668 catches what 667 can’t see.
Story 2: The SIM Swap Attack (667 Saved Him)
Kashif, a businessman from Lahore, woke up to find his mobile banking not working.
He used 668 first:
CNIC showed 5 SIMs total → Same as yesterday → Thought nothing changed
Then used 667:
His primary SIM showed a DIFFERENT name!
Result:
His SIM was swapped overnight. Fraudster registered replacement SIM on his CNIC (keeping count same) and transferred his original SIM to their CNIC. 668 alone showed no change, but 667 caught the swap immediately.
Lesson: 667 catches what 668 can’t detect.
Story 3: The Complete Strategy (Both Together)
Hamza from Islamabad uses both methods together:
Monthly routine:
- 1st of month: 668 check → Document counts
- Same day: 667 check on each SIM → Verify ownership
- Spreadsheet updated with both results
Result after 18 months:
Caught 1 unauthorized SIM (668 alert), detected 1 SIM transfer attempt (667 alert), blocked fraudulent franchise registration, protected his identity.
Lesson: Combined strategy provides complete protection.
Quick Reference: Decision Tree
NEED TO VERIFY SIM?
↓
Do you have physical access to the SIM?
↓
YES → Use 667
- Insert SIM
- Send MNP to 667
- Get owner name, CNIC, BVS
↓
NO → Use 668
- Send CNIC to 668
- Get count of all SIMs
- Visit operator for detailsMONTHLY MONITORING?
↓
Use BOTH:
1. Send CNIC to 668 (total overview)
2. Send MNP to 667 from each SIM (individual verification)
3. Cross-verify results match
4. Document in spreadsheetFrequently Asked Questions
Q1: Can I use 667 to check someone else’s SIM?
Answer: Technically yes if you have physical access to their SIM, but:
- Ethically questionable without permission
- May violate privacy under PECA 2016
- Only check SIMs you own or have explicit permission to verify
Q2: Can I use 668 to check someone else’s CNIC?
Answer: Technically yes if you know their 13-digit CNIC, but:
- Serious legal and ethical concerns
- Violates privacy rights
- Could constitute identity fraud
- Only check your own CNIC or immediate family with permission
Q3: Which method shows more information?
Answer: 667 shows MORE information (name, masked CNIC, network, status, BVS) but for ONLY ONE SIM. 668 shows LESS information (just counts) but for ALL SIMs across ALL networks. Different purposes, incomparable depth.
Q4: Which one should I use first?
Answer: Depends on situation:
- Routine monitoring: Start with 668 (overview), then 667 (verification)
- Specific SIM verification: Use 667 only
- CNIC health check: Use 668 only
- Maximum security: Always use both
Q5: Can results from 667 and 668 contradict each other?
Answer: They shouldn’t contradict, but can appear to:
Example:
- 668 shows: Jazz: 3
- You have 2 Jazz SIMs and both show your name via 667
- This means 1 Jazz SIM exists on your CNIC that you don’t physically have
This isn’t contradiction — it’s 668 revealing what 667 can’t check (SIMs you don’t possess).
Q6: Is one method more reliable than the other?
Answer: Both equally reliable — they query the same PTA DIRBS database. Perceived unreliability usually comes from user error:
- Wrong CNIC format in 668
- Wrong interpretation of results
- Not understanding what each method shows
Q7: Which method is faster?
Answer: 667 is typically faster (5-10 seconds) because it’s a simple single-record lookup. 668 takes longer (10-30 seconds) because it aggregates data across all five operators.
Q8: Do I need internet for either method?
Answer: No. Both are SMS-based services. No internet, no data balance, no special app required. Work on the most basic feature phones.
Q9: Can I use both methods from the same SIM?
Answer: Yes. You can:
- Send MNP to 667 from your SIM → Get its ownership details
- Send your CNIC to 668 from the same SIM → Get your CNIC’s SIM counts
Both work from any Pakistani SIM on any network.
Q10: What if 667 shows my name but 668 shows higher count?
Answer: This is normal and important:
- 667 confirms the SIM you’re checking is registered to you
- 668 reveals you have ADDITIONAL SIMs registered on your CNIC that you’re not currently checking
- Action: Visit operators showing higher counts and request full SIM list
SIM OWNER DETAILS
3 thoughts on “667 vs 668 Pakistan 2026 – Which SIM Check Method to Use When? Complete Comparison”