Feed status · checked 2026-08-01
Beaumont Transit
Based on the feed this agency publishes
Service mode Bus
down 0.1 since 2026-07-31
Catalogued in California.
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 3 hours 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
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
143 of 151 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 +24 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
170 of 170 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 +6 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
- 143 of 151 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
- 170 of 170 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 153 days.
- Published accessibility data
- Accessibility information is stated for 5.3% 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 74 instances (0 error, 22 warning, 52 informational).
Service data covers the next 153 days.
5% of stops state wheelchair accessibility (5% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
5% of stops state accessibility (5% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Route 3).
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.
41 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cherry Valley Blvd and Nancy St", "Xenia Avenue @ Noble Creek Apartments", "1st Street and Emory Avenue", 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 151 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.
- Commuter Link 125 (blue)
- Commuter Link 120 (teal)
- Casino Express (teal)
- Route 3 (teal)
- Route 4 (blue)
- Route 3/4 (white)
- Route 7-1 (orange)
- Route 9 (teal)
- Route 7-2 (teal)
| Route | Type | Line color |
|---|---|---|
| Commuter Link 125 | Bus | blue |
| Commuter Link 120 | Bus | teal |
| Casino Express | Bus | teal |
| Route 3 | Bus | teal |
| Route 4 | Bus | blue |
| Route 3/4 | Bus | white |
| Route 7-1 | Bus | orange |
| Route 9 | Bus | teal |
| Route 7-2 | Bus | teal |
List every stop
- 8th street and Allegheny street
- Xenia Avenue and Starlight Avenue (Southbound)
- Starlight Avenue and Xenia Avenue (Westbound)
- Starlight Avenue and Dorado Lane
- Starlight Avenue and Sundance Drive
- Cougar Way and Sunny Slope
- Beaumont Avenue and Vineland Street (Cherry Valley Market)
- Cherry Valley Blvd and Nancy St
- Cherry Valley Boulevard and Beaumont Avenue (Beaumont High School)
- Cherry Avenue and Cougar Way (Beaumont Adult School)
- Oak Valley Parkway and Edeleweiss Drive (Westbound)
- Starlight Avenue and Oak Valley Parkway (Southbound)
- Starlight Avenue and Snapdragon Way
- Xenia Avenue @ Noble Creek Apartments
- 6th Street and Xenia Avenue (Swapmeet)
- Walmart
- 1st Street and Emory Avenue
- Highland Springs Avenue and 8th Street (Hospital)
- Cougar Way and Beaumont Avenue
- Palm Avenue and Cedar View Drive
- Palm Avenue and Birchwood Avenue (Soutbound)
- Palm and Oak Valley Parkway
- 6th Street and Michigan Avenue (Eastbound)
- 6th Street and Pennsylvania Avenue
- Guardian Self Storage (6th Street)
- Highland Springs and 2nd Street (Game Stop)
- Seminole Drive @ Hadley's
- Seminole Drive and Millard Pass (Adidas Store)
- Seminole between East and West Wings
- Seminole Drive @ McDonald's
- Seminole Drive and Fields Road (Chevron Station)
- 6th Street @ Garden Center (Westbound)
- 6th Street and American Avenue
- 6th Street and Illinois Avenue
- 6th Street and Orange Avenue (Beaumont Civic Center)
- 6th Street and Egan Avenue
- Elm Avenue and 6th Street
- Beaumont Library
- Beaumont Avenue and 12th Street (Northbound)
- Beaumont Avenue and 13th Street (Southbound)
- Beaumont Avenue and Oak Valley Parkway (Mountain View Apartments)
- Pennsylvania Avenue and Oak Valley Parkway
- Pennsylvania Avenue and 13th Street
- Pennsylvania Avenue and 10th Street (Southbound)
- Pennsylvania Avenue and 8th Street
- 8th Street and Palo Alto Avenue
- Oak Valley Parkway and Gateway Drive
- Palmer Avenue and Morris Street
- Palmer Avenue and Armour Avenue
- Palmer Avenue and Jones Way
- Palmer Avenue and Harmon Heights
- Palmer Avenue and Trevino Trail
- Tukwet Canyon Pkwy and Sanders Street
- Tukwet Canyon Pkwy and Champions Drive
- Champions Drive and Ryders Cup Road
- Champions Drive and Bay Hill
- DeForge Community Park (Seneca Springs)
- Pennsylvania Avenue and 10th Street (Northbound)
- Cougar Way and Palm Avenue (Eastbound)
- Oak Valley Parkway and Cherry Avenue
- 6th Street and Xenia Avenue (Westbound)
- Beaumont Avenue and 9th Street
- CitiBank (Beaumont Ave)
- 8th Street and Xenia Avenue
- 1st Street and Highland Springs Avenue
- 6th Street and Michigan Avenue (Westbound)
- Oak Valley Parkway and Edeleweiss Drive (Eastbound)
- Starlight Avenue and Chenille Way
- Cherry Avenue and Oak Valley Parkway (Country Highlands)
- San Gorgonio Middle School (Cougar Way)
- Palm Avenue and Canyon Crest
- Three Rings Ranch Park (Brookside Ln)
- Manzanita Parkway and Brownie Way
- Seneca Springs and Lynn Avenue
- Seneca Springs and Malaga Avenue
- Seneca Springs and Tripoli Street
- Palm Avenue and Winter Pine Street
- Beaumont Ave and 7th St (Chamber of Commerce) - NB
- Oak View Drive and Cedarbrook Street
- Oak View Drive and Iris Street
- Oak View Dr and Golden Way
- Palm Avenue and 12th Street (Catholic Church)
- Calimesa Veterinarian
- Kaiser Redlands Medical Offices
- 10th Street and Beaumont Ave (Eastbound)
- Vineland Street and Ralph Road
- Redlands Transit Center (Westbound)
- Redlands Transit Center (Eastbound)
- Morgan Avenue and Monte Verde Drive
- Pennsylvania Avenue @ Beaumont Co-Op Apartments
- Xenia Avenue and Carnation Lane (Sundance Elementary)
- Oak Valley Parkway and Starlight Avenue (Westbound)
- 6th Street @ Food4Less (Eastbound)
- 4th St and B St (Rangel Park)
- Prosperity Wy and Distribution Wy (Amazon)
- 4th St @ KRB7 Amazon Warehouse
- 1st St and Beaumont Ave
- 3rd St and Pennsylvania Ave
- Maple Ave and 3rd St
- Tukwet Canyon Pkwy and Sorenstam Dr
- 4th St and Nicholas Rd (Lowe's)
- Oak Valley Pkwy and Sheridan Wy
- Cherry Festival Shuttle Stop (Stewart Park)
- Cherry Festival Shuttle Stop (Sports Park)
- 4th St and Elm Ave
- 4th St and Distribution Wy
- 4th St and Prime Dr
- 4th St and Nicholas Rd (Eastbound)
- Veile Ave and 4th St
- 1st St and Grace Ave
- Tukwet Canyon Pkwy and Josh Dr
- Tukwet Canyon Pkwy and Roxy Rd
- Beaumont Ave and 13th Street (Northbound)
- Crafton Hills College
- Sav-On Manufactured Homes (6th Street)
- Potrero Blvd and Olivewood Ave
- Palm Avenue & East 6th Street, Beaumont, CA, USA
- 6th Street and Magnolia Avenue (Wells Fargo Bank)
- Oak Valley Parkway and Palm Avenue (Fellowship Church)
- Beaumont Avenue and 10th Street (Northbound)
- Beaumont Avenue and 10th Street (Westbound)
- Casino Morongo
- Brookside Elementary (Oak View Drive)
- Cherry Valley Boulevard @ Cherry Tree Shoppe
- Beaumont Avenue and 12th Street (Southbound)
- Oak Valley Parkway and Potrero Boulevard
- Oak Valley Parkway and Apron Ln
- Oak Valley Plaza
- 8th Street and Highland Springs Avenue
- Calimesa Boulevard @ Stater Bros
- Loma Linda VA Hospital
- Palm Avenue and Birchwood Drive (Northbound)
- Cougar Way and Palm Avenue (Westbound)
- Cougar Way and Beaumont Avenue (Orchard Park Apartments)
- 10th Street and California Avenue
- Oak Valley Parkway @ Chatigny Recreation Center
- 8th Street and Pennsylvania Avenue
- 8th Street and Chestnut Avenue
- 8th Street and Maple Avenue
- 8th Street and Beaumont Avenue
- 8th Street and California Avenue (Beaumont Library)
- Brookside Avenue and Beaumont Avenue (Sports Park)
- Brookside Avenue and Lemon Avenue
- Brookside Avenue and Noble Street
- Cherry Avenue and Brookside Avenue
- Cherry Avenue and Mary Lane
- Oak Valley and Desert Lawn Drive
- Oak Valley and Linksman Drive
- Calimesa Boulevard @ Crown Village
- San Bernardino Transit Center
- Calimesa Blvd @ Dollar Tree
Over time
Overall score across the last 4 checks — down 0.1 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 84.1 | first check |
| 2026-07-30 | 84.0 | down 0.1 |
| 2026-07-31 | 84.1 | up 0.1 |
| 2026-08-01 | 84.0 | down 0.1 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall score fell 0.1 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.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning170 instances
170 of 170 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)
- Warning143 instances
143 of 151 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)
- Warning22 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)
- Warning1 instance
1 of 170 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
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
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · 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)
- Info2 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 153 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 170 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 5% 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 153 days.
- Accessible Not yet
- States wheelchair access on 5% 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.
- 22 of 151 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 153 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.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (5 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 5% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 170 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 91 / 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 61 / 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/beaumont-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.