Feed status · checked 2026-08-01
Rockingham MOOver
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued 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.3, validator 8.0.1.
Checked for changes 1 days ago; last changed 28 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
326 of 326 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
193 of 193 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
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.
⏱ A review pass in your scheduling software.worth about +8 points in its category
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.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 326 of 326 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 193 of 193 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Remove retired stops from the export, or add them back to the trips that should serve them. · 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.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 61 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
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.
Score by category
The MobilityData validator flagged 5 kinds of issue across 243 instances (0 error, 191 warning, 52 informational).
Service data covers the next 61 days.
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.
3 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (12, 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.
51 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.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored 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.
This feed has 326 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 7 (brown)
- 1 (orange)
- 2 (brown)
- 71 (red)
- 72 (red)
- 53 (green)
- 57 (pink)
- 4 (red)
- 5 (teal)
- 7 (white)
- 9 (white)
- 10 (black)
- 7S (white)
- 11 (black)
| Route | Type | Line color |
|---|---|---|
| 7 Wilmington-West Dover | Bus | brown |
| 1 Springfield In-Town | Bus | orange |
| 2 Bellows Falls In-Town | Bus | brown |
| 71 Bellows Falls-Lebanon & Hanover, NH | Bus | red |
| 72 Bellows Falls- Lebanon, NH | Bus | red |
| 73 VA & Dartmouth College | Bus | red (no shape in feed) |
| 53 Bellows Falls-Brattleboro | Bus | green |
| 57 Bellows Falls-Ludlow | Bus | pink |
| 4 Brattleboro Red Line | Bus | red |
| 5 Brattleboro Blue Line | Bus | teal |
| 7 Brattleboro White Line | Bus | white |
| 61 Okemo Village | Bus | gray (no shape in feed) |
| 9 Readsboro-W. Wilmington | Bus | white |
| 10 Wilmington-Brattleboro | Bus | black |
| 1 Mount Snow Weekends & Holidays | Bus | blue (no shape in feed) |
| 4 Bears Crossing-Suntec | Bus | yellow (no shape in feed) |
| 6 Kingswood | Bus | brown (no shape in feed) |
| 1 Mount Snow Midweek Non-Holiday | Bus | teal (no shape in feed) |
| 7S Brattleboro White Line Saturday | Bus | white |
| 11 Wilmington-Brattleboro | Bus | black |
| 2 Timber Creek | Bus | orange (no shape in feed) |
| 3 Greenspring | Bus | pink (no shape in feed) |
| 1A SMV-Upper SnowTree-The Outlook Weekends & Holidays | Bus | green (no shape in feed) |
| 14 Stratton-Manchester | Bus | red (no shape in feed) |
| 11 Main Base Lodge Upper Parking Lots | Bus | purple (no shape in feed) |
| 12 Main Base Lodge Lower Parking Lots | Bus | gray (no shape in feed) |
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
- JC's Market
- 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
- Brattleboro Transportation Center
- Rolling Hills
- Exit 3 Park & Ride
- Main St Wilmington
- Retreat Farm
- Exit 5 Park and Ride
- High Grove Lot
- Marlboro Town Garage
- Butterfield Common
- Stratton Village
- Travelodge Chalet Annex
- Econo Lodge
- Behind Northshire Bookstore
- Manchester Town Offices
- Travelodge
- Walgreens
- Windham County, VT, USA
- Brattleboro, VT, USA
- Dummerston, VT, USA
- Guilford, VT, USA
- Chester Town Hall
- Mt. Laurel
- Pleasant St. & Depot St
- Brookhaven
- United Church
- Timber Inn
- Fox Run
- Mill (Main St & Depot St)
- Abenaki Springs
- Walpole Health Clinic
- Windsor, VT, USA
- Stoney Fields
- West Woods
- Alpen Meadow
- Cavendish Green
- 841 Main St, Cavendish
- Pinnacle
- MCC Birge St
- Veterans Memorial Park
- Fletcher Memorial Library
- Lactalis USA Yogurt
- The Rest
- Community Bank
- 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
- Bellows Falls Amtrak Station
- Health Center
- 99 Atkinson St.
- Penguin Mart
- Putney Meadows
- Exit 3 Park & Ride
- Compass School
- 7 Atkinson St.
- Allen Brothers
- C&S
- Hannaford
- Putney Mtn Winery
- 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
- M&T Bank
- 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
- Bridge & Summer Streets
- 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
- 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
- and 76 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 81.0 | first check |
| 2026-07-30 | 81.1 | up 0.1 |
| 2026-07-31 | 81.1 | no change |
| 2026-08-01 | 81.1 | 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-31.
Same feed file as 2026-07-31; 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
10 findings, ordered by severity.
Show every finding
- Warning326 instances
326 of 326 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning193 instances
193 of 193 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. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning190 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.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
6 of 193 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Finding code: mixed_case_recommended_field · 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.)
Finding code: 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.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info10 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · 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).
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 61 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 193 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
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). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also 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. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 61 days.
- 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.
- 190 of 325 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 146 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 86 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 59 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers 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 badge on your agency site or feed README. It updates after each completed scoring check 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/rockingham-moover/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, 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.