Feed status · checked 2026-11-21

Loop Trolley

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

Service mode Bus

55.8 / 100

unchanged since 2026-11-20

Cataloged in Missouri.

Feed expiredRealtime not yet published

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

Top things to fix

Fix 01

Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool

Service data ended 27 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

This one is about the feed as a whole, so there is no share of it to count.

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

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.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Fix 03

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

This one is about the feed as a whole, so there is no share of it to count.

⏱ Two fields, set once in export settings.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.
  • Missouri 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_feed_expired

    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_no_fare_data

    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_feed_info_dates

    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 was 27 days ago.
Published accessibility data
Accessibility information is stated for 100% of stops and 100% 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.

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

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.

Loop Trolley’s published feed lists 1 bus route, 51 scheduled trips and 10 stops. The published file has not changed since our first check on 2026-06-19.

Score by category

Correctness83.0 / 100

The MobilityData validator flagged 4 kinds of issue across 114 instances (0 error, 63 warning, 51 informational).

Freshness0.0 / 100

Service data ended 27 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience62.5 / 100

100% of stops state wheelchair accessibility (60% marked accessible, 40% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility100 / 100

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

1 accessibility depth signal

  • 1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("LELAND AVE TROLLEY STOP").

    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 10 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.

  • 3603 (white)
Routes in Loop Trolley's feed
RouteTypeLine color
3603 Loop TrolleyBuswhite
List every stop
  • MISSOURI HISTORY MUSEUM TROLLEY STOP
  • THE PAGEANT TROLLEY STOP
  • U CITY PUBLIC LIBRARY TROLLEY STOP
  • DELMAR LOOP METROLINK TROLLEY STOP
  • CITY LIMIT TROLLEY STOP
  • LELAND AVE TROLLEY STOP
  • DELMAR AND DEBALIVIERE TROLLEY STOP
  • CROSSROADS SCHOOL TROLLEY STOP
  • FOREST PARK DEBALIVIERE METROLINK TROLLEY STOP
  • HAMILTON TROLLEY STOP

Over time

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

2026-10-02: 61.72026-10-03: 61.32026-10-04: 60.82026-10-05: 60.42026-10-06: 60.02026-10-07: 59.62026-10-08: 59.22026-10-09: 58.82026-10-10: 58.32026-10-11: 57.92026-10-12: 57.52026-10-13: 57.12026-10-14: 56.72026-10-15: 56.32026-10-16: 55.82026-10-17: 55.82026-10-18: 55.82026-10-19: 55.82026-10-20: 55.82026-10-21: 55.82026-10-22: 55.82026-10-23: 55.82026-10-24: 55.82026-10-25: 55.82026-10-26: 55.82026-10-27: 55.82026-10-28: 55.82026-10-29: 55.82026-10-30: 55.82026-10-31: 55.82026-11-01: 55.82026-11-02: 55.82026-11-04: 55.82026-11-05: 55.82026-11-06: 55.82026-11-09: 55.82026-11-10: 55.82026-11-11: 55.82026-11-12: 55.82026-11-13: 55.82026-11-14: 55.82026-11-15: 55.82026-11-16: 55.82026-11-17: 55.82026-11-18: 55.82026-11-19: 55.82026-11-20: 55.82026-11-21: 55.8
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-10-0261.7 first check
2026-10-0361.3 down 0.4
2026-10-0460.8 down 0.5
2026-10-0560.4 down 0.4
2026-10-0660.0 down 0.4
2026-10-0759.6 down 0.4
2026-10-0859.2 down 0.4
2026-10-0958.8 down 0.4
2026-10-1058.3 down 0.5
2026-10-1157.9 down 0.4
2026-10-1257.5 down 0.4
2026-10-1357.1 down 0.4
2026-10-1456.7 down 0.4
2026-10-1556.3 down 0.4
2026-10-1655.8 down 0.5
2026-10-1755.8 no change
2026-10-1855.8 no change
2026-10-1955.8 no change
2026-10-2055.8 no change
2026-10-2155.8 no change
2026-10-2255.8 no change
2026-10-2355.8 no change
2026-10-2455.8 no change
2026-10-2555.8 no change
2026-10-2655.8 no change
2026-10-2755.8 no change
2026-10-2855.8 no change
2026-10-2955.8 no change
2026-10-3055.8 no change
2026-10-3155.8 no change
2026-11-0155.8 no change
2026-11-0255.8 no change
2026-11-0455.8 no change
2026-11-0555.8 no change
2026-11-0655.8 no change
2026-11-0955.8 no change
2026-11-1055.8 no change
2026-11-1155.8 no change
2026-11-1255.8 no change
2026-11-1355.8 no change
2026-11-1455.8 no change
2026-11-1555.8 no change
2026-11-1655.8 no change
2026-11-1755.8 no change
2026-11-1855.8 no change
2026-11-1955.8 no change
2026-11-2055.8 no change
2026-11-2155.8 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-10-02 to 2026-11-21 (48 checks)4c0fd0987c702026-10-25Current rubric: see the trend above
2026-07-25 to 2026-10-01 (65 checks)4c0fd0987c702026-10-25D, 62.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-14 to 2026-07-24 (8 checks)4c0fd0987c702026-10-25C, 77.1 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-13 (25 checks)4c0fd0987c702026-10-25C, 77.1 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed over time

On 2026-10-02 this feed started at grade D. On 2026-10-07 the grade moved from D to F. On 2026-10-25 feed expired. As of 2026-11-21 it holds grade F.

A plain-language history of this feed, newest first.

  • 2026-10-25 Feed expired.
  • 2026-10-07 Grade went D to F.

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Error1 instance

    Service data ended 27 day(s) ago.

    When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

    Fix: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)

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

  • Warning61 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    A file GTFS asks for (usually feed_info.txt) is missing.

    feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

    Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

    Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Finding code: stop_too_far_from_shape · Read the fix guide for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    feed_info.txt is missing its start/end dates (the file itself is absent)

    Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

    Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · See MobilityData GTFS Validator rules (opens the validator rules 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)

  • Info51 instances

    Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info10 instances

    About 10 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

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

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

How we measured this

Checked for changes 13 days ago; last changed 154 days ago.

The latest run did not download this feed: the host's robots.txt could not be read, and this scorecard does not request a feed until it can. The grade shown was measured on 2026-11-21.

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

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. Service data expired 27 days ago, so FTA would find the link out of date.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Not ready
Service data expired 27 days ago, so FTA would find the link out of date.
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 51 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. Service data expired 27 days ago.

Valid Met
Passes validation with no errors.
Current Not yet
Service data expired 27 days ago.
Accessible Met
States wheelchair access on 100% of stops and 100% of trips.

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.

Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.

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 83 / 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 0 / 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 62 / 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 Missouri portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Missouri

Other scorecards in Missouri, 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.

Loop Trolley: GTFS feed quality grade F, 55.8 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/metro-st-louis-2035/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.