TRANSIT
ATLAS
Explore/Beacon Falls/Stop ID 4910
◎

Connecticut Transit / BOARDING STOP

Farren Ave @ Fairmont Ave

Stop code FARFAIN · Connecticut Transit network

Farren Ave @ Fairmont Ave

Next departures

America/New_York
206
206 - Downtown New HavenLive · estimated time
9 min8:13 AM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
39 min8:43 AM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
9:13 AM9:13 AM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
9:53 AM9:53 AM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
10:33 AM10:33 AM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
11:13 AM11:13 AM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
11:53 AM11:53 AM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
12:33 PM12:33 PM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
1:13 PM1:13 PM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
1:53 PM1:53 PM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
2:33 PM2:33 PM · Thu, Oct 29
206
206 - Downtown New HavenScheduled · estimated time
3:13 PM3:13 PM · Thu, Oct 29
Live predictions availableRefreshes every 30 seconds

Routes at this boarding location

206
Connecticut Transit · Bus

EAST CHAPEL ST

Schedules, stops & departures
↗

Other stops nearby

◎Townsend Ave @ opp Burwell St↗◎Townsend Ave @ Burwell St↗◎Forbes Ave @ Chamberlain St↗◎Forbes Ave @ Chamberlain St↗◎Townsend Ave @ Woodward Ave↗◎Fairmont Ave @ Quinnipiac Ave↗◎Fairmont Ave @ Quinnipiac Ave↗◎Farren Ave @ Fulton St↗◎Farren Ave @ Fulton St↗◎Farren Ave @ Lancraft St↗◎Farren Ave @ Lancraft St↗

Nearby locations are based on coordinates; walking connections have not been verified.

✓
Published Connecticut Transit schedule

Imported Oct 24, 2026 · 04:37 UTC · Service dates 2026-08-30 through 2027-01-09. See data status

Schedule data published by Connecticut Transit. Feed discovery and cached source archives from MobilityData. Source details ↗