Halfway point between Detroit and Lansing

1 h 44 drive apart · meet in Flint, MI · about 10 estimated hotels there

1 h 44 total drive89.9 miMeet in Flint, MI1 h 45 from Detroit1 h 28 from Lansingestimated drive times

The route at a glance

Detroit Lansing Flint Ann Arbor Jackson half-time point 25 mi Estimated route line Origin / destination city Meeting town Half-time point

Estimated route sketch for the Detroit–Lansing drive (straight-line basis — turn-by-turn road geometry arrives with the routing upgrade). Markers: both cities, the three meeting towns, and the half-time point.

The halfway point

"Halfway" is a time budget before it is a place — half the drive for each of you.

The 89.9 mi run from Detroit to Lansing takes an estimated 1 h 44 without traffic and trends west for most of the drive. Measured in time rather than distance, the halfway point lands near Ann Arbor, MI, about 18 mi from the center of town — the spot where each driver has spent exactly half the total trip behind the wheel.

We rank the towns below by a blend of split fairness, detour off the direct line, town size, and estimated hotel supply. On this route that puts Flint first, Ann Arbor second, and Jackson third. Every number on this page is computed for the Detroit–Lansing pair specifically, and all drive times are traffic-free estimates.

The three meeting towns between Detroit and Lansing

We scored every seeded town near the halfway point of the 1 h 44 drive. Flint came out on top — here is how the splits and detours compare.

Flint, MIBest match

Genesee County · county seat · 81,252 residents

From Detroit
1 h 45
From Lansing
1 h 28
Detour
+89 min
Hotels (est.)
~10

The seat of Genesee County, Flint counts 81,252 residents and sits 1 h 45 out of Detroit versus 1 h 28 from Lansing — a 54.4% / 45.6% split of the driving.

Check hotel rates in Flint for tonight →

We may earn a commission when you search Kayak through our links.

Where to sleep in Flint

10 estimated lodging properties in Flint (Genesee County) — chains and independents; confirm directly with the hotel. Counts in this early version are population-derived estimates, not live listings.

  • For a 7 pm dinner in Flint, leave Detroit around 5:15 pm and Lansing around 5:32 pm — you both arrive by 7 pm, with only 17 minutes difference in total driving.
  • The split through Flint is 54.4% / 45.6% of the 1 h 44 drive.
  • Want to wake up closer to Lansing? Ann Arbor moves the split to 41.0% / 59.0% for about 56 extra minutes.

Drive-time splits

Fairness comes down to minutes. The table shows, for each candidate meeting point, how long each driver spends behind the wheel and what the stop adds to the combined drive. Flint splits the 1 h 44 run at 54.4% for the Detroit driver and 45.6% for the Lansing driver. The 40/60 and 60/40 points mark where one driver takes the longer share — useful when one of you needs to be home earlier.

Meeting pointFrom DetroitFrom LansingTotal via pointDetour vs direct
Flint, MI — primary meeting town1 h 451 h 283 h 13+89 min
Ann Arbor, MI1 h 061 h 352 h 41+56 min
Jackson, MI1 h 381 h 032 h 41+57 min
40/60 split point (near Ann Arbor, MI)1 h1 h 302 h 30+46 min
60/40 split point (near Ann Arbor, MI)1 h 301 h2 h 30+46 min

All times estimated, traffic-free (straight-line × road factor). Detour compares the via-point drive with the direct Detroit–Lansing estimate of 1 h 44.

Around the midpoint

Beyond the three meeting towns, the middle of the Detroit–Lansing corridor has a few more places worth knowing. These are the seeded towns closest to Flint:

  • Saginaw, MI — about 57 min from Flint (population 43,823).
  • Bay City, MI — about 1 h 16 from Flint (population 32,917).

The nearest major city to Flint is Toledo, OH, about 2 h south — handy if a third person is joining by plane from TOL.

Point-of-interest listings — parks, museums, roadside attractions — arrive with the mapped-data upgrade. We would rather show computed neighbors than invented sights.

Detroit and Lansing, side by side

A meeting point is only fair if both drivers know what they are signing up for. Here is the context at each end of the 89.9 mi drive.

Detroit, MI

Population 639,000Detroit-Warren-Dearborn MI metroEastern time

Lansing, MI

Population 112,644Lansing MI metroEastern time

Detroit keeps Eastern time and Lansing keeps Eastern — a 0-hour difference. Drive times are clock-agnostic, but wall clocks are not: leave Detroit at 9:00 am and, after the 1 h 44 estimated drive, it is about 10:44 am in Lansing. Clock-change weeks can shift this by an hour.

Search cars, hotels & flights

We may earn a commission when you search Kayak through our links.

Common questions

What is the halfway point between Detroit and Lansing?
Flint, MI. It sits an estimated 1 h 45 from Detroit and 1 h 28 from Lansing, splitting the 1 h 44 drive roughly in half.
What is the biggest town between Detroit and Lansing?
Ann Arbor, MI — population 123,851 — the largest of the 3 towns we ranked near the midpoint.
Is there a spot that is exactly 50/50?
Almost never on real roads. The half-time point on this route falls near Ann Arbor, MI; the closest practical base is Flint, which splits the driving within 17 minutes.
Where should we stay overnight between Detroit and Lansing?
Flint is the default pick, with an estimated 10 lodging properties — chains and independents. Confirm availability directly with the hotel. For timing, a Friday or Saturday meet-up gives you the most options; check the Flint forecast a day or two before you commit to a date, since town-level climate data arrives in a later update.
How long is the drive from Detroit to Lansing?
An estimated 1 h 44 covering about 89.9 mi, computed traffic-free from a straight-line road-factor model. Budget extra for stops, fuel, and rush hour at either end.

More halfway guides

From here you can branch two ways: every other halfway guide from Detroit or from Lansing, or pairs whose midpoint lands near this one. Siblings share a city; the last few share the same stretch of map.

Data & method

Towns come from a GeoNames-derived seed inventory; drive times are traffic-free estimates built from straight-line distance and a road factor — no routing engine yet. Hotel counts are population-derived estimates, not live inventories. Mapped hotels, road-level routing, and climate normals arrive with the next data upgrade. We may earn a commission when you search Kayak through our links.