Feed status · checked 2026-08-01
Advance Transit
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 16 hours ago; last changed 23 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
203 of 203 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
890 of 890 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
Check the flagged stop times for transposed minutes.
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.
⏱ A few minutes per flagged trip.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
- 203 of 203 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
- 890 of 890 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 scheduled trips move faster between stops than a bus can.
- Next action
- Check the flagged stop times for transposed minutes.
- 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.
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.
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 122 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 8 kinds of issue across 136 instances (0 error, 88 warning, 48 informational).
Service data covers the next 122 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
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Red Route, Downtown Shuttle, Green Route, Orange Route).
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.
39 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Depot St", "Dan & Whit’s", "Dresden Rd EB (Drop Only)", 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 203 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.
- Yellow Route (yellow)
- Downtown Shuttle (pink)
- Green Route (green)
- Brown Route (brown)
- Orange Route (orange)
- Blue Route (blue)
- Red Route (red)
- Lot 20 (purple)
- Enfield-Canaan (gray)
- Blue-Red Route (purple)
- Pink Route (pink)
- Lot 9 (white)
| Route | Type | Line color |
|---|---|---|
| Yellow Route | Bus | yellow |
| Downtown Shuttle Dartmouth-Hanover Downtown Shuttle | Bus | pink |
| Green Route | Bus | green |
| Brown Route | Bus | brown |
| Orange Route | Bus | orange |
| Blue Route | Bus | blue |
| Red Route | Bus | red |
| Lot 20 Lot 20 Shuttle | Bus | purple |
| Enfield-Canaan Enfield-Canaan Commuter | Bus | gray |
| Blue-Red Route | Bus | purple |
| Pink Route | Bus | pink |
| Lot 9 Lot 9 Shuttle | Bus | white |
List every stop
- Olcott Industrial Park
- A Street
- Depot St
- Datamann, Opp.
- Wilder Motel
- Stoney Creek, Opp.
- Billings Farm Road
- Brick House Lane NB (Drop Only)
- Hemlock Ridge, Opp.
- Hanover Fire Station
- CRREL
- Dan & Whit’s
- Heritage Lane
- 45 Lyme Road
- Dartmouth Printing EB (Drop Only)
- Dresden Rd EB (Drop Only)
- Rivercrest
- Kendal
- Brockway
- Vail DMS
- Enfield @ Anne's
- Huse Park
- Canaan SB
- Canaan Church
- Hartford Village
- Heater Rd, DHMC, Opp.
- Heater Landing, Opp.
- 89 Lebanon St NB (Drop Only)
- Sunset Motel, Opp.
- Indian Ridge
- Maple, Rt 10
- Hazen Street 3
- Highland Ave
- Hazen Street
- Hazen Street 2
- Tracy Hall
- Target Plaza
- Upper Valley Plaza
- 70 Hanover St
- Lebanon
- Summer St, Leb
- Go Go Mart
- Hanover High School
- DHMC East
- Buck Road
- Colburn to Lebanon
- Wilder Motel, Opp.
- Datamann
- Billings Farm Rd, Opp.
- Stoney Creek
- Hemlock Ridge
- Jericho St. SB (Drop Only)
- Gould Rd, Opp.
- Valley Terrace
- Hayden Court
- Maple Rt 10, Opp.
- Ravenswood
- Chandler Road
- Dartmouth Ave to Lebanon
- VA Hospital
- Veterans Park
- Bugbee Senior Center
- Sunset Motel
- Dunkin Donuts
- Twin River Clinic
- Cloverleaf NB
- Downtown WRJ
- S. Main & Mountain Ave
- Trailer Park @ Sykes
- Hickory Ridge
- Cumberland Farms
- Knights Funeral Home
- Haven
- US 5 @ Co-op
- Cascadnac, Opp.
- Shady Lawn, Opp.
- Hartford PO
- Hartford PO, Opp.
- Lebanon Towers
- Leverone Field House, Opp.
- Go Go Mart NB
- Greensboro Road
- Heater Rd, DHMC
- Heater Landing
- 20 Mechanic St
- Hartford Town Hall
- Slayton Hill Rd, Opp.
- Rivermill, Opp.
- Park & Ride, Tafts Flats
- Cumberland Farms, Opp.
- Saunders Ave
- Miracle Mile Plaza
- Hair Shed
- Gilman Ctr
- Wheeler Hall
- Hanover Inn
- McKenna Road
- West St., Opp.
- Service Center
- King Arthur Café and Store
- West Street
- Montshire Road
- Main at Church, Opp.
- Whitcomb Ave
- Main at Church St.
- Kildeer, Opp.
- Service Center, Opp.
- Romano Circle
- Glen Rd Plaza, Opp.
- Mascoma, Holiday Dr
- Timberwood to Hanover
- Glen Ridge Rd
- Memorial Drive to Hanover
- Sykes Ave @ Greyhound
- Wyeth Road
- Hanover Park
- 89 Lebanon St SB (Drop Only)
- Hartford Town Hall, Opp.
- Mascoma Svgs Bk
- Valley Rd
- West Lebanon
- Cascadnac Ave
- Shady Lawn
- Romano Circle, Opp.
- Glen Road Plaza
- Shaws
- Beverage King EB
- Interchange Drive
- Walmart
- BJ's
- Irving
- Main at Allen
- Hanover PO (Drop Only) NB
- Dunster Drive
- DHMC
- Hanover Co-op
- Gould Road (Sachem)
- Parkhurst
- Maynard Street
- Colburn to Hanover
- Carter Street
- Webster Avenue
- Timberwood to Lebanon
- Quail Hollow
- Park & Ride, Turnpike Rd
- Moore Lane
- Dulacs
- Rivermill
- 25 Mechanic St
- Westboro Woods
- Miracle Mile Plaza, Opp.
- Golf Course
- Thompson Lot
- Visual Arts Ctr
- Hanover Park, Opp.
- Reed/Dartmouth Hall
- Burke
- G Lot
- Dewey Lot
- Tuck Circle
- Summer St NB
- Alumni Gym
- Carson
- Wheeler Hall, Opp.
- Maynard
- Wentworth St
- Lot 9 - Stop 4
- North Entrance
- Lot 9 - Stop 3
- Lot 9 - Stop 2
- Lot 9 - Stop 1
- Lot 20 - Stop 4
- Lot 20 - Stop 5
- Lot 20 - Stop 3
- Lot 20 - Stop 2
- Lot 20 - Stop 1
- Sachem Village
- Sykes @ Holiday Drive
- Aquatic Center
- Bugbee @ Brookview
- Sterling Springs
- 401 Mt Support
- 402 Mt Support
- Wentworth Way
- Mascoma HS
- Elm to Lebanon
- Elm to Canaan
- South Rd
- Lebanon Middle School, Opp
- Lebanon Middle School
- River House at Quail Hollow
- White River Junction, VT
- Norwich Farmers Market – Saturdays, May-Oct only
- Norwich Farmers Market, Opp. – Saturdays, May-Oct only
- Daniels Drive
- Johnson Drive
- Centerra Co-Op
- River Valley Club
- Observatory Road
- Leverone Field House
- Outpatient Surgery Center
- Court Street
- Ledyard Lot
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 74.2 | first check |
| 2026-07-30 | 74.2 | no change |
| 2026-07-31 | 74.3 | up 0.1 |
| 2026-08-01 | 74.3 | 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
11 findings, ordered by severity.
Show every finding
- Warning890 instances
890 of 890 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)
- Warning203 instances
203 of 203 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)
- Warning64 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)
- Warning12 instances
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)
- Warning7 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)
- Warning3 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · 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)
- 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)
- 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)
- Info6 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)
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 122 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 890 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 122 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.
- 7 of 203 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 122 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 70 / 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 60 / 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/advance-transit/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.