← All posts

How Nammaooru verifies a bus route — and why it matters

TownBus Admin · 25 May 2026 · updated 9 Jun 2026

Every route on Nammaooru passes through community verification. Here's the process, why scraped data alone never works, and how you can help.

Most transit apps scrape route data from one source, dump it into a database, and never check again. That's why their timings are wrong, their routes outdated, and their fares fictional.

Nammaooru takes a different approach.

Three-step verification

  1. Initial entry: Routes start as community submissions or curated imports. They show on the site marked "Unverified — community to confirm".
  2. Two independent confirmations: When two different commuters report the same timing, fare, or stop within 30 days, the data flips to ✓ Verified.
  3. Periodic re-check: Verified data goes stale. After 6 months without any user interaction, the badge downgrades to "Last verified DD-MM-YYYY".

Why this matters

A scraped database has no notion of "is this still true today?" Community verification answers exactly that. The bus that ran at 8:15 in 2023 might run at 8:30 today — and the person who actually boards it knows.

How to help

Open any route page. Each schedule pill has a tiny ✓ / ✗ next to it. One tap = one verification. Two taps from independent commuters = a verified schedule, helping every future passenger on that route.