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
Marble Valley Regional Transit District (MVRTD)
Based on the feed this agency publishes
down 0.5 since 2026-07-08
Ahead of 63% of all tracked agencies and 62% 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 8 hours ago; last changed 8 days ago.
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
306 of 306 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
781 of 781 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Check the flagged stop times for transposed minutes.
Some scheduled trips travel implausibly fast between stops. Usually a typo'd stop time; riders get impossible arrival estimates.
⏱ A few minutes per flagged trip.worth about +8 points
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
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.
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.
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.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · 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.
Check the flagged stop times for transposed minutes. · 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.
Score by category
The MobilityData validator flagged 7 kinds of issue across 218 instances (0 error, 165 warning, 53 informational).
Service data covers the next 53 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.
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.
- Rutland-Killington Commuter (red)
- Fair Haven (teal)
- Hospital (green)
- Ludlow (teal)
- Manchester (pink)
- Middlebury Connector (red)
- North (red)
- Proctor (green)
- South (black)
- West (teal)
- K1 - SnowShed (pink)
- Vale (blue)
- High Ridge (teal)
- Bear (brown)
- Skyship (white)
- Mountain Green (pink)
| Route | Type | Line color |
|---|---|---|
| Rutland-Killington Commuter | Bus | red |
| Fair Haven | Bus | teal |
| Hospital | Bus | green |
| Ludlow | Bus | teal |
| Manchester | Bus | pink |
| Middlebury Connector | Bus | red |
| North | Bus | red |
| Proctor | Bus | green |
| South | Bus | black |
| West | Bus | teal |
| Fair Haven Expansion | Bus | teal (no shape in feed) |
| K1 - SnowShed | Bus | pink |
| Vale | Bus | blue |
| High Ridge | Bus | teal |
| Bear | Bus | brown |
| Skyship | Bus | white |
| Mountain Green | Bus | pink |
This feed has 306 stops.
List every stop
- Pine St. & Maple St.
- SymQuest
- Killington Ave. & Lafayette St.
- The Pines
- Curtis Ave. & Preston Park
- Curtis Ave. & Stratton Rd.
- Wales St. & Center St.
- Boys & Girls Club
- East St. & Killington Ave.
- Sears - Diamond Run Mall
- Diamond Run Mall
- Kmart - Diamond Run Mall
- Farrell Rd. & Cop John Dr.
- Academy Street Middlebury
- Human Resources
- Rutland, VT, USA
- Barnes St
- Hortonville Road
- Belmont Road
- Healdville Road
- Hillside Inn
- Ramshead Lodge
- Vale Rd
- Killington Rd / ALA Pad
- E Mountain Rd / Trail Creek Condos
- E Mountain Rd / Whiffletree Condos
- 727 E Mountain Rd
- 913 E Mountain Rd
- High Ridge Condo Southbound
- 108 High Ridge Rd
- 180 High Ridge Rd
- Highridge Condominiums
- Spruce Ln / High Ridge Rd
- Killington Bear Mountain Lodge
- Killington Skyeship Base Lodge
- Human Resources Roadside
- Long Trail
- Trail Head
- Albert Cree Drive
- Stratton Road & Gilrain Ave. - Olivia's Market
- Mt Green Rear Entrance
- Mt Green 2D-07
- Pinnacle Condos Rear Lot
- Tennis Courts
- Old Mill Rd at Pinnacle Condos
- Mountain Inn/Cascades
- Court Sq
- 132 Marble St.
- Across from Cumberland Farms
- Allen St.
- American Legion-Brandon
- Baxter St. & Oak St.
- Best Western
- Bowlarama
- Brandon Center (gazebo)
- Brooklyn Rd.
- Carris Reels
- Castleton Family Health Center
- Castleton Post Office
- Castleton State College
- Castleton Village Store
- Chittenden Bank Manchester
- College of St. Joseph
- Colonial Apartments
- Cortina Inn
- Top of West Street
- Crampton Ave. & West St.
- Cumberland Farms Store
- Curtis Ave.
- Deer St.
- Deli @ Killington Corners
- Diamond Run Mall
- E Proctor Rd. & Route 4A
- East Center
- East Dorset Country Store
- East St.
- Eastridge Professional Bldg.
- Estabrook Field Brandon
- Fair Grounds
- Fair Haven Park
- Gazebo Plaza (across from Post Office)
- Godnick Center
- Granger St. & South St.
- Green Mountain College
- Green Mountain Plaza
- Hartsboro Rd.
- Cortina Inn
- Howe Center
- Jackson Ave.
- Jackson Gore
- John C. Stewart
- K1 Base Lodge
- Pittsford Post Office
- Killington Center Inn
- Killington Grand Hotel
- Killington Sports
- Leicester Park & Ride
- Library
- Ludlow Park & Ride
- Mac's
- Main St. & College St.
- Manchester Town Office
- Manchester Village Post Office
- Salisbury Park and Ride
- Maple Village
- Rutland Multi-Modal Transit Center
- Meadow Lake Dr.
- Meadow St. & South St.
- Mendon Mountain Orchards & Motel
- Mendon Mountain View Lodge
- Merchants Bank
- Middle School
- Middlebury Beef E. Middlebury
- Mountain Green Resort
- Mt. Tabor Country Store
- Mussey St.
- North St. & Main St.
- North St. & Pearl St.
- Okemo
- Old Turnpike Rd.
- Porter Pl. & Park St.
- Park Village Brandon
- Parker House
- Pico Resort Hotel
- North West School - Pierpoint Ave.
- Price Chopper
- Proctor High School
- Quality Inn
- Quiznos Ave.
- Randbury Rd.
- Route 4 & Lafayette St.
- Rutland Airport
- Rutland Airport Industrial Park (Entrance)
- Ripley Road and Route 4 (Bennington Furniture)
- Sawyer Hill Rd.
- Seward's Dairy
- Shaws Shopping Complex
- Shaws Supermarket
- Sheldon Towers
- Skyline Corp.
- Snowshed Base Lodge
- St. Alphonso Lot-Pittsford
- Stewarts - Fair Haven
- Terrill St.
- The Inn at Long Trail
- The Inn of Six Mountains
- The Maples
- Town Line Rd.
- Wallingford House
- West Rutland High School
- West Rutland Industrial Park - Call Ahead
- West St. & Cramton Ave.
- West St. & Nichols St.
- Westway Mall
- White Rocks Inn
- William St. & East St.
- Rutland Regional Medical Center
- Regency Manor
- Castleton Park & Ride
- Stewart's - Poultney
- Keith's II
- West St. Market
- West Proctor Rd. & Route 4A
- Killington Motel
- Pico Mountain Commons
- Granger St. & Plain St.
- Granger St. & Park St.
- River St. & Granger St.
- Walmart
- Forest St. & Gibson Ave.
- Meadow St. & Convent Ave.
- Pearl St. & Field Ave.
- Grove St. & Linden St.
- Grove St. & State St.
- Washington St. & Nickwackett St.
- Temple St. & Davis St.
- Brandon Green Mountain Garage
- Killington Park and Ride
- Glenbrook Gymnasium
- Pediatric Associates
- Community Health
- Mussey Street and Allen Street
- Curtis Ave.
- Stratton Rd. and Albert Cree Dr.
- Mussey Street at Brookside Mobile Park
- East Street and Killington Avenue
- Stratton Road and Jackson Avenue
- Jackson Avenue and Stratton Road - Fire Hydrant
- Jackson Avenue and Jackson Heights
- Jackson Ave. & Main St.
- Washington St. & Court St.
- Wales St. & Washington St.
- Norton Pl.
- Templewood Court
- East Street and Edgerton Street
- Temple Street and Main Street
- Main Street and North Street
- Field Avenue and Phillips Street
- Field Avenue and Lincoln Avenue
- Lincoln Avenue and Vernon Street
- 169 Lincoln Ave
- North Street and Church Street
- Crescent Street and Church Street
- Crescent Street and Grove Street
- Park Avenue and Grove Street
- Pine St. & State St.
- Evelyn Street
- Park Village Brandon
- Post Office Brandon
- Otter Valley High School
- Rutland Airport Industrial Park
- Orvis Sporting Goods
- Holden Avenue and Park Street
- Strongs Avenue and Scale Avenue
- Scale Ave. (PEG TV)
- Curtis Avenue and Chase Avenue
- Curtis Avenue at Billings Mobile Manor
- Gay Street and Curtis Avenue
- Regency Manor Driveway
- Genesis Health Ventures Driveway
- Allen St. & Mahoney Ave.
- Killington Avenue and Lafayette Street
- E Center St. & East St.
- Granger Street at Forest Park
- Forest Street and Hickory Street
- South Street and Forest Street
- Meadow Street and River Street
- Meadow Street and School Street
- Meadow Street and West Street
- West St. & Green Hill Ln.
- State Street and Cramton Avenue
- State Street and Evergreen Avenue
- State Street and Columbian Avenue
- Crescent St. & Cleveland Ave.
- Oak Street and Grove Street
- Pearl St. & Vernon St.
- Field Street and Grove Street (Antique Mansion)
- Grove Street and Seabury Street
- Strongs Avenue and River Street
- Ripley Rd.
- East St. & Washington St.
- Killington Ave.
- Allen St. & Common St.
- Forest St. & Park St.
- The Inn at Long Trail
- Jen's Motel - Industrial Park
- Whipple Hollow Road
- Pond Hill Stables
- Crampton Road
- Tags Motel
- and 56 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 9 checks — down 0.5 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 74.6 | first check |
| 2026-07-01 | 74.7 | up 0.1 |
| 2026-07-02 | 74.7 | no change |
| 2026-07-04 | 73.8 | down 0.9 |
| 2026-07-05 | 73.4 | down 0.4 |
| 2026-07-06 | 73.0 | down 0.4 |
| 2026-07-07 | 72.6 | down 0.4 |
| 2026-07-08 | 72.2 | down 0.4 |
| 2026-07-09 | 71.7 | down 0.5 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.5 points 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
- Warning781 instances
781 of 781 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)
- Warning306 instances
306 of 306 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)
- Warning229 instances
229 of 781 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)
- Warning113 instances
Some scheduled trips travel implausibly fast between stops.
Usually a typo'd stop time; riders get impossible arrival estimates.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning41 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)
- Warning10 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)
- 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)
- 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.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info11 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)
- Info8 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)
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).
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Proctor, Ludlow, Bear).
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.
88 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Pine St. & Maple St.", "Killington Ave. & Lafayette St.", "Curtis Ave. & Preston Park", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 53 days.
- 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. 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 53 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.
- 41 of 306 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 139 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
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 74 / 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 88 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 56 / 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/marble-valley-regional-transit-district-mvrtd-430/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.