← All agencies

Feed status · checked 2026-08-01

Greater Bridgeport Transit

Based on the feed this agency publishes

Service mode Bus

FDCBA

75.2 / 100

unchanged since 2026-07-31

Catalogued in Connecticut.

Covers 148 daysAccessibility gapsFlexible serviceRealtime not yet published

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 1 days ago; last changed 38 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

Fix 01

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

1208 of 1208 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

Fix 02

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

1753 of 1753 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

Fix 03

Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool

Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

⏱ Often a bulk fix in your scheduling software.worth about +8 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: 1208 of 1208 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

Agency: Greater Bridgeport Transit
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 1208 of 1208 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/greater-bridgeport-transit/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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 148 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: 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.

Hi,

Our GTFS feed (Greater Bridgeport Transit) scored C (75.2 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 1208 of 1208 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 1753 of 1753 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
   What: Some rider-facing names are in ALL CAPS or all lowercase.
   Finding code: mixed_case_recommended_field
   Guide: https://gtfsscorecard.org/fix/mixed_case_recommended_field/

Full scorecard: https://gtfsscorecard.org/agency/greater-bridgeport-transit/

Score by category

Correctness72.0 / 100

The MobilityData validator flagged 7 kinds of issue across 2363 instances (0 error, 2318 warning, 45 informational).

Freshness100.0 / 100

Service data covers the next 148 days.

Rider experience60.0 / 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 published.

Accessibility0 / 100

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

FaresLegacy fares

Fares are applied to trips.

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 1208 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 (blue)
CL (teal)
19X (purple)
17 (gray)
3 (gray)
6 (pink)
7 (orange)
8 (green)
4 (yellow)
9 (teal)
23 (green)
10 (yellow)
22X (purple)
5 (purple)
13 (yellow)
15 (pink)

Routes in Greater Bridgeport Transit's feed
Route	Type	Line color
1 Route 1	Bus	blue
CL Coastal Link	Bus	teal
19X Route 19X	Bus	purple
17 Route 17	Bus	gray
3 Route 3	Bus	gray
6 Route 6	Bus	pink
7 Route 7	Bus	orange
8 Route 8	Bus	green
4 Route 4	Bus	yellow
9 Route 9	Bus	teal
23 Route 23	Bus	green
10 Route 10	Bus	yellow
22X Route 22x	Bus	purple
5 Route 5	Bus	purple
13 Route 13	Bus	yellow
15 Route 15	Bus	pink

List every stop

Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Trapp Falls Rd. at Opposite Heather Ridge
Trumbull Ave at Opposite 505 Trumbull Ave.
Trumbull Ave at 610 Trumbull Ave.
Trumbull Ave at 730 Trumbull Ave.
Post Rd. West at Opposite 375 Post Rd. West
Post Rd. West at Kings Hwy. North
Post Rd. West at Opposite Kings Hwy. North
Post Rd. West at Kings Hwy. South
Post Rd. West at Opposite Kings Hwy. South
Post Rd. West at Lincoln St.
Post Rd. West at Ludlow Rd.
Post Rd. West at Main St.
Post Rd. East at Opposite Main St.
Post Rd. West at Myrtle Ave.
Post Rd. West at Wright St.
Post Rd. West at Sylvan Rd. North
Post Rd. West at Sylvan Rd. South
Post Rd. West at Wilton Rd.
Quality St. at Trumbull Town Hall
Quality St. at Trumbull Town Hall
Research Dr. at Opposite Optimum
Research Dr. at Progress Dr.
Reservoir Ave. at Clover Hill Ave.
Reservoir Ave. at Old Town Rd.
Reservoir Ave. at Old Town Rd.
Reservoir Ave. at Opposite Wilbur Cross School
Reservoir Ave. at Rainbow Rd.
Reservoir Ave. at Sylvan Ave.
Reservoir Ave. at Trumbull Ave.
Reservoir Ave. at Wilbur Cross School
River Rd. at 770 River Rd. (Centrix Building)
River Rd. at Opposite 770 River Rd.
River Rd. at Long Hill Ave.
River Rd. at Opposite Long Hill Ave.
River St. at Milford City Hall
River St. at Milford Railroad Station
River St. at Milford Railroad Station
River St. at Prospect St.
Ryon St. at Soundview Ave.
Ryon St. at Soundview Ave.
Saint Stephen's Rd. at Wordin Ave.
Saint Stephen's Rd. at Yacht St.
Seaview at Beardsley St.
Seaview at Dekalb Ave.
Seaview at Jefferson St.
Seaview Ave. at Opposite Beardsley St.
Seaview Ave. at Opposite Dekalb Ave.
Seaview Ave. at Opposite Jefferson St.
Seaview Ave. at Opposite Newfield Ave.
Second Hill Ln. at Briarfield Dr.
Second Hill Ln. at Broadbridge Ave.
Second Hill Ln. at Mcleod Pl.
Second Hill Ln. at Russell Rd.
Second Hill Ln. at Second Hill Ln.
Post Rd. at Opposite 417 Post Rd.
Woodend Rd. at Sedgewick Ave.
Soundview Ave. at Omega Ave.
Soundview Ave. at Opposite Omega Ave.
Soundview Ave. at Sylvan Ave.
Soundview Ave. at Sylvan Ave.
South Broad St. at Opposite Greensend Pl.
State St. at Bostwick Ave.
State St. at Clinton Ave.
State St. at Hancock Ave.
State St. at Housatonic Community College
State St. at Howard Ave.
State St. at Iranistan Ave.
State St. at Main St.
State St. at Norman St.
State St. at West Ave.
State St. at Seeley St.
State St. at Wordin Ave.
State St. Ext. at Ash St.
State St. Ext. at Opposite Ash St.
Stewart St. at Bond St.
Stewart St. at Palisade Ave.
Stillson Rd. at Farist Rd.
Stratford Ave. at 2200 Stratford Ave.
Stratford Ave. at Bruce Ave.
Stratford Ave. at Opposite Bruce Ave.
Stratford Ave. at Carroll Ave.
Stratford Ave. at Central Ave.
Stratford Ave. at Cowles St.
Stratford Ave. at Edwin St.
Stratford Ave. at Eleanor St.
Stratford Ave. at Opposite Eleanor St.
Stratford Ave. at Hamilton Ave.
Stratford Ave. at Hewitt St.
Stratford Ave. at Hollister Ave.
Stratford Ave. at Honeyspot Rd.
Stratford Ave. at Opposite Honeyspot Rd.
Stratford Ave. at I-95 Overpass
Stratford Ave. at Kossuth St.
Stratford Ave. at Kossuth St.
Stratford Ave. at Lupes Dr.
Stratford Ave. at Opposite Lupes Dr.
Stratford Ave. at Main St.
Stratford Ave. at Main St.
Stratford Ave. at Newfield Ave.
Stratford Ave. at Saint Michael's Cemetary
Stratford Ave. at Seaview Ave.
Stratford Ave. at Seaview Ave.
Stratford Ave. at Sherwood Pl.
Stratford Ave. at Surf Ave.
Stratford Ave. at Opposite Surf Ave.
Stratford Ave. at Opposite Waterview Ave.
Stratford Ave. at Waterview Ave.
Success Ave. at Court A
Success Ave. at Court D
Success Ave. at Granfield Ave.
Sylvan Ave. at Carlson Ave.
Sylvan Ave. at Opposite Carlson Ave.
Sylvan Ave. at Edwards St.
Sylvan Ave. at Opposite Dodd Ave
Sylvan Ave. at Home Depot
Sylvan Ave. at Wilkins Ave.
Sylvan Ave. at Opposite Wilkins Ave.
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Bridgeport Transportation Center
Trumbull Ave at Chopsey Hill Rd.
Trumbull Ave. at 505 Trumbull Ave.
Trumbull Ave. at 625 Trumbull Ave.
Trumbull Ave. at Opposite 730 Trumbull Ave.
Tunxis Hill Cutoff South at Villa Ave.
Tunxis Hill Rd. at Beaver St.
Tunxis Hill Cut-Off at Opposite Cedarhurst Ln.
Tunxis Hill Cut-Off at Cedarhurst Ln.
Tunxis Hill Cut-Off at Knapps Hwy.
Tunxis Hill Cut-Off at Knapps Hwy.
Tunxis Hill Rd. at Kohl's Department Store
Tunxis Hill Rd. at Marlborough Ter.
Tunxis Hill Rd. at Old Stratfield Rd.
Tunxis Hill Rd. at Old Stratfield Rd.
Tunxis Hill Rd. at Super Stop & Shop
Tunxis Hill Rd. at Villa Ave.
Tunxis Hill Cut-Off at Whitewood Dr.
Veterans Blvd. at Side Of Stratford Square
Waldemere Ave. at Hazel St.
Wall St. at Commerce St
Burnell Blvd. at Norwalk Wheel Hub
Washington Ave. at Catherine St.
Washington Ave. at Catherine St.
Washington Ave. at Opposite Coleman St.
Washington Ave. at Coleman St.
Washington Ave. at Highland Ave.
Washington Ave. at Highland Ave.
Washington Ave. at James St.
Washington Ave. at James St.
Washington Ave. at Pequonnock St.
Washington Ave. at West Ave.
Washington Ave. at Opposite West Ave.
Water St. at John St.
Waterview Dr. at 10 Waterview Dr.
Waterview Dr. at Opposite 10 Waterview Dr.
Waterview Dr. at Constitution Blvd. South
Waterview Dr. at Constitution Blvd. South
Waterview Dr. at Morningside Ct.
Waterview Dr. at Opposite Morningside Ct.
Waterview Dr. at Pitney Bowes Entrance
Waterview Dr. at Opposite Pitney Bowes Entrance
Wells St. at North Ave.
Westfield Trumbull Mall
Westport Ave. at 330 Westport Ave.
Westport Ave. at 56 Westport Ave..
Westport Ave. at Dry Hill Rd. (Stew Leonard's)
Westport Ave. at Dry Hill Rd. (Stew Leonard's)
Westport Ave. at George Ave
Westport Ave. at Opposite George Ave.
Westport Ave. at Lois St.
Westport Ave. at Opposite Lois St.
Westport Ave. at Strawberry Hill Ave.
Westport Ave. at Strawberry Hill Ave.
Westport Ave. at Vollmer Ave.
Westport Ave. at Walgreen's
Westport Ave. at Walter Ave.
Westport Ave. at Willard Rd.
Westport Ave. at Oppostie Willard Rd.
Westport Ave. at Wolfpit Ave.
Westport Ave. at Opposite Wolfpit Ave.
White Plains Rd. at Pequonnock Rd.
White Plains Rd. at Reservoir Ave.
White Plains Rd. at Reservoir Ave.
White Plains Rd. at Sunset Ave.
White Plains Rd. at Trumbull Center
White Plains Rd. at Trumbull Center
Stratford Ave. at Beardsley Ave.
Research Dr. at Commerce Dr.
Woodend Rd. at Birch Dr.
Woodend Rd. at Columbus Ave.
Woodend Rd. at Ketcham Rd.
Woodend Rd. at Opposite Leeward Dr.
Woodend Rd. at Mcpadden Dr.
Wordin Ave. at Ocean Ter.
Wordin Ave. at Opposite Ocean Ter.
Ocean Ter. at Ocean Ave.
Brewster St. at Fairfield Ave.
Sylvan Ave. at Opposite Home Depot
Lindeman Dr. at Oakview Dr.
Trumbull Ave. at Reservoir Ave.
Woodend Rd. at Main St.
Woodend Rd. at Sedgewick Ave.
Monroe Tpk. at Stop & Shop
Trap Falls Rd. at Bridgeport Ave.
Main St. & Oronoque Ln.
South Broad St. at High St.
Schick-Wilkinson Sword
East Main St. at I-95 Overpass
West Broad St. at Main St.
Boston Ave. at Glenwood Ave.
Barnum Ave. at Essex Pl.
Barnum Ave. at King St.
Benton St. at Opposite Wellington St.
Golden Hill St. at Lyon Ter.
Pequonnock St. at Harral Ave.
Commerce Dr. at Bridgeport Ave.
North Broad St. at High St.
Constitution Blvd. at River Rd.
Constitution Blvd. at River Rd.
Newtown Tpk. at St. Joseph's Manor
Success Ave. at Boston Ave.
Success Ave. at Granfield Ave.
Success Ave. at Baird Ct.
Success Ave. at Baird Ct.
Stonybrook Rd. at Success Ave.
Stonybrook Rd. at Success Ave.
Stonybrook Rd. at Henry Ave.
Stonybrook Rd. at Eaton St.
Stonybrook Rd. at Henry Ave. Ext.
Quarry Rd. at Opposite Bridgeport P.A.L. Building
Quarry Rd. at Opposite Entrance To Magnet School
Quarry Rd. at 112 Quarry Rd.
Quarry Rd. at Entrance To Magnet School
Quarry Rd. at Bridgeport P.A.L. Building
North Ave. at Remer St.
North Ave. at Remer St.
Main St. at Curtis Pl.
Ocean Ter at Osborne St.
and 958 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

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-25	75.2	first check
2026-07-30	75.2	no change
2026-07-31	75.2	no change
2026-08-01	75.2	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

Everything we checked

11 findings, ordered by severity.

Show every finding

Warning1770 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1753 instances
1753 of 1753 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)
Warning1208 instances
1208 of 1208 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)
Warning526 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning21 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
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules 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)
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.)
Finding code: scorecard_station_no_pathways · 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)
Info3 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 148 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 1753 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 148 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.

21 of 1207 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 147 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 72 / 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 60 / 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.

[![Greater Bridgeport Transit GTFS data quality grade: C](https://gtfsscorecard.org/data/artifacts/greater-bridgeport-transit/badge.svg)](https://gtfsscorecard.org/agency/greater-bridgeport-transit/)

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/greater-bridgeport-transit/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.

GTFS Scorecard. (2026). Greater Bridgeport Transit GTFS feed-quality record, dated 2026-08-01 (grade C (75.2/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 7da6051a460e…). https://gtfsscorecard.org/data/artifacts/greater-bridgeport-transit/2026-08-01.json

@misc{gtfsscorecard-greater-bridgeport-transit-2026-08-01,
  title        = {Greater Bridgeport Transit GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/greater-bridgeport-transit/2026-08-01.json}},
  note         = {Checked 2026-08-01; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade C (75.2/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.