Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
The Current
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 14% of all tracked agencies and 14% of mid-size agencies. Operates in Vermont.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.1, validator 8.0.1.
Checked for changes 6 hours ago; last changed 8 days ago.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1688 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +12 points
Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required column (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Re-generate shape distances in your export; flag to your vendor if it persists.
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 10 kinds of issue across 237 instances (7 error, 184 warning, 46 informational).
Service data ended 1688 day(s) ago. Trip planners have likely already dropped this feed.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
This agency publishes realtime, but the feed needs an access key we don't have yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (orange)
- 2 (brown)
- 71 (red)
- 72 (red)
- 73 (red)
- 53 (green)
- 57 (pink)
- 4 (red)
- Brattleboro Blue Line (teal)
- 7 (white)
| Route | Type | Line color |
|---|---|---|
| 1 Springfield In-Town | Bus | orange |
| 2 Bellows Falls In-Town | Bus | brown |
| 71 DHMC First Run | Bus | red |
| 72 DHMC Second Run | Bus | red |
| 73 VA & Dartmouth College | Bus | red |
| 53 Bellows Falls-Brattleboro | Bus | green |
| 57 Bellows Falls-Springfield-Ludlow | Bus | pink |
| 4 Brattleboro Red Line | Bus | red |
| Brattleboro Blue Line | Bus | teal |
| 7 Brattleboro White Line | Bus | white |
| 61 Bellows Falls-Chester-Ludlow | Bus | gray (no shape in feed) |
| Dial-a-Ride | Bus | green (no shape in feed) |
| Paratransit | Bus | green (no shape in feed) |
This feed has 291 stops.
List every stop
- White Oaks Loop
- White Oaks Loop
- White Oaks Loop and Tanglewood Road
- Silver Birch
- Silver Birch and Black Pine
- Black Pine
- Tanglewood Lane
- Tanglewood Lane
- Mount Snow drop zone
- Greenspring Road
- (REQUEST STOP) The Summit
- Suntec Loop 1
- Suntec Loop 2
- Main Base Lodge
- Parking Lot E
- Parking Lot E
- Parking Lot D
- Parking Lot D
- Mt Snow Road
- Mount Snow drop zone
- Walmart
- Rodeway Inn
- Park & Union
- North Springfield Post Office
- Gassetts
- 100 River Street
- Irving
- Park & Union
- North Springfield Post Office
- Gassetts
- SHS/RVTC/CCV
- South Street Hill
- 56 Etna Rd
- Brattleboro Union High School (BUHS)
- Exit 1 Industrial Park
- Winston Prouty Center
- Living Memorial Park/BMC
- Bennett Drive
- Great River Terrace
- Brattleboro Police Station
- Brattleboro Post Office
- Centre Congregational Church
- NECCA
- Union Station
- Red Clover
- Transportation Center
- Rolling Hills
- Exit 3 Park & Ride
- Main St Wilmington
- Retreat Farm
- Exit 5 Park and Ride
- High Grove Lot
- Shaws
- Valley News
- East Dover Road
- Austrian Haus
- Mount Snow Marketplace
- Tony's Rock
- Rentals Only
- Gray Ghost
- Kitzhof
- Big Bear's Lodge
- Timber Creek Sugar House
- Coffee House
- Upper Handle Road
- Equipe Sport
- Snow Lake Lodge
- Invasion Snowboard Shop
- 7/11
- Wheeler Farm
- Baptist Church
- Beaver Street
- Beaver Street (Inbound)
- Downtown
- North Star Bowl
- Wheeler Village
- Coldbrook Road
- Higley Hill Road
- Cross's Corner
- Grand Summit Hotel
- Dover School
- West Dover Fire House
- West Wilmington
- Readsboro
- Twin Valley Middle High School
- Marlboro College
- Greyhound Station
- Grace Christian School
- GMCN Terminal
- CT River Transit Office
- Pointe Hotel
- Chester Depot
- Springfield Plaza
- PCM
- Adult Day
- Brattleboro Retreat
- HCRS
- Parent Child Center
- Atkinson & Williams St.
- Penguin Mart
- Mr. G's
- North Meadow Plaza
- SEVCA
- Senior Center
- Sterling House
- Amtrak/Waypoint
- Health Center
- 99 Atkinson St.
- Penguin Mart
- Putney Meadows
- Exit 3 Park & Ride
- Compass School
- 7 Atkinson St.
- Allen Brothers
- C & S
- Hannaford
- Basketville
- Westminster Town Hall
- Riverview Apartments
- Bellows Falls Square
- American Legion
- Hypertherm Building 21
- Hypertherm Heater Rd.
- I-91 Exit 7 Park & Ride
- Webster Hall
- NH Machinery
- Springfield Hospital
- Black River Produce
- Okemo
- I-91 Exit 6 Park & Ride
- VA Hospital
- Dartmouth College/Hanover Inn
- Hypertherm Building 17
- Hypertherm Building 15
- I-91 Exit 8 Park & Ride
- Centerra Park Building 46
- Coburn Hill
- I-91 exit 9 Park & Ride
- DHMC East Entrance
- Centerra Park Building 21
- Centerra Park/LSI
- DHMC-Clinic
- Heater Rd. Bus Shelter
- Southview
- Mountain View
- Whitcomb Building
- State Offices
- North Springfield
- Westview
- People's Bank/Main St.
- Huber Building
- So. VT Rec Center
- Evergreen Heights
- Centerra Park Building 41
- 56 Etna Rd
- Gilman Office Park
- Greyhound/VT Transit
- Main St./Gates St.
- Gathering Place
- SIT
- Lovejoy
- Stantec
- N. Springfield Industrial Park
- Pleasant St. & Rt. 103
- Family Center
- Precision Valley
- Joy Wah
- Lisai's Deli
- Father's Restaraunt
- Rec Center
- Our Place
- Westgate
- MH Winding
- MH Dettman
- Creamery Bridge
- Crowell Lot
- High & Oak
- Main & Elliot
- Elliot & Elm
- Frost
- Canal & Elm
- Market 32
- River Garden (Main St.)
- CCV
- Brattleboro Bowl
- Royal Square Plaza
- Main St./Chamber
- Pliny Park
- Melrose Terrace
- Hayes Court
- Rts. 119 & 63
- Rolling Hills
- Hinsdale High School
- Thicket Hill
- Downtown Hinsdale
- Walmart
- Union Station
- BMH
- Omega
- Guilford Country Store
- BUHS
- Cotton Mill - Brat Industrial Park
- South Main St.
- Marlboro Graduate Center
- Groundworks Shelter
- Holiday Inn Express
- Chester Green
- Jackson Gore
- Western/Fire Station
- Hinsdale High School
- Harlow's
- Riverview Apartments
- Heater Rd. Bus Shelter
- Hypertherm Etna Road
- 56 Etna Rd
- NH Industries
- Greyhound
- Dartmouth College/Hanover Inn
- PCM
- Western/Fire Station
- High & Oak
- Westminster Station
- Downtown Hinsdale
- Rts. 119 & 63
- Mount Snow drop zone
- Mount Snow drop zone
- Mount Snow drop zone
- Mount Snow drop zone
- Mount Snow drop zone
- Mount Snow drop zone
- Mount Snow drop zone
- Mount Snow drop zone
- Mount Snow drop zone
- Sundance Base Lodge
- Carinthia Base Lodge
- Mountaineer Inn
- Inn at Mount Snow
- Upper Snow Tree
- Snow Mountain Village
- The Outlook
- Suntec
- Polar Bear
- Cub Ridge
- Brumm's Way
- Bear's Crossing
- Black Bear
- C & S
- Basketville
- Westminster Town Hall
- Pleasant St. & Rt. 103
- and 41 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 10 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 39.5 | first check |
| 2026-07-01 | 39.5 | no change |
| 2026-07-02 | 39.5 | no change |
| 2026-07-03 | 39.5 | no change |
| 2026-07-04 | 39.5 | no change |
| 2026-07-05 | 39.5 | no change |
| 2026-07-06 | 39.5 | no change |
| 2026-07-07 | 39.5 | no change |
| 2026-07-08 | 39.5 | no change |
| 2026-07-09 | 39.5 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Error5 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show buses jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Validator rule: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
Missing required column (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1688 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning291 instances
291 of 291 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning239 instances
239 of 239 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning173 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 instances
Some service calendars in the feed have already expired.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
5 of 239 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Validator rule: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info29 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
48 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Park & Union", "Park & Union", "SHS/RVTC/CCV", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Recased shouting stop names 5 changes
For example: SHS/RVTC/CCV -> Shs/rvtc/ccv
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Not ready
Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 1688 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Not ready
- Service data expired 1688 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. 2 validator errors to resolve. Service data expired 1688 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Not yet
- Service data expired 1688 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 173 of 290 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 7 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 48 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 59 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/the-current-428/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.