Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Broward County Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 97% of all tracked agencies and 100% of large agencies. Operates in Florida.
Heads-up: Days until the service window ends dropped by 29 between 2026-07-01 and 2026-07-02, but only 1 day(s) passed. The feed's calendar appears to have moved backward, which can happen when an older export is republished. Worth confirming the latest export is the one being served. (checked 2026-07-02). This can be a brief vendor export glitch; watch the next update before acting.
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.1, validator 8.0.1.
Checked for changes 4 hours ago; last changed 9 days ago.
Top things to fix
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
5926 of 5926 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
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
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
136 of 4793 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.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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.
Score by category
The validator found no problems in this feed. That is rare and worth celebrating.
Service data covers the next 79 days.
97% of stops state wheelchair accessibility (83% marked accessible, 14% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
97% of stops state accessibility (83% marked accessible). Reflects what the feed states, 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 01 (red)
- 02 (pink)
- 04 (yellow)
- 05 (teal)
- 06 (purple)
- 07 (brown)
- 08 (teal)
- 09 (purple)
- 10 (red)
- 101 (teal)
- 106 (teal)
- 108 (blue)
- 109 (red)
- 11 (gray)
- 110 (blue)
- 114 (green)
- 115 (blue)
- 12 (brown)
- 14 (teal)
- 15 (orange)
- 16 (yellow)
- 18 (pink)
- 19 (gray)
- 20 (green)
- 22 (pink)
- 23 (red)
- 28 (green)
- 30 (orange)
- 31 (brown)
- 34 (gray)
- 36 (orange)
- 40 (teal)
- 42 (brown)
- 441 (teal)
- 48 (yellow)
- 50 (gray)
- 55 (teal)
- 56 (red)
- 60 (yellow)
- 62 (yellow)
- 72 (brown)
- 81 (gray)
- 83 (blue)
- 88 (green)
| Route | Type | Line color |
|---|---|---|
| 01 Us 1 Local | Bus | red |
| 02 University Dr Local | Bus | pink |
| 04 South Sr A1a Local | Bus | yellow |
| 05 Pembroke Rd Local | Bus | teal |
| 06 Broward Terminal / County Line Rd | Bus | purple |
| 07 Hollywood Blv / Pines Blv Local | Bus | brown |
| 08 Taft Street Local | Bus | teal |
| 09 Broward Terminal - Young Circle Via Bcc | Bus | purple |
| 10 Federal Hwy Local | Bus | red |
| 101 Us 1 Breeze | Bus | teal |
| 106 95 Express Miramar | Bus | teal |
| 108 95 Express Pembroke Pines | Bus | blue |
| 109 95 Express Pembroke Pines/miramar | Bus | red |
| 11 Us 441/prospect R - Brow Term - Us 1/copans R | Bus | gray |
| 110 595 Express Bb&t Center To Miami/brickell | Bus | blue |
| 114 595 Express Bb&t Center To Miami Civic Center | Bus | green |
| 115 75 Express Miramar P&r To Miami Intermodal Center | Bus | blue |
| 12 Westfield Mall - A1a Via Oakwood Plaza | Bus | brown |
| 14 Powerline Rd Local | Bus | teal |
| 15 Tri-rail - County Line Rd | Bus | orange |
| 16 Stirling Rd Local | Bus | yellow |
| 18 Us 441 Local | Bus | pink |
| 19 N State Rd 7 Local | Bus | gray |
| 20 15 A - Cypress Rd - 3 A Local | Bus | green |
| 22 Broward Blvd Local | Bus | pink |
| 23 Pembroke Lakes Mall -sawgrass Mills Mall | Bus | red |
| 28 Hallandale Blv / Miramar Pky Local | Bus | green |
| 30 Davie Blv Local | Bus | orange |
| 31 Broward Terminal - Hillsboro Blv | Bus | brown |
| 34 Sample Rd Local | Bus | gray |
| 36 A1a - Sawgrass Mills Mall | Bus | orange |
| 40 Lauderhill - Browterm - Galleria / Pts Of America | Bus | teal |
| 42 Atlantic Blv Local | Bus | brown |
| 441 Sr 7 Breeze | Bus | teal |
| 48 Hillsboro Blv Local | Bus | yellow |
| 50 Dixie Hwy Local | Bus | gray |
| 55 Commercial Blv Local | Bus | teal |
| 56 Welleby Plz-109 A-sunrise Lks-jacaranda Plz | Bus | red |
| 60 Andrews Ave Local | Bus | yellow |
| 62 Mcnab Rd Local | Bus | yellow |
| 72 Oakland Park Blvd Local | Bus | brown |
| 81 Broward Terminal - West Terminal | Bus | gray |
| 83 Copans Rd/royal Plam Blv Local | Bus | blue |
| 88 Pine Island Rd Local | Bus | green |
This feed has 4793 stops.
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 90.4 | first check |
| 2026-06-20 | 87.8 | down 2.6 |
| 2026-06-21 | 90.4 | up 2.6 |
| 2026-06-22 | 90.4 | no change |
| 2026-06-23 | 90.4 | no change |
| 2026-06-24 | 90.4 | no change |
| 2026-06-25 | 90.4 | no change |
| 2026-06-26 | 90.4 | no change |
| 2026-06-27 | 90.4 | no change |
| 2026-06-28 | 90.4 | no change |
| 2026-06-29 | 90.4 | no change |
| 2026-06-30 | 90.4 | no change |
| 2026-07-01 | 90.4 | no change |
| 2026-07-02 | 86.9 | down 3.5 |
| 2026-07-04 | 90.4 | up 3.5 |
| 2026-07-05 | 90.4 | no change |
| 2026-07-06 | 90.4 | no change |
| 2026-07-07 | 90.4 | no change |
| 2026-07-08 | 90.4 | no change |
| 2026-07-09 | 90.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-08.
Same feed file as 2026-07-08; 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.
What changed over time
On 2026-06-19 this feed started at grade A. On 2026-06-20 the grade moved from A to B. On 2026-06-21 the grade moved from B to A. On 2026-07-02 the grade moved from A to B. As of 2026-07-09 it holds grade A.
A plain-language history of this feed, newest first.
- 2026-07-04 Grade went B to A, correctness rose 6 points.
- 2026-07-02 Grade went A to B, correctness fell 6 points.
- 2026-06-21 Grade went B to A, correctness rose 6 points.
- 2026-06-20 Grade went A to B, correctness fell 6 points.
Everything we checked
- Warning5926 instances
5926 of 5926 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning136 instances
136 of 4793 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · 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 connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
26 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (01, 02, 04, 05, 10, and more).
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.
4702 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Broward Boulevard/Southeast 3rd Avenue", "Southeast 3rd Avenue/Southeast 7th Street", "Southeast 3rd Avenue/Southeast 9th Street", 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.
NTD certification readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 79 days.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 97% 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 79 days.
- Accessible Not yet
- States wheelchair access on 97% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 79 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 100 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 69 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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/broward-county-transit/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.