CIBIL Score Not Showing Despite Active Credit Cards – Need Clarification

[Mallikarjun Barika]

Hello everyone

I’m facing a strange issue with CIBIL and need guidance.
CIBIL website shows “NH / No Score” with reasons like no credit activity / only add-on cards, which is not true in my case.
I actively use 4 credit cards (including 1 secured card) every month and pay all dues on time.
Recent bureau scores:
Experian: 816
Equifax: 855
CRIF High Mark: 778
My cards are reporting correctly to other bureaus.
No missed payments, no inactivity, regular statements generated and paid.
Questions:
Why would CIBIL show no score when other bureaus clearly show active credit history?
Is this a reporting/mapping issue from card issuers to CIBIL?
What’s the correct way to get this fixed — dispute, issuer escalation, or CIBIL grievance?

Any insights or similar experiences would really help. Thanks

Attachments​

• 
  IMG_20260102_104056.jpg
  81.5 KB · Views: 0
• 
  IMG_20260102_104020.jpg
  80.1 KB · Views: 0
• 
  IMG_20260102_104003.jpg
  80.5 KB · Views: 0
• 
  

 

[arjungoyal12]

This is actually a pretty common CIBIL quirk, so you’re not doing anything wrong.

Most likely it’s a data mapping or reporting issue on CIBIL’s side. Even a small mismatch in PAN, name format, DOB, or address from one issuer can cause CIBIL to treat your profile as “no score”, while Experian/Equifax/CRIF merge it correctly. I’ve seen cases where cards were reporting fine everywhere except CIBIL.

Another possibility is misclassification, sometimes CIBIL wrongly tags accounts as add-on or non-scoreable (secured cards especially), which blocks score generation.

What I’d suggest:

• Raise a dispute on CIBIL under “No Score / No Credit Activity”.
• At the same time, email or call your card issuers and ask them to specifically confirm reporting to CIBIL (not just “all bureaus”) and to re-push your data.
• If nothing changes after one reporting cycle, file a CIBIL grievance referencing both the dispute and issuer confirmations.

Since your other bureau scores are excellent, this is almost certainly a backend issue and should fix itself once the data syncs properly.

Hope this helps, you should be sorted soon