Explore/Beacon Falls/Stop ID 5350

◎

Connecticut Transit / BOARDING STOP

Main St @ Martin St

Stop code MAIMARE · Connecticut Transit network

Main St @ Martin St

Next departures

America/New_York

265

265S - Savin RockScheduled · estimated time

5:41 AM5:41 AM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

7:28 AM7:28 AM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

8:13 AM8:13 AM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

9:25 AM9:25 AM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

10:30 AM10:30 AM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

11:30 AM11:30 AM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

12:30 PM12:30 PM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

1:37 PM1:37 PM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

2:45 PM2:45 PM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

3:39 PM3:39 PM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

4:14 PM4:14 PM · Fri, Oct 30

265

265S - Savin RockScheduled · estimated time

5:23 PM5:23 PM · Fri, Oct 30

Live predictions availableRefreshes every 30 seconds

Routes at this boarding location

265

Connecticut Transit · Bus

CONGRESS AVE

Schedules, stops & departures

↗ 271

Connecticut Transit · Bus

KIMBERLY AVE

Schedules, stops & departures

↗

Other stops nearby

◎Court St @ Campbell Ave↗◎Campbell Ave @ Church St↗◎Campbell Ave @ Curtiss Pl↗◎Campbell Ave @ Main St↗◎Main St @ Campbell Ave↗◎Campbell Ave @ Main St↗◎Main St @ Campbell Ave↗◎Main St @ Washington Ave↗◎Main St @ Washington Ave↗◎Main St @ opp Martin St↗◎Main St @ Union Ave↗◎Main St @ Union Ave↗

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 ↗