Feed status · checked 2026-08-01
Marble Valley Regional Transit District (MVRTD) Flex
Based on the feed this agency publishes
Service mode Bus
down 0.4 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 73 minutes ago; last changed 41 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
Review the rule documentation for 'invalid_pickup_drop_off_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid pickup drop off window (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
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 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
787 of 787 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
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
- Invalid pickup drop off window (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_pickup_drop_off_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- 306 of 306 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
- 787 of 787 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
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.
Review the rule documentation for 'invalid_pickup_drop_off_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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_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.
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 30 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 9 kinds of issue across 301 instances (6 error, 254 warning, 41 informational).
Service data covers the next 30 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.
2 accessibility depth signals
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.
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 306 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.
- 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) |
| Marble Valley ADA Paratransit | Bus | green (no shape in feed) |
| K1 - SnowShed | Bus | pink |
| Vale | Bus | blue |
| High Ridge | Bus | teal |
| Bear | Bus | brown |
| Skyship | Bus | white |
| O&D Marble Valley Community Transportation | Bus | green (no shape in feed) |
| Mountain Green | Bus | pink |
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 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 54.0 | first check |
| 2026-07-30 | 51.9 | down 2.1 |
| 2026-07-31 | 51.5 | down 0.4 |
| 2026-08-01 | 51.1 | down 0.4 |
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.4 points 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.
What changed over time
On 2026-07-25 this feed started at grade F. On 2026-08-01 feed entered the expiry window (30 days of service left). As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-01 Feed entered the expiry window (30 days of service left).
Everything we checked
13 findings, ordered by severity.
Show every finding
- Error6 instances
Invalid pickup drop off window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_pickup_drop_off_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_pickup_drop_off_window · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning787 instances
787 of 787 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)
- 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning178 instances
178 of 787 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)
- Warning113 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning88 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · 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.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning11 instances
Some service calendars in the feed have already ended.
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.)
Finding code: 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.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info21 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)
- Info12 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)
- Info1 instance
This feed includes flexible (demand-responsive) service, and riders are told how to book it.
Dial-a-ride and zone service are described for trip planners, not just fixed routes.
Fix: No action needed. (None.)
Finding code: scorecard_flex_service
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 30 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Needs attention
- Service data runs out in 30 days; renew before you certify.
- 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 Needs attention
- 781 of 787 trips have a shape; 6 do not. Fill in shapes.txt and trips.shape_id for the remaining trips so every trip has a path. Reduced, Rural, and Tribal NTD reporters need full coverage by Report Year 2026.
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. 1 validator error to resolve. Service data runs out in 30 days; renew to qualify. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data runs out in 30 days; renew to qualify.
- 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 116 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 6 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 48 / 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 50 / 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 57 / 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/marble-valley-regional-transit-district-mvrtd-2831/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.