Feed status · checked 2026-11-21

Lowell Regional Transit Authority (LRTA)

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

Service mode Bus

42.5 / 100

unchanged since 2026-11-20

Cataloged in Massachusetts.

Feed expiredAccessibility gapsRealtime 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 7 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

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

1658 of 1658 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 1,658 stops in the feed.

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

Fix 03

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

1109 of 1109 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 1,109 trips in the feed.

⏱ A default or per-trip field in your export.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.
  • Massachusetts 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.

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.

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

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown

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

  3. Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    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. 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 7 days ago.
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 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.

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.

Lowell Regional Transit Authority (LRTA)’s published feed lists 22 bus routes, 1,109 scheduled trips and 1,658 stops. The published file last changed on 2026-10-14.

Score by category

Correctness71.0 / 100

The MobilityData validator flagged 7 kinds of issue across 129 instances (0 error, 127 warning, 2 informational).

Freshness0.0 / 100

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

Rider experience36.6 / 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.

3 accessibility depth signals

  • 2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 13).

    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.

  • 1308 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Boys & Girls", "Stevens&Jenness", "River&Trull", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

  • This feed models stations or entrances but has no pathways.txt and levels.txt.

    Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.

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

  • 1 (green)
  • 10 (blue)
  • 11 (black)
  • 12 (yellow)
  • 13 (green)
  • 14 (purple)
  • 15 (gray)
  • 16 (pink)
  • 17 (gray)
  • 18 (yellow)
  • 19 (white)
  • 2 (purple)
  • 20 (orange)
  • 21 (black)
  • 3 (pink)
  • 4 (teal)
  • 5 (red)
  • 6 (yellow)
  • 7 (gray)
  • 8 (blue)
  • 9 (green)
