Explore/Beacon Falls/Stop ID 4910

◎

Connecticut Transit / BOARDING STOP

Farren Ave @ Fairmont Ave

Stop code FARFAIN · Connecticut Transit network

Next departures

America/New_York

206

206 - Downtown New HavenScheduled · estimated time

32 min6:24 PM · Sat, Oct 31

206

206 - Downtown New HavenScheduled · estimated time

7:17 PM7:17 PM · Sat, Oct 31

206

206 - Downtown New HavenScheduled · estimated time

8:15 PM8:15 PM · Sat, Oct 31

206

206 - Downtown New HavenScheduled · estimated time

9:15 PM9:15 PM · Sat, Oct 31

206

206 - Downtown New HavenScheduled · estimated time

10:15 PM10:15 PM · Sat, Oct 31

206

206 - Downtown New HavenScheduled · estimated time

11:15 PM11:15 PM · Sat, Oct 31

206

206 - Downtown New HavenScheduled · estimated time

12:15 AM12:15 AM · Sun, Nov 1

206

206 - Downtown New HavenScheduled · estimated time

1:15 AM1:15 AM · Sun, Nov 1

206

206 - Downtown New HavenScheduled · estimated time

8:12 AM8:12 AM · Sun, Nov 1

206

206 - Downtown New HavenScheduled · estimated time

9:12 AM9:12 AM · Sun, Nov 1

206

206 - Downtown New HavenScheduled · estimated time

10:27 AM10:27 AM · Sun, Nov 1

206

206 - Downtown New HavenScheduled · estimated time

11:27 AM11:27 AM · Sun, Nov 1

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 ↗