How Our LTO Tracker Works: Full Methodology

What actually happens when you use it

The tracker is JavaScript that runs entirely in your browser. When you type a plate or MV file number, no request is sent anywhere — there is no server on our side receiving it. The page you already downloaded contains the published rules, and your browser applies them locally.

What each result is based on

• Number coding day — the MMDA UVVRP schedule, keyed to the last digit of your plate.
• Registration renewal month and week — the LTO staggered registration scheme: last digit sets the month, second-to-last digit sets the week.
• MV file number formatting — the official inquiry usually rejects the segment after the dash when it keeps its leading zeros. We generate the variants and rank the one that typically works first.
• Estimated stage — your application date measured against LTO's published targets and widely reported real-world timelines. This is the one output that is an estimate rather than a rule, and it is labelled as such everywhere it appears.

What the tracker cannot know

It cannot see your actual record, and it will never claim to. Sites that show a spinning "searching the LTO database" animation without database access are performing theatre — during our research we found trackers that query endpoints that do not exist. Ours does the opposite: it tells you what is deterministic, estimates what is not, and hands you to the official inquiry pages for the part only the LTO can answer.

How we keep it correct

• Every rule table carries a last-verified date and is re-checked when LTO or MMDA announces a change.
• The decoding logic is covered by an automated test suite that runs before any release.
• When we cannot identify something — such as an issuing office code we cannot source — the tool says "not identified" instead of guessing.

Found a wrong output? That is a priority bug: report it here.