Routes in Lowell Regional Transit Authority (LRTA)'s feed
RouteTypeLine color
1 Christian HillBusgreen
10 Dracut/TyngsboroBusblue
11 IRS/Raytheon via Rte. 133Busblack
12 Tewksbury via Rte. 38/Wilmington Train StationBusyellow
13 Billerica via EdsonBusgreen
14 Burlington Mall/Lahey ClinicBuspurple
15 Chelmsford/Westford via Rte. 129/110Busgray
156 Chelmsford Center/Westford via Rtes. 129/110Busgray (no shape in feed)
16 Chelmsford via Chelmsford StreetBuspink
17 North Chelmsford via Middlesex StreetBusgray
18 Downtown ShuttleBusyellow
19 Pheasant Lane Mall via Middlesex StreetBuswhite
2 BelvidereBuspurple
20 Orange Line/UMass Lowell NorthBusorange
21 Wilmington Train Station/Burlington MallBusblack
3 South LowellBuspink
4 Highlands via StevensBusteal
5 Westford Street/Drum HillBusred
6 Broadway/UMass LowellBusyellow
7 Pawtucketville/UMass Lowell NorthBusgray
8 CentralvilleBusblue
9 Lowell CirculatorBusgreen
List every stop
  • Vinal Square
  • Bill&Chelms
  • Burnham&Florence
  • Outside Mit Fac
  • Outside Mit Fac
  • Main&North
  • Lake&Litchfield
  • South Street
  • North Bill T.S.
  • Westminster
  • School St
  • 99 Restaurant
  • Baldwin St
  • Wood&Redwood
  • The Talbot School
  • Talbot School
  • Middlesex & Marshall
  • Concord & Campbell
  • 2nd Ave & South Ave
  • Middlesex&Samuel
  • University Suites
  • University Suites
  • Tsongas Arena
  • Tsongas Arena
  • Lowell High School
  • 16 Boston Rd
  • 16 Carlisle
  • 160 Middlesex
  • Tyngsboro&Cross
  • Marshall's Plaza
  • Frost&Fletcher
  • Lexington St.
  • Groton&Dunstable
  • Apt Tyngsborough
  • Wilson&Billerica
  • Nesmith&Mansur
  • University&White
  • Lake&Tennis Pla
  • Mid&Cornell
  • Lake&Tennis Pla
  • Nashoba Tech
  • Mid Tpk&4th
  • Mid&Cornells
  • 175 Littleton
  • Lake&Pointsetta
  • 179 Littleton
  • Ludlam&Dana
  • Lake&Pointsetta
  • 180 Tyngsboro
  • Lake&St Paul
  • Groton&Scotty
  • Tyngs&Wellman
  • Vinal Square
  • Gorham&Summer
  • Prin&Brouilette
  • Pine&Stevens
  • Woburn&Easton
  • Lawrence&Cady
  • Main&Wisser
  • Mid&Dingwell
  • Nashoba Tech
  • Boston&Amherst
  • Liberty&Grace
  • Mkt Basket Plaza
  • Wentworth&Hovey
  • Andover&Radcliff
  • Broadway&Suffolk
  • Woburn&Grafton
  • Middlesex&Nelson
  • Mid&Thorncliff
  • Lake&Pine
  • Rogers&Park
  • Lake&Mill
  • Burnham&Russell
  • Treble C. Plaza
  • 199 Chelmsford
  • Cross Point Twr
  • Triangle Store
  • Boston&Amherst
  • Drum HL Rd
  • Gorham&Lincoln
  • West&Parkhurst
  • Treble C. Plaza
  • 200 Network Dr
  • University&4th
  • W 6th&Bunker HL
  • Pollard&Salem
  • 203 Littleton
  • Pl&Coventry
  • Gorham&London
  • Billerica&Apollo
  • Chelms&Rangeway
  • 21 Drum Hill
  • Tyngsboro Center
  • Mammoth&Ross
  • Main&Hill
  • Pl&Coventry
  • Chelms&Sylvan
  • Central&Jackson
  • Chelms&Finnway
  • Che&Independence
  • 221 Boston Rd
  • 224 Litt Rd
  • Atrius Health
  • Andover&Nesmith
  • Lake&Pinehurst
  • Humph&Pemberton
  • Nesmith&Sherman
  • Bill&Progress
  • River&Burnham
  • Bridge&18th
  • Liberty&S Walker
  • Plain&Payton
  • University&6th
  • Andover&Park
  • Ideal Tape&Mid
  • Branch&Branch Pl
  • Brattle&Douglas
  • Main&Roosevelt
  • 25 Drum Hill Rd
  • Main&Hoover
  • Colonial Dr
  • Dalton&Field
  • Prin&Harvard
  • 254 Billerica Rd
  • 255 Chelmsford
  • 255 North Rd
  • 255 Rogers St
  • Old Meadow&Lamb
  • V.A. Clinic
  • W 6th&Beaulieu
  • Gor&Manchester
  • Boston&Marshall
  • Boston&Bridge
  • 273 Littleton
  • 273 Main
  • Mkt Bas Senior
  • High&Andover
  • Andover&Mansion
  • Gor&Manchester
  • Stevens&Pine
  • Billerica&Elliot
  • High&Andover
  • Littleton&Powers
  • Chelmsford&Glen
  • Littleton&Powers
  • Mari&Dunstable
  • Kidder&Littleton
  • Law&Bill
  • Var&Avalon
  • 291 Douglas
  • Woburn&Jean
  • Bill(297 Boston)
  • Chelmsford&Glen
  • Brookside&Varnum
  • Billerica&Elliot
  • Chelmsford&Shaw
  • Kidder&Littleton
  • 109 Arlington
  • Billerica Center
  • University&7th
  • Rogers&Waverly
  • 31 Littleton
  • Hannaford
  • 313 Littleton
  • West&Hastings
  • Bos&Collins Rae
  • Hildreth&Aiken
  • 320 Nesmith
  • Pheasant Lane
  • University&7th
  • High St & Oak St
  • Low Superior Ct
  • Mammoth&W Meadow
  • Con&Richardson
  • Bill&Omni Way
  • 330 Boston Rd
  • Douglas&Windward
  • Litt&Robbins
  • Tyngsboro&Locust
  • Con&Blanchard
  • Litt&Robbins
  • 334 Main
  • Tyngs&Stewart
  • Main&Middlesex
  • Bridge&2nd
  • Aiken Av
  • 34 Central Sq
  • 345 North Rd
  • Wob&Canterbury
  • Colonial Dr
  • Andover&Mansion
  • Chest Burlington
  • 355 Littleton
  • Lowell&Bellevue
  • Brick&Sprague
  • Low Superior Ct
  • 360 Littleton
  • Main&Veranda
  • Boston&Farmers
  • 11 Technology
  • 364 Littleton
  • Stevens&D
  • Rogers&Welling
  • Bill Town Hall
  • Camb&Van Norden
  • 62 & Boutwell
  • 62 & Boutwell
  • Litt&Beth Ann
  • Lowell&Tessier
  • 62&Deming way
  • Gorham&Blossom
  • Hildreth&Essex
  • Wob&Comwealth
  • Main&Colab
  • 62&Deming way
  • High&Porter
  • Camb&Four Acre
  • High&Porter
  • Bill Town Hall
  • Brick Kiln&Moore
  • Pollard&Water
  • Hannafords Plaza
  • Westford&Gates
  • Var&Barbara Ter
  • Chelms&Factory
  • Lake&Frost
  • 4 Tech Park
  • Tyngsboro&Nashua
  • Mission&Rte. 3A
  • Lake&Cricones
  • Parkhurst&Smith
  • Pollard&Call
  • 400 Littleton
  • Andover&Cobleigh
  • Merr&Cardinal OC
  • 495 Business Ctr
  • Main&Colab
  • Mid Tpk&Concord
  • Boston&Andover
  • 406 Lowell St
  • Boston&Grace
  • Village Square
  • And&Pentucket
  • Stevens&B
  • And&Longmeadow
  • High&Sherman
  • High&Sherman
  • Bridge&W 4th
  • And&Pentucket
  • and 1408 more (see the full list on the map or in the GeoJSON)

