Feed status · checked 2026-08-01
Lowell Regional Transit Authority (LRTA)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Massachusetts.
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 74 minutes ago; last changed 18 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
886 of 886 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
949 of 949 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
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.
⏱ A small file for most flat-fare systems.worth about +15 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
- 886 of 886 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
- 949 of 949 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
- The feed contains no fare information.
- Next action
- 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.
- 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.
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. · 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 183 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 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 4 kinds of issue across 106 instances (0 error, 62 warning, 44 informational).
Service data covers the next 183 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 13, 2, 17, 4).
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.
711 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Billerica Rd & Chelmsford St", "Burnham Rd & Florence St", "Main St & North St", 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.
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 886 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.
- 1 (green)
- 2 (purple)
- 3 (pink)
- 4 (teal)
- 5 (red)
- 6 (yellow)
- 7 (gray)
- 8 (blue)
- 9 (green)
- 10 (blue)
- 11 (black)
- 12 (yellow)
- 13 (green)
- 14 (purple)
- 15 (gray)
- 16 (pink)
- 17 (gray)
- 18 (yellow)
- 20 (orange)
| Route | Type | Line color |
|---|---|---|
| 15-16 Chelmsford Center/Westford via Rtes. 129/110 | Bus | gray (no shape in feed) |
| 1 Christian Hill | Bus | green |
| 2 Belvidere | Bus | purple |
| 3 South Lowell | Bus | pink |
| 4 Highlands via Stevens | Bus | teal |
| 5 Westford Street/Drum Hill | Bus | red |
| 6 Broadway/UMass Lowell | Bus | yellow |
| 7 Pawtucketville/UMass Lowell North | Bus | gray |
| 8 Centralville | Bus | blue |
| 9 Lowell Circulator | Bus | green |
| 10 Dracut/Tyngsboro | Bus | blue |
| 11 IRS/Raytheon via Rte. 133 | Bus | black |
| 12 Tewksbury via Rte. 38/Wilmington Train Station | Bus | yellow |
| 13 Billerica via Edson | Bus | green |
| 14 Burlington Mall/Lahey Clinic | Bus | purple |
| 15 Chelmsford/Westford via Rte. 129/110 | Bus | gray |
| 16 Chelmsford via Chelmsford Street | Bus | pink |
| 17 North Chelmsford via Middlesex Street | Bus | gray |
| 18 Downtown Shuttle | Bus | yellow |
| 19 Pheasant Lane Mall via Middlesex Street | Bus | white (no shape in feed) |
| 20 Orange Line/UMass Lowell North | Bus | orange |
List every stop
- Billerica Rd & Chelmsford St
- Burnham Rd & Florence St
- Outside Mitre Facility
- Outside Mitre Facility
- Main St & North St
- Chandler St & Lee St
- Massachusetts General Hospital
- Beth Israel Deaconess Medical Center East Campus
- Beth Israel Deaconess Medical Center West Campus
- Dana-Farber Cancer Institute
- Brigham and Women's Hospital
- Veterans Affairs Boston Healthcare System Jamaica Plain
- Lakeview Ave & Litchfield Ave
- St. Elizabeth's Medical Center
- Main Street & South Street
- East St. (Shelter)
- Kennedy Center Departure
- Kennedy Center Terminal
- North Billerica Train Station
- Westminster Village Apts
- School St and Westford (Outbound)
- 99 Restaurant (Outbound)
- Princeton & Baldwin St
- Wood St & Redwood Ln
- Swan St and Industrial Ave E
- The Talbot School
- The Talbot School
- Middlesex Turnpike & Marshall St (IB)
- Concord Rd & Campbell Rd (IB)
- 2nd Ave & South Ave (OB)
- Tufts Medicine Lowell General Hospital – Tewksbury
- Middlesex St & Samuel St
- University Suites
- University Suites
- Tsongas Arena
- Tsongas Arena
- 16 Boston Rd
- 16 Carlisle
- 160 Middlesex
- Tyngsboro Rd & Cross St
- Marshall's Plaza
- Frost Rd & Fletcher Dr
- Burlington Mall Rd. and Lexington St.
- Groton Rd & Dunstable Rd
- Lakeview Apartments Tyngsborough
- Wilson St & Billerica Rd
- Nesmith St & Mansur St
- University Ave & White St
- Lakeview Ave & Tennis Plaza Rd
- Middlesex St & Cornell St
- Lakeview Ave & Tennis Plaza Rd
- Nashoba Tech
- Middlesex Tpk & 4th Ave
- Middlesex St & Cornells St
- 175 Littleton
- Lakeview Ave & Pointsetta Ave
- 179 Littleton
- Ludlam St & Dana St
- Lakeview Ave & Pointsetta Ave
- 180 Tyngsboro
- Lakeview Ave & St Paul St
- Groton Rd & Scotty Hollow Dr
- Tyngsboro Rd & Wellman Ave
- Middlesex St Middlesex Plaza
- Gorham St & Summer St
- Princeton St & Brouilette St
- Pine St & Stevens St
- Woburn St & Easton St
- Lawrence St & Cady St
- Main St & Wisser St
- Middlesex St & Dingwell St
- Nashoba Tech
- Boston Rd & Amherst St
- Liberty St & Grace St
- Market Basket Plaza
- Wentworth Ave & Hovey St
- Andover St & Radcliff Rd
- Broadway St & Suffolk St
- Woburn St & Grafton St
- Middlesex St & Nelson St
- Middlesex St & Thorncliff Ave
- Lakeview Ave & Pine St
- Middlesex Turnpike & Burlington Mall Rd
- Rogers St & Park Ave
- Lakeview Ave & Mill St
- Burnham Rd & Russell St
- Treble Cove Plaza (199 Boston Rd)
- 199 Chelmsford
- Cross Point Tower
- Triangle Store (2 Main St)
- Boston Rd & Amherst St
- Drum Hill Rd at Enterprise Bank
- Gorham St & Lincoln St
- Westford St & Parkhurst Rd
- Treble Cove Plaza
- 200 Innovation Dr
- University Ave & 4th Ave
- W 6th St & Bunker Hill Ave
- Pollard St & Salem Rd
- 20-26 Crosby Drive
- 203 Littleton
- Pleasant St & Coventry Dr
- Gorham St & London St
- Billerica Rd & Apollo Dr
- Chelmsford Rd & Rangeway Rd
- 21 Drum Hill
- Vinal Square
- Mammoth Rd & Ross Ave
- Main St & Hill St
- Pleasant St & Coventry Dr
- Chelmsford St & Sylvan Ave
- Central St & Jackson St
- Chelmsford Rd & Finnway St
- Chelmsford St & Independence Dr
- 221 Boston Rd
- 224 Littleton Road
- 228 Billerica Rd (Atrius Health)
- Andover St & Nesmith St
- Lakeview Ave & Pinehurst Ave
- Humphrey St & Pemberton St
- Nesmith St & Sherman St
- Billerica Rd & Progress Ave
- River Rd & Burnham Rd
- Bridge St & 18th St
- Liberty St & S Walker St
- Plain St & Payton St
- University Ave & 6th Ave
- Andover St & Park St
- Ideal Tape & Middlesex St
- Branch St & Branch Pl
- Brattle St & Douglas Rd
- Main St & Roosevelt Rd
- 25 Drum Hill Rd
- Main St & Hoover Rd
- Main St & Colonial Dr
- Dalton Rd & Field St
- Princeton St & Harvard St
- 254 Billerica Rd
- 255 Chelmsford St
- 255 North Rd
- 255 Rogers Street
- Old Meadow Rd & Lamb St
- V.A. Clinic (263 Industrial Ave)
- East St & Chandler St
- W 6th St & Beaulieu St
- Gorham St & Manchester St
- Boston Rd & Marshall Rd
- Boston Rd & Bridge St
- 273 Littleton
- 273 Main
- Market Basket Senior Center
- Chelmsford Center
- High St & Andover St
- Andover St & Mansion Dr
- 28-30 Crosby Drive
- Gorham St & Manchester St
- Stevens St & Pine St
- Billerica Rd & Elliot St
- High St & Andover St
- Littleton & Powers Rd
- Chelmsford & Glen Ave
- Littleton Rd & Powers Rd
- Gorham St & Riverneck Rd
- Marinel Ave & Dunstable Rd
- Kidder Rd & Littleton Rd
- Lawrence St & Billerica St
- Varnum Ave & Avalon St
- 291 Douglas
- Woburn St & Jean Ave
- Billerica Center (297 Boston Rd)
- Chelmsford St & Glen Ave
- Brookside St & Varnum Ave
- Billerica Rd & Elliot St
- Chelmsford St & Shaw St
- Kidder Rd & Littleton Rd
- 109 Arlington
- Billerica Center
- University Ave & 7th Ave
- Rogers St & Waverly Ave
- 31 Littleton
- Hannaford
- 313 Littleton
- Westford St & Hastings St
- Boston Rd & Collins Rae Ln
- Hildreth St & Aiken Ave
- 320 Nesmith
- University Ave & 7th Ave
- High St & Oak St
- Gorham St & Highland St
- Mammoth Rd & W Meadow Rd
- Concord Rd & Richardson St
- Billerica Rd & Omni Way
- 330 Boston Rd
- Douglas Rd & Windward Rd
- Littleton Rd & Robbins Rd
- Tyngsboro Rd & Locust St
- Concord Rd & Blanchard Ave
- Littleton Rd & Robbins Rd
- 334 Main
- Tyngsboro Rd & Stewart St
- Main St & Middlesex Ave
- Bridge St & 2nd St
- Lakeview Ave & Aiken Ave.
- 34 Central Square
- 345 North Rd
- Woburn St & Canterbury St
- Main St & Colonial Dr
- Andover St & Mansion Dr
- Chestnut Street Burlington
- 355 Littleton
- Lowell St & Bellevue Rd
- Brick Kiln Rd & Sprague Ave
- Gorham St & Hobson St
- 360 Littleton
- Main St & Veranda Ave
- Boston Rd & Farmers Ln
- 11 Technology
- 364 Littleton
- Stevens St & D St
- Rogers St & Wellington Ave
- Billerica Town Hall
- Cambridge St & Van Norden Rd
- Littleton Rd & Beth Ann Dr
- Lowell St & Tessier Dr
- Gorham St & Blossom St
- Hildreth St & Essex St
- Woburn St & Commonwealth Ave
- Main St & Colab Rd
- High St & Porter St
- Cambridge St & Four Acre Dr
- High St & Porter St
- Billerica Town Hall
- Brick Kiln Rd & Moore St
- Pollard St & Waterview Ave
- Hannafords Plaza
- Westford St & Gates St
- Varnum Ave & Barbara Terrace
- Chelmsford St & Factory St
- Lakeview Ave & Frost Rd
- 4 Technology Park Dr
- Tyngsboro Rd & Nashua Rd
- Mission Rd & Rte. 3A
- Lakeview Ave & Cricones Way
- Parkhurst Rd & Smith St
- Pollard St & Call St
- 400 Littleton
- Andover St & Cobleigh Dr
- Merrimack St & Cardinal O Connell Pkwy
- The Center at Innovation Drive
- Main St & Colab Rd
- and 636 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 78.4 | first check |
| 2026-07-30 | 78.4 | no change |
| 2026-07-31 | 78.4 | no change |
| 2026-08-01 | 78.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning949 instances
949 of 949 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)
- Warning886 instances
886 of 886 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)
- Warning62 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
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 · 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
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 183 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 949 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 183 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 62 of 886 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 183 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 90 / 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 45 / 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/lowell-regional-transit-authority-lrta/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.