← All agencies

Feed status · checked 2026-08-01

Connecticut Transit

Based on the feed this agency publishes

Service mode Bus

FDCBA

56.1 / 100

down 0.4 since 2026-07-31

Catalogued in Connecticut.

Covers 161 daysAccessibility gaps

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 79 minutes ago; last changed 19 days ago; last fetch returned HTTP 404.

Measured 4 of 4 score categories from the Mobility Database's mirror copy of the feed.

How we measured this

Confidence in this measurement: medium.

All four score categories were measured this run.
Realtime was sampled in one bounded window of 9 snapshots.
The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.

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

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

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

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

⏱ Two fields, set once in export settings.worth about +15 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: 9612 of 9612 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: Connecticut Transit
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 9612 of 9612 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/connecticut-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. 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. See this feed's finding-clearance log.
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. 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. See this feed's finding-clearance log.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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. See this feed's finding-clearance log.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility: The feed's last published service date is in 161 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: Live-arrival data covered 72.8% of scheduled trips in the sampled window.

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.

Hi,

Our GTFS feed (Connecticut Transit) scored F (56.1 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: 9612 of 9612 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: 20490 of 20490 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. Add feed_info.txt with feed_start_date and feed_end_date to your export.
   What: feed_info.txt is missing its start/end dates (the file itself is absent)
   Finding code: scorecard_missing_feed_info_dates
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_feed_info_dates/

Full scorecard: https://gtfsscorecard.org/agency/connecticut-transit/

Score by category

Correctness33.2 / 100

The MobilityData validator flagged 13 kinds of issue across 5611 instances (0 error, 5605 warning, 6 informational).

Freshness85.0 / 100

Service data covers the next 161 days.

Rider experience37.5 / 100

0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility0 / 100

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

Realtime quality90.3 / 100

Sampled 9 times: 3 of 3 configured feeds healthy; 72.8% of scheduled trips had live predictions; 98.6% of vehicles on their route; predictions ran a median of 128s behind schedule.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 9612 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.

291 (black)
292 (purple)
411 (blue)
412 (purple)
413 (teal)
416 (brown)
417 (orange)
418 (purple)
421 (white)
422 (green)
425 (teal)
426 (blue)
428 (white)
431 (white)
432 (blue)
433 (purple)
436 (brown)
441 (teal)
442 (white)
444 (green)
445 (teal)
446 (blue)
447 (teal)
450 (black)
460 (purple)
470 (teal)
471 (pink)
472 (blue)
473 (black)
479 (green)
480 (white)
561 (red)
563 (blue)
564 (blue)
565 (green)
566 (green)
567 (purple)
508 (blue)
509 (purple)
510 (blue)
901 (purple)
919 (red)
921 (red)
923 (red)
926 (purple)
926/927 (purple)
927 (purple)
928 (red)
501 (purple)
502 (white)
503 (blue)
505 (orange)
506 (green)
507 (brown)
511 (yellow)
512 (blue)
513 (black)
532 (teal)
541 (brown)
542 (purple)
543 (blue)
940 (brown)
201 (blue)
204 (purple)
206 (red)
212 (black)
213 (green)
215 (green)
223 (pink)
224 (red)
228 (blue)
229 (teal)
234 (teal)
237 (blue)
238 (brown)
241 (green)
243 (red)
246 (red)
254 (brown)
255 (teal)
261 (red)
262 (purple)
265 (green)
268 (black)
271 (teal)
272 (black)
274 (black)
278 (green)
282 (purple)
567* (purple)
USS (blue)
311 (blue)
312 (purple)
313 (pink)
321 (blue)
324 (purple)
326 (pink)
327 (gray)
328 (orange)
331 (blue)
333 (red)
334 (gray)
335 (gray)
336 (blue)
341 (teal)
342 (brown)
344 (pink)
345 (green)
349 (purple)
351 (black)
355 (teal)
971 (blue)
101 (gray)
102 (green)
121 (blue)
125 (teal)
128 (purple)
144 (brown)
153 (black)
161 (purple)
24* (black)
30 (teal)
31 (blue)
32 (orange)
33 (blue)
34 (blue)
36 (teal)
37 (blue)
38 (blue)
39 (purple)
40 (pink)
42 (pink)
43 (purple)
44 (teal)
46 (purple)
47 (blue)
50 (black)
52 (black)
53 (blue)
54 (orange)
55 (blue)
56 (black)
58 (teal)
59 (pink)
60 (blue)
61 (blue)
62 (brown)
63 (blue)
64 (green)
66 (purple)
69 (teal)
72 (blue)
74 (blue)
76 (orange)
80 (purple)
82 (orange)
82/84 (gray)
83 (orange)
84 (orange)
86 (blue)
87 (blue)
88 (green)
904 (teal)
904/914 (blue)
905 (blue)
906 (blue)
91 (teal)
910 (blue)
912 (blue)
914 (blue)
92 (orange)
94 (purple)
95 (orange)
96 (purple)
AH (blue)
CB (green)
DASH (black)
SC (black)
903 (purple)
903/913 (purple)
913 (purple)
918 (purple)
950 (purple)
PPB (black)

Routes in Connecticut Transit's feed
Route	Type	Line color
291 CENTER ST	Bus	black
292 NORTH COLONY RD	Bus	purple
411 WILLOW ST	Bus	blue
412 HILL ST	Bus	purple
413 COOKE ST	Bus	teal
416 NORTH MAIN ST	Bus	brown
417 THOMASTON AVE	Bus	orange
418 LONG HILL RD	Bus	purple
421 WALNUT ST	Bus	white
422 WOLCOTT ST	Bus	green
425 MERIDEN RD	Bus	teal
426 EAST MAIN ST	Bus	blue
428 SCOTT RD	Bus	white
431 HAMILTON AVE	Bus	white
432 SYLVAN AVE	Bus	blue
433 BALDWIN ST	Bus	purple
436 CONGRESS AVE	Bus	brown
441 HIGHLAND AVE	Bus	teal
442 CHASE PKWY	Bus	white
444 BUNKER HILL AVE	Bus	green
445 WATERTOWN AVE	Bus	teal
446 WATERTOWN-INDUSTRIAL PARK	Bus	blue
447 WATERTOWN-STRAITS TPKE	Bus	teal
450 WATERBURY/TORRINGTON	Bus	black
460 WATERBURY/CHESHIRE	Bus	purple
470 WATERBURY/NAUGATUCK	Bus	teal
471 RUBBER AVE	Bus	pink
472 NEW HAVEN RD	Bus	blue
473 SPRING ST	Bus	black
479 WATERBURY/BEACON FALLS	Bus	green
480 WATERBURY/SOUTHBURY	Bus	white
561 MERIDEN MALL	Bus	red
563 YALE ACRES	Bus	blue
564 SOUTH MERIDEN	Bus	blue
565 WEST MAIN ST	Bus	green
566 EAST MAIN ST	Bus	green
567 MERIDEN/WALLINGFORD	Bus	purple
508 EAST MAIN ST	Bus	blue
509 EAST STREET	Bus	purple
510 SOUTH STREET	Bus	blue
901 AVON/CANTON EXP	Bus	purple
919 CROMWELL/MERIDEN EXP	Bus	red
921 MIDDLETOWN/OLD SAYBROOK EXP	Bus	red
923 BRISTOL EXP	Bus	red
926 WINSTED EXP	Bus	purple
926/927 WINSTED/TORRINGTON EXP	Bus	purple
927 TORRINGTON EXP	Bus	purple
928 SOUTHINGTON/CHESHIRE/WATERBURY	Bus	red
501 ARCH STREET	Bus	purple
502 BLACK ROCK AVENUE	Bus	white
503 CORBIN AVENUE	Bus	blue
505 BURRITT STREET	Bus	orange
506 FARMINGTON AVENUE	Bus	green
507 OAK STREET	Bus	brown
511 NEW BRITAIN/MERIDEN	Bus	yellow
512 NEW BRITAIN/BERLIN TPKE	Bus	blue
513 NEW BRITAIN/CROMWELL	Bus	black
532 QUEEN ST	Bus	teal
541 BRISTOL LOCAL	Bus	brown
542 BRISTOL HOSPITAL	Bus	purple
543 WEST STREET	Bus	blue
940 WATERBURY/MERIDEN EXP	Bus	brown
201 NEW HAVEN/MADISON	Bus	blue
204 NEW HAVEN/EAST HAVEN	Bus	purple
206 EAST CHAPEL STREET	Bus	red
212 GRAND AVENUE	Bus	black
213 NEW HAVEN/NORTH BRANFORD	Bus	green
215 NEW HAVEN/WALLINGFORD/MERIDEN	Bus	green
223 LOMBARD STREET	Bus	pink
224 STATE STREET	Bus	red
228 WHITNEY AVENUE	Bus	blue
229 NEW HAVEN/WATERBURY	Bus	teal
234 WINCHESTER AVENUE	Bus	teal
237 SHELTON AVENUE	Bus	blue
238 DIXWELL AVENUE	Bus	brown
241 GOFFE STREET	Bus	green
243 WHALLEY AVENUE	Bus	red
246 EDGEWOOD AVENUE	Bus	red
254 WEST CHAPEL STREET	Bus	brown
255 NEW HAVEN/ANSONIA/SEYMOUR	Bus	teal
261 BOSTON POST ROAD	Bus	red
262 ORANGE BUSINESS DISTRICT/MILFORD	Bus	purple
265 CONGRESS AVENUE	Bus	green
268 WASHINGTON AVENUE	Bus	black
271 KIMBERLY AVENUE	Bus	teal
272 UNION AVENUE	Bus	black
274 SARGENT DRIVE	Bus	black
278 NEW HAVEN CONNECTOR	Bus	green
282 GRAND AVE BUS BRIDGE	Bus	purple
567* MERIDEN/WALLINGFORD	Bus	purple
USS UNION STATION SHUTTLE	Bus	blue
311 PORT CHESTER	Bus	blue
312 WEST MAIN ST	Bus	purple
313 WEST BROAD ST	Bus	pink
321 WEST AVE	Bus	blue
324 FAIRFIELD AVE	Bus	purple
326 PACIFIC ST	Bus	pink
327 SHIPPAN AVE	Bus	gray
328 COVE RD	Bus	orange
331 HIGH RIDGE RD	Bus	blue
333 NEWFIELD AVE	Bus	red
334 HOPE ST	Bus	gray
335 WASHINGTON BLVD	Bus	gray
336 LONG RIDGE RD	Bus	blue
341 NORWALK	Bus	teal
342 EAST MAIN ST	Bus	brown
344 GLENBROOK RD	Bus	pink
345 NCC FLYER	Bus	green
349 SPRINGDALE/COVE	Bus	purple
351 STAMFORD CONNECTOR: DOWNTOWN LOOP	Bus	black
355 UCONN STAMFORD	Bus	teal
971 STAMFORD/WHITE PLAINS EXPRESS	Bus	blue
101 HARTFORD/NEW BRITAIN	Bus	gray
102 HARTFORD/NEW BRITAIN/BRISTOL	Bus	green
121 CT STATE/HARTFORD/UCONN HEALTH	Bus	blue
125 HARTFORD/BERLIN TPKE	Bus	teal
128 HARTFORD/WESTFARMS/NEW BRITAIN	Bus	purple
144 WETHERSFIELD/WESTFARMS	Bus	brown
153 FLATBUSH/COPACO	Bus	black
161 HOSPITAL CONNECTOR	Bus	purple
24* WINDSOR LOCKS/BRADLEY INT'L AIRPORT	Bus	black
30 BRADLEY FLYER	Bus	teal
31 PARK ST	Bus	blue
32 WINDSOR AVE	Bus	orange
33 PARK ST	Bus	blue
34 KENNEDY RD	Bus	blue
36 DAY HILL RD	Bus	teal
37 NEW BRITAIN AVE	Bus	blue
38 WESTON ST	Bus	blue
39 NEW BRITAIN AVE	Bus	purple
40 NORTH MAIN ST	Bus	pink
42 BARBOUR ST	Bus	pink
43 CAMPFIELD AVE	Bus	purple
44 GARDEN ST	Bus	teal
46 VINE ST	Bus	purple
47 FRANKLIN AVE	Bus	blue
50 BLUE HILLS AVE	Bus	black
52 BLUE HILLS AVE	Bus	black
53 WETHERSFIELD AVE	Bus	blue
54 BLUE HILLS AVE	Bus	orange
55 HARTFORD/MIDDLETOWN	Bus	blue
56 BLOOMFIELD AVE	Bus	black
58 ALBANY AVE	Bus	teal
59 LOCUST ST	Bus	pink
60 FARMINGTON AVE	Bus	blue
61 BROAD ST	Bus	blue
62 FARMINGTON AVE-NORTH MAIN ST	Bus	brown
63 HILLSIDE AVE	Bus	blue
64 FARMINGTON AVE-SOUTH MAIN ST	Bus	green
66 FARMINGTON AVE-UCONN HEALTH	Bus	purple
69 CAPITOL AVE	Bus	teal
72 ASYLUM AVE	Bus	blue
74 GRANBY ST	Bus	blue
76 ASHLEY ST	Bus	orange
80 BUCKLAND FLYER	Bus	purple
82 TOLLAND ST	Bus	orange
82/84 TOLLAND ST	Bus	gray
83 SILVER LA	Bus	orange
84 TOLLAND ST	Bus	orange
86 BURNSIDE AVE	Bus	blue
87 BREWER ST	Bus	blue
88 BURNSIDE AVE	Bus	green
904 GLASTONBURY EXP	Bus	teal
904/914 GLASTNBRY/MARLBRGH/COLCHSTR EXP	Bus	blue
905 WINDSOR LOCKS/ENFIELD EXP	Bus	blue
906 CROMWELL EXP	Bus	blue
91 FORBES ST	Bus	teal
910 ROCKY HILL/CENTURY HILLS EXP	Bus	blue
912 SIMSBURY/GRANBY EXP	Bus	blue
914 MARLBOROUGH/COLCHESTER EXP	Bus	blue
92 TOWER AVE	Bus	orange
94 PARK AVE	Bus	purple
95 GLASTONBURY	Bus	orange
96 JOHN FITCH BLVD	Bus	purple
AH ASYLUM HILL CONNECTOR	Bus	blue
CB COLUMBUS BLVD CONNECTOR	Bus	green
DASH	Bus	black
SC STATE CAPITOL CONNECTOR	Bus	black
903 BUCKLAND/VERNON EXP	Bus	purple
903/913 BUCKLAND/VERNON/STORRS EXP	Bus	purple
913 BUCKLAND/STORRS EXP	Bus	purple
918 WILLIMANTIC/COVENTRY EXP	Bus	purple
950 NEW HAVEN/HARTFORD EXP	Bus	purple
PPB HARTFORD/PROVIDENCE	Bus	black

List every stop

Main St @ Atheneum Sq
Capitol Ave @ Broad St
Farmington Ave @ Prospect Ave
Corbin Ave @ Governor St
Corbin Ave @ Opp Walker Rd
Skipper St @ Helen Dr
Skipper St @ Scarlett Dr
Burritt St @ 475 Burritt St
Osgood Ave @ Lawrence St
Osgood Ave @ opp Lawrence St
Scarlett Dr @ Slater Rd
Stonegate Rd @ 51 Stonegate Rd
Marwood Dr @ 5 Marwood Dr
Marwood Dr @ 17 Marwood Dr
Marwood Dr @ 25 Marwood Dr
Corbin Ave @ Maplehurst Ave
Burritt St @ Opp Clinton St
Farmington Ave @ Alexander Rd
Farmington Ave @ Ruth Rd
Whitney Ave @ 2330 Whitney Ave
Oak St @ Allen St
McClintock St @ Eddy Glover Blvd
Stanley St @ CCSU
Stanley St @ opp CCSU
Oak St @ Allens St
Black Rock Ave @ Wooster St
Whitney Ave @ Mather St
Washington St @ Auto Zone
Washington St @ Broad St
Washington St @ 261 Washington St
Washington St @ Lasalle St
Farmington Ave @ Ward St
Farmington Ave @ Concord St
Farmington Ave @ opp Hayes St
Farmington Ave @ Allen St
Farmington Ave @ Eddy Glover Blvd
Farmington Ave @ opp Osgood Ave
Farmington Ave @ opp Richmond Ave
Farmington Ave @ opp Governor St
Farmington Ave @ Carroll St
Farmington Ave @ Pulaski Middle School
Farmington Ave @ opp Yeaton St
Farmington Ave @ Lewis Rd
Farmington Ave @ Fribbieb Dairy Barn
Colt Hwy @ Fienemann Rd
Colt Hwy @ South Rd
Fienemann Rd @ Colt Hwy
Fienemann Rd @ Farm Springs Rd
Fienemann Rd @ Batterson Park Rd
Orange St @ Wall St
Farmington Ave @ Slater Rd
Farmington Ave @ 950 Farmington Ave
Farmington Ave @ opp Lewis Rd
Farmington Ave @ Yeaton St
Farmington Ave @ Hutchinson St
Farmington Ave @ opp Eddy Glover Blvd
Farmington Ave @ McKinley Dr
Farmington Ave @ Governor St
Farmington Ave @ Richmond Ave
Farmington Ave @ Osgood Ave
Farmington Ave @ opp Allen St
Farmington Ave @ Hayes St
Farmington Ave @ Miller St
Washington St @ Lasalle St
Washington St @ 260 Washington St
Jefferson St @ Canal St
Dock St @ Canal St
Main St @ opp Lafayette St
Main St @ Lee St
North St @ opp Sexton St
North St @ opp Tremont St
North St @ opp Erwin Pl
Oak St @ North St
Oak St @ Putnam St
Oak St @ Daly Ave
Oak St @ Lasalle St
Oak St @ 253 Oak St
Carlton St @ opp Cranston Ter
Allen St @ Dudley St
Carlton St @ Allen St
Carlton St @ Roxbury Rd
Carlton St @ Stratford Rd
Carlton St @ Commonwealth Ave
Carlton St @ Eddy Glover Blvd
Eddy Glover Blvd @ opp Seneca St
Eddy Glover Blvd @ opp Tunixis St
Eddy Glover Blvd @ 303 Eddy Glover Blvd
Eddy Glover Blvd @ opp Commonwealth Ave
Commonwealth Ave @ Mcclintock St
Eddy Glover Blvd @ Hawthorne St
Eddy Glover Blvd @ Commonwealth Ave
Commonwealth Ave @ Eddy Glover Blvd
Commonwealth Ave @ opp Tunxis St
Commonwealth Ave @ Pequot St
Commonwealth Ave @ Carlton St
Commonwealth Ave @ Park Rd
Commonwealth Ave @ Stanley St
Stanley St @ Lyle Rd
Stanley St @ Blake Rd
Stanley St @ opp Chrisopher Cir
Mark Twain Dr @ University High
Stanley St @ opp Drury Ln
Stanley St @ Blake Rd
Stanley St @ opp Lyle Rd
Stanley St @ Eddy Glover Blvd
Commonwealth Ave @ Stanley St
Commonwealth Ave @ Uncas Rd
Carlton St @ Commonwealth Ave
Carlton St @ Stratford Rd
Carlton St @ Cranston Ter
Carlton St @ Roxbury Rd
Allen St @ Carlton St
Allen St @ Oak St
Oak St @ 254 Oak St
Oak St @ Lasalle St
Oak St @ Daly Ave
Oak St @ Putnam St
Oak St @ North St
North St @ Erwin Pl
North St @ Tremont St
North St @ Sexton St
Main St @ opp Lee St
Main St @ Lafayette St
Jones Hill Rd @ Bellevue Ave
Campbell Ave @ opp West Walk
Lincoln St @ Lincoln Ct
Black Rock Ave @ Opp S Burritt St
Black Rock Ave @ Sherwood Rd
Black Rock Ave @ Opp Harrison St
Black Rock Ave @ Oldfield St
Black Rock Ave @ Opp New Hampshire Dr
Black Rock Ave @ Warren St
Black Rock Ave @ Opp Texas Dr
Woodford Ave @ Mereline Ave
Woodford Ave @ Dallas Ave
Woodford Ave @ Kent St
Woodford Ave @ East St
Farmington Ave @ South Main St
E Main St @ Opp Crown St
E Main St @ opp Plainville Ctr Library
E Main St @ Norton Pl
W Main St @ opp Pierce St
W Main St @ opp Strong Ct
W Main St @ N Washington St
Forestville Ave @ opp W Main St
E Main St @ Broad St
Mountain Rd @ Middle St
Boston Post Rd @ 512 Boston Post Rd
Boston Post Rd @ 523 Boston Post Rd
Forestville Ave @ Bohemia St
E Main St @ 189 E Main St
E Main St @ Lincoln Ave
Broad St @ Central St
Broad St @ Broad Pl
Broad St @ Emmett St
Emmett St @ Broad St
South St @ Opp Ridge Rd
South St @ Opp East Rd
South St @ East St
South St @ Mellen St
South St @ Willis St
Main St @ South St
Saw Mill Rd @ Hampton Inn
Mitchell Dr @ opp Wilbur Cross High
Stafford Ave @ Fair St
Stafford Ave @ Jewel St
Stafford Ave @ Mountain View Ave
Farmington Ave @ Mix St
Farmington Ave @ Vincent Rd
Forbes St @ Blueberry Ln
Farmington Ave @ opp Morris Ave
Farmington Ave @ Hoover Ave
Farmington Ave @ Oakland St
Farmington Ave @ opp Stewart St
Farmington Ave @ Burlington Ave
N Main St @ North St
N Main St @ Center St
Forbes St @ Opp Melton Dr
West St @ School St
West St @ Gridley St
South St @ West St
Main St @ South St
South St @ Willis St
South St @ Seymour St
South St @ Emily Ln
South St @ East Rd
South St @ Ridge Rd
Sargent Dr @ Sargent Corp 2
Middle St @ Lake Ave
Middle St @ Battisto Rd
Middle St @ Cross St
Forest St @ Forest Ln
Emmett St @ Ronzo Rd
Emmett St @ Pinewood Terrace Condo
Forest St @ Opp Dorothy Rd
High St @ Goodwin St
High St @ Bellevue Ave
High St @ Main St
Mountain Rd @ Middle St
Forest St @ Opp Noch Ln
Veterans Cir @ Campbell Ave
Pine St @ Birch St
Pine St @ opp Forest St
Pine St @ Daley St
Pine St @ Stop & Shop
Pine St @ Marion St
Farmington Ave @ Raymond Rd
Forest St @ 310 Forest St
Pine St @ Overlook Ave
W Main St @ Bohemia St
W Main St @ Hoerle Ct
W Main St @ Washington St
W Main St @ Strong Ct
W Main St @ Pierce St
Bridge St @ 1st St
Alexander Rd @ Country Club Rd
Forest St @ Opp Brewer St
Stanley St @ Stanley Woods Condo
Forest St @ 228 Forest St
Stanley St @ AW Stanley Park
Stanley St @ opp Huber St
Stanley St @ Country Club Rd
Country Club Rd @ Highridge Rd
Country Club Rd @ opp Nachilly Dr
Country Club Rd @ Crestwood Ln
Alexander Rd @ 268 Alexander Rd
Alexander Rd @ Nachilly Dr
Alexander Rd @ 100 Alexander Rd
Stanley St @ Alexander Rd
Forest St @ 164 Forest St
Stanley St @ Huber St
Stanley St @ A W Stanley Park
Stanley St @ Stanley Woods Condo
Talcottville Rd @ opp Loveland Hill Rd
Tunxis Comm College @ Plainville Ave
Defco Park Rd @ opp Dodge Ave
Forest St @ 128 Forest St
Uconn Health Blvd @ Pond
Farmington Ave @ Exchange
Farmington Ave @ 308-314 Farmington Ave
Farmington Ave @ 400 Farmington Ave
Poquonock Ave @ 34-36 Poquonock Ave
Forest St @ 78 Forest St
Farm Springs Rd @ 5 Farm Springs Rd
Farm Springs Rd @ 4 Farm Springs Rd
Farm Springs Rd @ UPC Fire Security
Farm Springs Rd @ The Hartford Ins
Farm Springs Rd @ Otis Elevator
Farm Springs Rd @ Otis Elevator
Forest St @ 40 Forest St
and 9362 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — down 0.4 since 2026-07-31.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-25	41.8	first check
2026-07-30	56.1	up 14.3
2026-07-31	56.5	up 0.4
2026-08-01	56.1	down 0.4

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change
Realtime quality down 2.4

What changed in this feed

Overall score fell 0.4 points since 2026-07-31.

Same feed file as 2026-07-31; the published zip did not change.

Changed counts

up 47 of 173 trips scheduled during the sampling window had no live predictions. (45 → 47) (scorecard_rt_trip_coverage)

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-07-25 this feed started at grade F. On 2026-08-01 the grade held, though the score rose from 42 to 56. As of 2026-08-01 it holds grade F.

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

2026-07-30 Score rose 14 points, realtime rose 90 points.

Everything we checked

20 findings, ordered by severity.

Show every finding

Warning20490 instances
20490 of 20490 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)
Warning9612 instances
9612 of 9612 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)
Warning2912 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 streets or point riders to the wrong corner.
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)
Warning2622 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)
Warning47 instances
47 of 173 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
Warning29 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)
Warning8 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning6 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning6 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)
Warning6 instances
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning5 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning5 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
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)
Warning4 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · 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
1 of 20490 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info6 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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 161 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) Different (allowed): Your feed's agency_id is 4, 5, 3, 2, 1, 7, 8; your National Transit Database ID is 10048. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 4, 5, 3, 2, 1, 7, 8 to NTD ID 10048, and keep the feed value stable. Do not change it solely to make the two values equal.

shapes.txt covers your trips Ready: All 20490 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 161 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.

Realtime reliability

The realtime feed responded on 68.5% of 200 checks over the last 34 days, with 3s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Live predictions vs schedule

Arrival predictions ran a median 128s late versus the schedule, and stayed within 510s nine times in ten. They were on time (about a minute early to five late) 69.7% of the time. 98.6% of reported vehicle positions sat on or near the published route shape.

From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.

Clears the Google and Apple Maps four-week coverage bar. This feed has 161 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 33 / 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 85 / 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 38 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 90 / 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.

[![Connecticut Transit GTFS data quality grade: F](https://gtfsscorecard.org/data/artifacts/connecticut-transit/badge.svg)](https://gtfsscorecard.org/agency/connecticut-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/connecticut-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). Connecticut Transit GTFS feed-quality record, dated 2026-08-01 (grade F (56.1/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 86b8fd94ea73…). https://gtfsscorecard.org/data/artifacts/connecticut-transit/2026-08-01.json

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

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