Over time

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

2026-11-09: 42.52026-11-10: 42.52026-11-11: 42.52026-11-12: 42.52026-11-13: 42.52026-11-14: 42.52026-11-15: 42.52026-11-16: 42.52026-11-17: 42.52026-11-18: 42.52026-11-19: 42.52026-11-20: 42.52026-11-21: 42.5
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0942.5 first check
2026-11-1042.5 no change
2026-11-1142.5 no change
2026-11-1242.5 no change
2026-11-1342.5 no change
2026-11-1442.5 no change
2026-11-1542.5 no change
2026-11-1642.5 no change
2026-11-1742.5 no change
2026-11-1842.5 no change
2026-11-1942.5 no change
2026-11-2042.5 no change
2026-11-2142.5 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-09 to 2026-11-21 (13 checks)ed08d1ea9f1e2026-11-14Current rubric: see the trend above
2026-10-14 to 2026-11-06 (24 checks)ed08d1ea9f1e2026-11-14F, 42.5 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-10-02 to 2026-10-13 (12 checks)f3cc117bc6ae2027-01-31C, 78.4 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-10-01 (65 checks)f3cc117bc6ae2027-01-31C, 78.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-14 to 2026-07-24 (8 checks)f3cc117bc6ae2027-01-31C, 78.4 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-13 (25 checks)f211aef5e23b2026-07-31F, 59.2 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed over time

On 2026-11-09 this feed started at grade F. On 2026-11-14 feed expired. As of 2026-11-21 it holds grade F.

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

  • 2026-11-14 Feed expired.

Everything we checked

15 findings, ordered by severity.

Show every finding
  • Error1 instance

    Service data ended 7 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)

  • Warning1658 instances

    1658 of 1658 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)

  • Warning1109 instances

    1109 of 1109 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)

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

  • Warning66 instances

    66 of 1109 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)

  • Warning17 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning13 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 for stop_without_stop_time · 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

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

    Finding code: stops_match_shape_out_of_order · 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)

  • Warning1 instance

    This feed models stations or entrances but has no pathways.txt.

    Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.

    Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)

    Finding code: scorecard_station_no_pathways · Read the fix guide for scorecard_station_no_pathways · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Info1 instance

    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)

  • Info1 instance

    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 for unknown_column · See MobilityData GTFS Validator rules (opens the validator rules 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 18 hours ago; last changed 38 days 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 Not ready

Resolve this before you certify on the D-10. Service data expired 7 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 7 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 1109 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

Two requirements remain for this feed to earn the conformance mark. Service data expired 7 days ago. 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 Not yet
Service data expired 7 days ago.
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.

  • 13 of 829 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.

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

Similar feeds in Massachusetts

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

Lowell Regional Transit Authority (LRTA): GTFS feed quality grade F, 42.5 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/lowell-regional-transit-authority-lrta/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.