Feed status · checked 2026-08-01
Hillsborough Area Regional Transit (HART)
Based on the feed this agency publishes
Service mode Tram + Bus
down 1.7 since 2026-07-31
Catalogued in Florida.
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 76 minutes ago; last changed 41 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 6 snapshots.
- 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
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 14 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +66 points in its category
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +50 points in its category
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +50 points in its category
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
- Service data runs out in 14 day(s).
- Next action
- Re-export with a validity window that reaches at least 60 days out.
- 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 trip updates realtime feed failed during sampling.
- Next action
- Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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 vehicle positions realtime feed failed during sampling.
- Next action
- Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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.
Re-export with a validity window that reaches at least 60 days out. · Read the fix guide
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. Self-check a feed before you publish.
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
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. Self-check a feed before you publish.
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
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. 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 14 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
- Fare information is published using GTFS Fares v1.
- Realtime information
- No realtime feed was reachable during sampling.
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.
Score by category
The MobilityData validator flagged 4 kinds of issue across 90 instances (0 error, 90 warning, 0 informational).
Service data runs out in 14 day(s). Publish an updated feed soon or riders will lose trip planning.
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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
2266 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("50th St @ Palm River Rd", "Nebraska Av @ Twiggs St", "Nebraska Ave @ Cass 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.
Fares are applied to trips.
Sampled 6 times: 0 of 2 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 2315 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)
- 10 (green)
- 12 (green)
- 14 (green)
- 15 (green)
- 16 (green)
- 19 (green)
- 24 (red)
- 25 (red)
- 275 (red)
- 30 (green)
- 31 (green)
- 32 (green)
- 33 (green)
- 34 (green)
- 36 (green)
- 360 (red)
- 37 (green)
- 38 (green)
- 39 (green)
- 400 (green)
- 42 (green)
- 44 (green)
- 45 (green)
- 46 (green)
- 48 (green)
- 5 (green)
- 571 (yellow)
- 576 (yellow)
- 6 (green)
- 7 (green)
- 8 (green)
- 800 (yellow)
- 9 (green)
- Sky (purple)
| Route | Type | Line color |
|---|---|---|
| 1 Florida Avenue | Bus | green |
| 10 Cypress Street | Bus | green |
| 12 22nd Street | Bus | green |
| 14 Armenia/Howard Avenue | Bus | green |
| 15 Columbus Drive | Bus | green |
| 16 Waters Avenue | Bus | green |
| 19 South Tampa | Bus | green |
| 24 Fishhawk/South Tampa Limited Express | Bus | red |
| 25 Bloomingdale/South Tampa Limited Express | Bus | red |
| 275 New Tampa Limited Express | Bus | red |
| 30 Kennedy Boulevard/Town N Country | Bus | green |
| 31 South Hillsborough County | Bus | green |
| 32 Dr. Martin Luther King Jr. Boulevard | Bus | green |
| 33 Fletcher Avenue/Northdale | Bus | green |
| 34 Hillsborough Avenue | Bus | green |
| 36 Dale Mabry Highway/Himes Avenue | Bus | green |
| 360 Brandon/South Tampa Limited Express | Bus | red |
| 37 Brandon/Netpark | Bus | green |
| 38 Mango/Brandon | Bus | green |
| 39 Busch Boulevard | Bus | green |
| 400 Nebraska Avenue | Bus | green |
| 42 University Area Connector | Bus | green |
| 44 Sinclair Hills Connector | Bus | green |
| 45 University Area/Westshore | Bus | green |
| 46 Brandon Boulevard | Bus | green |
| 48 Temple Terrace | Bus | green |
| 5 40th Street | Bus | green |
| 571 HARTFlex South County | Bus | yellow |
| 576 HARTFlex East Fletcher | Bus | yellow |
| 6 56th Street | Bus | green |
| 7 West Tampa | Bus | green |
| 8 Progress Village/Brandon | Bus | green |
| 800 Tampa Historic Streetcar | Tram / light rail | yellow |
| 9 15th/30th Street | Bus | green |
| Sky SkyConnect operated by Tampa International Airport | Tram / light rail | purple |
List every stop
- N Boulevard @ Yukon St
- N Boulevard @ Waters Av
- N Boulevard @ Sitka St
- N Boulevard @ Cypress St
- Himes Av @ Columbus Dr
- Himes Av @ Leroy St
- Himes Av @ Tampa Bay Blvd
- Himes Av @ Hillsborough Av
- Himes Av @ Idlewild Av
- Himes Av @ Sunrise Villas Ct
- Himes Av @ Lambright St
- Himes Av @ Sligh Av
- Himes Av @ Hamilton St
- Himes Av @ Townhouse Ct
- Himes Av @ Sitka St
- Himes Av @ Waters Av
- Himes Av @ Kenyon Av
- Himes Av @ Humphrey St
- Himes Av @ Kenyon Av
- Himes Av @ Waters Av
- Himes Av @ Townhouse Ct
- Himes Av @ Sligh Av
- Himes Av @ Lambright St
- Himes Av @ Idlewild Av
- Himes Av @ Hillsborough Av
- Himes Av @ Hillsborough Av
- Himes Av @ M L King Blvd
- Himes Ave @ M L King Jr Blvd
- Himes Av @ M L King Jr Blvd
- Himes Av @ Spruce St
- M L King Jr Blvd @ Lake Av
- M L King Jr Blvd @ 39th St
- M L King Jr Blvd @ 37th St
- M L King Jr Blvd @ 36th St
- M L King Jr Blvd @ 34th St
- M L King Jr Blvd @ 31st St
- M L King Jr Blvd @ 26th St
- M L King Jr Blvd @ 24th St
- M L King Jr Blvd @ 20th St
- M L King Jr Blvd @ 15th St
- M L King Jr Blvd @ 13th St
- M L King Jr Blvd @ 12th St
- M L King Jr Blvd @ 10th St
- M L King Jr Blvd @ Central Av
- M L King Jr Blvd @ Branch Av
- M L King Jr Blvd @ Highland Av
- M L King Jr Blvd @ Lynn Av
- M L King Jr Blvd @ N Boulevard
- M L King Jr Blvd @ Myrtle Ave
- M L King Jr Blvd @ Poplar Ave
- M L King Jr Blvd @ Riverside Dr
- M L King Jr Blvd @ 1913 M L King Jr Blvd
- M L King Jr Blvd @ Tampania Av
- MLK Jr Blvd @ Dale Mabry Hwy
- M L King Jr Blvd @ Gomez Av
- M L King Jr Blvd @ Habana Av E/S
- M L King Jr Blvd @ Armenia Ave
- M L King Blvd @ Armenia Ave E/S
- M L King Jr Blvd @ Howard Ave
- M L King Jr Blvd @ St Isabel St
- M L King Jr Blvd @ Poplar Ave
- M L King Jr Blvd @ Myrtle Ave
- M L King Jr Blvd @ Lynn Av
- M L King Jr Blvd @ Highland Av
- M L King Jr Blvd @ Suwanee Av
- M L King Jr Blvd @ Central Av
- M L King Jr Blvd @ Nebraska Av
- M L King Jr Blvd @ 10th St
- M L King Jr Blvd @ 12th St
- M L King Jr Blvd @ 13th St
- M L King Jr Blvd @ 15th St
- M L King Jr Blvd @ 17th St
- M L King Jr Blvd @ 31st St
- M L King Jr Blvd @ 34th St
- M L King Jr Blvd @ 35th St
- M L King Jr Blvd @ 37th St
- M L King Jr Blvd @ 50th St
- M L King Jr Blvd @ Phillips St
- M L King Jr Blvd @ 54th St
- M L King Jr Blvd @ Carroway St
- Hillsborough Av @ 48th St
- Hillsborough Av @ 46th St
- Hillsborough Av @ 43rd St
- Hillsborough Av @ 40th St
- Hillsborough Av @ 37th St
- Hillsborough Av @ 34th St
- Hillsborough Av @ 30th St
- Hillsborough Av @ 22nd St
- Hillsborough Av @ 19th St
- Hillsborough Av @ 15th St
- Hillsborough Av @ 11th St
- Hillsborough Av @ Central Av
- Hillsborough Av @ Florida Av
- Hillsborough Av @ Habana Av
- Hillsborough Av @ MacDill Av
- Hillsborough Av @ Lincoln Av
- Hillsborough Av @ Lois Av (Hooters)
- Hillsborough Av @4427 Hesperides St
- Hillsborough Av @ Hoover Blvd
- Hillsborough @ 5555 Crown Bowling
- Hillsborough Ave @ Benjamin Rd
- Hillsborough Av @ Beaumont Ctr Blvd
- Hillsborough Av @ Golden Dr
- Hillsborough Av @ Sawyer Rd
- Hillsborough Av @ Hanley Rd
- Hillsborough Av @ Ambassador Dr
- Hillsborough Av @ Town 'N Country
- Hillsborough Av @ Webb Rd
- Hillsborough Av @ Sheldon Rd
- Hillsborough Av @ Webb Rd
- Hillsborough Av @ Town 'N Country
- Hillsborough Av @ Kelly Rd
- Hillsborough Av @ Hoover Blvd
- Hillsborough Av @ Lois Av
- Hillsborough Av @ Himes Av
- Hillsborough Av @ Lincoln Av
- Hillsborough Av @ MacDill Av
- Hillsborough Av @ Habana Av
- Hillsborough Av @ Armenia Av
- Hillsborough Av @ Howard Av
- Hillsborough Av @ Mendenhall Dr
- Hillsborough Av @ Rome Av
- Hillsborough Av @ Florida Av
- Hillsborough Av @ Central Av
- Hillsborough Av @ Nebraska Av
- Hillsborough Av @ 15th St
- Hillsborough Av @ 19th St
- Hillsborough Av @ 22nd St
- Hillsborough Av @ 30th St
- Hillsborough Av @ 32nd St
- Hillsborough Av @ 34th St
- Hillsborough Av @ 37th St
- Hillsborough Av @ 40th St WS
- Hillsborough Av @ 40th St ES
- Hillsborough Av @ 43rd St
- Hillsborough Av @ 46th St
- Hillsborough Av @ Walton Way
- HillsboroughAv@SuncoastC
- Hillsborough Av @ Orient Rd
- Westshore Blvd @ Gray St
- Westshore Blvd @ Gray St
- Westshore Blvd @ Loughman St
- Westshore Blvd @ Bradley St
- Waters Av @ 17th St
- Waters Av @ Mulberry St
- Waters Av @ 12th St
- Waters Av @ Edison Av
- Waters Av @ El Portal Dr
- Waters Av @ Willow Av
- Waters Av @ Orleans Av
- Waters Av @ Rome Av
- Waters Av @ Jones Av
- Waters Av @ Armenia Av
- Waters Av @ Habana Av
- Waters Av @ Twin Lakes Blvd
- Waters Av @ Sevilla Dr
- Waters Av @ Dale Mabry Hwy E/S
- Waters Av @ Grady Av
- Waters Av @ Lake Melena Way
- Waters Av @ Lois Av
- Waters Av @ Camden St
- Waters Av @ Manhattan Av
- Waters Av @ Woodland Corporate Blvd
- Waters Av @ Florida Mining Blvd N/S
- Waters Av @ Anderson Rd
- Waters Av @ Benjamin Rd
- Waters Av @ Henderson Rd
- Waters Av @ Twelve Oaks Blvd
- Waters Av @ J R Manor Dr
- Waters Av @ Hanley Rd
- Waters Ave @ Pinehurst Dr
- Waters Av @ Rustic Dr
- Waters Av @ Twelve Oaks Blvd
- Waters Av @ Oak Trace Way
- Waters Av @ Sitka St
- Waters Av @ Anderson Rd
- Waters Av @ Uhaul Storage
- Waters Av @ Savarese Blvd
- Waters Av @ Woodland Center Blvd
- Waters Av @ Woodland Corporate Blvd
- Waters Av @ Manhattan Av
- Waters Av @ Thatcher Av
- Waters Av @ Lois Av
- Waters Av @ Grady Av
- Waters Av @ Dale Mabry Hwy
- Waters Av @ Himes Av
- Waters Av @ Sevilla Dr
- Waters Av @ Lago Vista Dr
- Waters Av @ Palma Vista Lane
- Waters Av @ Habana Av
- Waters Av @ Armenia Av
- Waters Av @ Saulray St
- Waters Av @ Fremont Av
- Waters Av @ Rome Av
- Waters Av @ Orleans Av
- Waters Av @ El Portal Dr
- Waters Av @ 14th St
- Sligh Av @ Rowlett Park Dr
- Sligh Av @ Willow Av
- Sligh Av @ 30th St
- Sligh Av @ 53rd St
- 40th St @ Osborne Av
- 40th St @ Ellicott St
- 40th St @ Hillsborough Av
- 40th St @ Idlewild Ave
- 40th St @ Paris St
- 40th St @ Diana St
- 40th St @ Riverhills Dr
- 40th St @ Bird St
- 40th St @ Regnas Av
- 40th St @ Seward St
- 40th St @ Busch Blvd
- McKinley Dr @ Busch Blvd
- McKinley Dr @ Linebaugh Av
- Mckinley Dr @ Bougainvillea Av
- Mckinley Dr @ Bougainvillea Av
- 40th St @ Seward St
- 40th St @ Regnas Av
- 40th St @ Hanlon St
- 40th St @ Norfolk St
- 40th St @ River Grove Dr
- 40th St @ Fern St
- 40th St @ Powhattan Av
- 40th St @ Hillsborough Av
- 40th St @ Ellicott St
- 40th St @ Osborne Av
- 30th St @ Hillsborough Ave
- 30th St @ Powhatan Av
- 30th St @ Idlewild Av
- 30th St @ Hanna Av
- 30th St @ Diana St
- 30th St @ Pocahontas Av
- 30th St @ Sligh Av
- 30th St @ Busch Blvd
- 30th St @ Annie St
- 30th St @ Bougainvillea Av
- 30th St @ 113th Av
- 30th St @ 109th Av
- 30th St @ Bougainvillea Av
- 30th St @ Poinsettia Av
- 30th St @ Annie St
- 30th St @ Busch Blvd
- 30th St @ Diana Ct
- 30th St @ Hanna Av
- 30th St @ Henry Av
- 30th St @ Hillsborough Av N/S
- Dale Mabry Hwy @ Interbay Blvd
- Dale Mabry Hwy @ Bay Ave
- Dale Mabry Hwy @ Wisconsin Ave
- Dale Mabry Hwy @ Oklahoma Ave
- and 2065 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 1.7 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 50.7 | first check |
| 2026-07-30 | 49.0 | down 1.7 |
| 2026-07-31 | 48.7 | down 0.3 |
| 2026-08-01 | 47.0 | down 1.7 |
What changed since your last check
- Correctness down 4.0
- Freshness down 1.7
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall score fell 1.7 points since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
New since 2026-07-31 (1 finding)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
Finding code: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Error1 instance
The trip updates realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The vehicle positions realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_vehicle_positions_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning10884 instances
10884 of 10884 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning2315 instances
2315 of 2315 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)
- Warning80 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date30_days · Read the fix guide · 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 transit vehicle route through the wrong path or point riders to the wrong boarding location.
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 14 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 14 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 14 days; renew before you certify.
- 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 10884 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. Service data runs out in 14 days; renew to qualify. 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 runs out in 14 days; renew to qualify.
- 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.
Realtime reliability
The realtime feed responded on 0.0% of 200 checks over the last 34 days, with lag not reported by the feed.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 14 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
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 78 / 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 23 / 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 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 0 / 100
- 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/hillsborough-area-regional-transit-hart/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.