One B.Tech graduate, five calculators, and the three mistakes that caused them.
We are a small independent team, not an SEO company or a content agency. Examfo.com is five calculators that solve problems we ran into ourselves while studying.
Three things went wrong for us during our degrees, and each one became a tool here.
One of us was short on attendance in third semester. An online calculator said eight more classes would fix it. Weeks later, worked out on paper, the real number was thirty. The tool had assumed the total classes would stay frozen while more were attended, which is impossible: every class you attend is also a class that gets held. That single wrong number nearly cost an exam.
Later, on a job application, a CGPA was converted using the CGPA × 9.5 formula that every website quotes. That university published a different one. The figure submitted was several points off. Nobody tells you the formula changes by university, and changes again by regulation year.
And after JEE Main, the same score checked on three different calculators gave three different answers, because some were still using a marking rule that NTA had changed.
The pattern in all three: the tool gave a confident number and no way to check it.
No accounts, no signup, no data collection. Nothing you type reaches a server, because there is no server-side calculation anywhere here. No rank predictors or college predictors, because doing those properly needs a dataset we don't have. And we never present a converted figure as official: for any transcript or application, your institution's own number is the one that counts.
University conversion formulas are genuinely hard to pin down. They change by regulation year and are often published in a circular that never reaches the wider internet. If a formula here is wrong for your university and you have the official circular, notification or grade card that proves it, send it through the contact page. We'll correct the tool, mark that formula verified, and note where it came from.
The same goes for bugs, and for anything that doesn't work with a screen reader or keyboard. We treat accessibility problems as bugs, not feature requests.