Driving from Rochester to Markham
Markham lies 155 km (96 mi) north-west of Rochester, in the same time zone. What the numbers say about getting there.
Driving takes about 2 h 6 min without stops, over roughly 189 km (117 mi) of road; add breaks, fuel and any border.
| Rochester | Markham | |
|---|---|---|
| Country | United States | Canada |
| Population | 209,802 | 338,503 |
| Elevation | 156 m (512 ft) | 168 m (551 ft) |
| Time now | UTC-4 (America/New_York) | UTC-4 (America/Toronto) |
What changes when you arrive in Markham
Crossing from United States into Canada: money changes from the Dollar to the Dollar (CAD); the dialling code becomes +1; the emergency number is http://www.wikidata.org/entity/Q533806.
Where to book car hire from Rochester to Markham
We take no bookings for these providers and hold no reservation with them. The provider you choose handles payment, confirmation, changes and refunds. How that works.
Staying in Markham
Live rooms and prices for Markham are in the search below.
Book a hotel in Markham
Live rooms and prices from our booking partner, booked and paid for here. Free cancellation is marked where it applies.
Common questions
How far is Markham from Rochester?
155 km (96 mi) in a straight line, north-west of Rochester; by road roughly 189 km (117 mi).
How long does it take to get from Rochester to Markham by car?
About 2 h 6 min, estimated from distance and typical speeds. Timetables and traffic decide the real figure.
Is there a time difference between Rochester and Markham?
No, both are on the same offset at the moment.
What currency do I need in Markham?
The Dollar (CAD).
Where these facts come from
- GeoNames (CC BY 4.0): population, elevation, time zone, postal codes
- Wikidata (CC0): area, sister cities, visitor numbers, heritage listings, stations and ports
- OurAirports (public domain): airports, runways
- Natural Earth (public domain): map outlines
Data compiled 13 September 2026. Hotel figures are from our booking partner’s catalogue on that date. Journey times on this page are estimates from distance, not timetables; check the operator before you rely on one.