Feed status · checked 2026-11-21

Bell Gardens Trolley

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

78.1 / 100

unchanged since 2026-11-20

Cataloged in California.

Covers 365 daysAccessibility gapsRealtime not yet published

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Checked 2026-11-08: the feed URL on file had stopped working, so this record now tracks ips-systems.com, the current address Transitland lists for this feed. The agency name and service area in that file match this record. Grades dated before this change came from an older Mobility Database mirror copy.

Top things to fix

Fix 01

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

52 of 52 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.

Fixing this covers all 52 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

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

30 of 30 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 30 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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.

30 of 30 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

Fixing this covers all 30 trips in the feed.

⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • California as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
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.

  1. Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

  3. Fix 03 · Read the fix guide for scorecard_missing_headsigns

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

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 365 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
No fare information is published in the feed.
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 your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

About this feed

Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.

Bell Gardens Trolley’s published feed lists 1 bus route, 30 scheduled trips and 52 stops. Its service dates run from 2026-11-21 through 2027-11-21. The published file last changed on 2026-11-21.

Score by category

Correctness100.0 / 100

The validator found no problems in this feed. That is rare and worth celebrating.

Freshness100.0 / 100

Service data covers the next 365 days.

Rider experience30.0 / 100

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 not published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 49 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Bell Gardens Park - 6662 Loveland St", "Market Place - 6901 Eastern Av. (West Side)", "Ford Park - 7800 Scout Av.", 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.

Realtime qualityNot yet measured

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 52 stops.

Skip to route and stop data

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.

  • 130 (green)
Routes in Bell Gardens Trolley's feed
RouteTypeLine color
130 Monday-SaturdayBusgreen
List every stop
  • Bell Gardens Park - 6662 Loveland St
  • Market Place - 6901 Eastern Av. (West Side)
  • Ford Park - 7800 Scout Av.
  • City Hall - 7100 Garfield Av.
  • S/E corner Emil Av. and Foster Bridge
  • N/E corner Foster Bridge and Chalet Dr.
  • N/W corner Chalet Dr. and Gage Av.
  • N/W corner Gage Av. and Emil Av.
  • N/W corner Gage Av. and Perry Rd.
  • N/E corner Gage Av. and Garfield Av.
  • N/E corner Gage Av. and Darwell Av.
  • N/W corner Gage Av. and Jaboneria Rd.
  • N/W corner Gage Av. and Colmar Av.
  • N/W corner Gage Av. And El Selinda
  • S/W corner Eastern Av. and Gage Av.
  • N/W corner Eastern Av. and Lubec St.
  • S/W corner Eastern Av. and Florence Av.
  • N/W corner Eastern Av. and Live Oak St.
  • N/W corner Eastern Av. and Clara St.
  • S/W corner Jaboneria Rd. and Quinn St.
  • N/E corner Jaboneria Rd. and Muller St.
  • N/W corner Eastern Av. and Cecilia St.
  • East side - 8450 Garfield Av.
  • N/E corner Garfield Av. and Fostoria St.
  • East side - 8040 Garfield Av.
  • N/E corner Park Lane and Garfield Av.
  • N/W corner Clara St. and Emil Av.
  • N/E corner Clara St. and Kress Av.
  • N/E corner Clara St. and Garfield Av.
  • N/E corner Clara St. and Ira Av.
  • N/E corner Clara St. and Gephart Av.
  • N/E corner Jaboneria Rd. and Clara St.
  • N/W corner Florence Av. and Jaboneria Rd.
  • N/E corner Florence Av. and El Selinda Av.
  • Toys R Us - 7102 Eastern Av.
  • 6950 Eastern Av.
  • S/E corner Lubec St. and Eastern Av.
  • S/W corner Lubec St. and El Selinda Av.
  • S/W corner Lubec St. and Jaboneria Rd.
  • S/E corner Jaboneria Rd. and Florence Av.
  • S/W corner Florence Av. and Garfield Av.
  • Super A - 6380 Florence Av.
  • S/W corner Florence Av. and Emil Av.
  • N/E corner Scout Av. and Florence Av.
  • 6891 Florence Pl.
  • 6713 Florence Pl.
  • N/E corner Florence Pl. and Perry Rd.
  • S/E corner Garfield Av. And Loveland St.
  • South Scout at Emil side
  • S/E corner Scout at Clara
  • Eastside Jaboneria Rd. North off Priory
  • S/W corner Ludell & El Selinda Av.

Over time

Overall score across the last 13 checks — unchanged since 2026-11-20.

2026-11-09: 78.12026-11-10: 78.12026-11-11: 78.12026-11-12: 78.12026-11-13: 78.12026-11-14: 78.12026-11-15: 76.22026-11-16: 78.12026-11-17: 78.12026-11-18: 78.12026-11-19: 78.12026-11-20: 78.12026-11-21: 78.1
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0978.1 first check
2026-11-1078.1 no change
2026-11-1178.1 no change
2026-11-1278.1 no change
2026-11-1378.1 no change
2026-11-1478.1 no change
2026-11-1576.2 down 1.9
2026-11-1678.1 up 1.9
2026-11-1778.1 no change
2026-11-1878.1 no change
2026-11-1978.1 no change
2026-11-2078.1 no change
2026-11-2178.1 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-21bee77dca456f2027-11-21Current rubric: see the trend above
2026-11-20dd03545de5ab2027-11-20Current rubric: see the trend above
2026-11-19a003fce964602027-11-19Current rubric: see the trend above
2026-11-189753018a32202027-11-18Current rubric: see the trend above
2026-11-17b117d1654b992027-11-17Current rubric: see the trend above
2026-11-167c84b649098c2027-11-16Current rubric: see the trend above
2026-11-15170566a3e46e2027-11-15Current rubric: see the trend above
2026-11-141e9ae0ad889f2027-11-14Current rubric: see the trend above
2026-11-137947831f51e32027-11-13Current rubric: see the trend above
2026-11-122b975076f2352027-11-12Current rubric: see the trend above
2026-11-11f97aa2d8cc3e2027-11-11Current rubric: see the trend above
2026-11-107fe1d28c59e12027-11-10Current rubric: see the trend above

Showing the 12 most recent of 17 periods.

Everything we checked

4 findings, ordered by severity.

Show every finding
  • Warning52 instances

    52 of 52 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning30 instances

    30 of 30 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning30 instances

    30 of 30 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.

    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 for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

    Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)

How we measured this

Checked for changes 18 hours ago; last changed 18 hours ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

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.5, validator 8.0.1.

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 365 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 30 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

One requirement remains for this feed to earn 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 365 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 364 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 (4 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 0% of stops and 0% of trips.

  • Meets shapes.txt with a shape for every trip

    All 30 trips have a shape in shapes.txt.

  • Gap Fare data published, or the service marked fare-free

    No fare data is published.

Correctness 100 / 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 30 / 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.

Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in California

Other scorecards in California, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Bell Gardens Trolley: GTFS feed quality grade C, 78.1 of 100, checked 2026-11-21. GTFS 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/bell-gardens-trolley/2026-11-21.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-11-21. 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.