GTFS FEED CHECK · RUNS IN YOUR BROWSER · NOTHING UPLOADED

Check a GTFS feed before you publish it

Drop the GTFS schedule zip your scheduling software exported and get every problem with its file and line: missing files and fields, trips pointing at routes, stops or services that do not exist, stop times that run backwards, the date your service runs out, buses that would have to travel at 900 km/h, and stops with latitude and longitude swapped.

For small transit agencies, demand-response and campus shuttles, and the vendors who build their feeds. The zip is opened in this tab and never leaves your device. Rules from the GTFS Schedule Reference (revised 2026-04-27); each finding says which rule it is.

1. Your feed

Or drag the zip onto this box.

Choose a feed, then click Check feed.

A worked example

The "example with errors" button loads a made-up four-stop bus line with seventeen kinds of problem planted in it. Among them:

Each one comes back with its file, line and the rule it breaks. The same checks on four real published feeds, and what they found, are in the list of every check.

What it checks, and what it leaves out

Check every export in CI

cli.mjs is the same engine for a terminal or a CI job, with no dependencies (Node 20 or newer). It reads the zip from disk and sends nothing anywhere.

node cli.mjs gtfs.zip              # exit 1 if there are errors
node cli.mjs gtfs.zip --strict     # warnings fail too
node cli.mjs gtfs/ --json          # a folder of .txt files, machine-readable
node cli.mjs gtfs.zip --today=2026-12-01

A 2.6-million-stop-time feed (TriMet's, 210 MB unzipped) takes about 8 seconds in Node. In a browser tab the same feed needs a few hundred MB of memory; for feeds that size the CLI is the better fit.

Common questions

Why does a trip planner show no service from my GTFS feed?

The most common reason is that the feed has expired: every service_id in calendar.txt has an end_date in the past, so no trip runs on today's date. The checker reports the last date with any service and warns when it is less than 7 days away, the minimum the GTFS reference asks for.

What does the checker look at?

The required files and fields; every value's type (times, dates, colours, time zones, URLs, coordinates, enums); unique keys; references between trips, routes, stops, shapes, services and agencies; the order of stop times within each trip; the calendar's coverage of the next 30 days; and two sanity checks the reference does not set: straight-line speeds between stops above a per-mode ceiling, and stops hundreds of kilometres from the rest of the feed.

Is my feed uploaded?

No. The zip is opened in this browser tab with the browser's own decompression, and a test in the code asserts the page and the engine make no network calls.

Does a clean result mean Google Maps or another app will accept the feed?

No. Each consumer has its own rules and review. This tool checks the feed against the published GTFS Schedule Reference and a few sanity limits, and tells you which rule each finding comes from.

How is this different from the MobilityData validator?

The MobilityData GTFS Validator is the canonical, much larger rule set, and the right tool before you submit a feed. This checker covers fewer rules but runs instantly in a browser tab or as a zero-dependency Node script, with no install, account or upload, which suits a quick check on every export or a CI step.