Halfway point between Las Vegas and Tulsa
17 h 40 drive apart · meet in Santa Fe, NM · about 10 estimated hotels there
The route at a glance
Estimated route sketch for the Las Vegas–Tulsa 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
The fairest meeting point splits the driving time, not the map distance.
The 1130.3 mi run from Las Vegas to Tulsa takes an estimated 17 h 40 without traffic and trends east for most of the drive. Measured in time rather than distance, the halfway point lands near Santa Fe, NM, about 63 mi from the center of town — the spot where each driver has spent exactly half the total trip behind the wheel.
Honesty first: the half-time point itself sits in open country — our town map has nothing within 60 miles of it. The towns below are the nearest mapped places of any size, ranked by how sane a meeting they make; Santa Fe is the closest at roughly 63 miles from the true midpoint. Every number is computed for the Las Vegas–Tulsa pair specifically, and all drive times are traffic-free estimates.
The nearest towns to the Las Vegas–Tulsa midpoint
No mapped town sits within 60 miles of this pair's half-time point, so these are the nearest real places — treat the drive times as the honest cost of meeting here, and consider meeting in one of the two endpoint cities instead if the split looks lopsided.
Santa Fe, NMBest match
- From Las Vegas
- 8 h 32
- From Tulsa
- 9 h 14
- Detour
- +6 min
- Hotels (est.)
- ~10
Santa Fe is the seat of Santa Fe County with a population of 87,825 and an estimated 10 places to sleep. Meeting there adds about 6 minutes to the combined drive.
We may earn a commission when you search Kayak through our links.
Where to sleep in Santa Fe
10 estimated lodging properties in Santa Fe (Santa Fe 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 Santa Fe, leave Las Vegas around 10:28 am and Tulsa around 9:46 am — you both arrive by 7 pm, with only 42 minutes difference in total driving.
- The split through Santa Fe is 48.0% / 52.0% of the 17 h 40 drive.
- Want to wake up closer to Tulsa? Raton moves the split to 55.3% / 44.7% for about 10 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. Santa Fe splits the 17 h 40 run at 48.0% for the Las Vegas driver and 52.0% for the Tulsa 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 point | From Las Vegas | From Tulsa | Total via point | Detour vs direct |
|---|---|---|---|---|
| Santa Fe, NM — primary meeting town | 8 h 32 | 9 h 14 | 17 h 46 | +6 min |
| Raton, NM | 9 h 52 | 7 h 58 | 17 h 50 | +10 min |
| Las Vegas, NM | 9 h 13 | 8 h 35 | 17 h 48 | +8 min |
| 40/60 split point (near Aztec, NM) | 7 h 12 | 10 h 36 | 17 h 48 | +8 min |
| 60/40 split point | 10 h 36 | 7 h 12 | 17 h 48 | +8 min |
All times estimated, traffic-free (straight-line × road factor). Detour compares the via-point drive with the direct Las Vegas–Tulsa estimate of 17 h 40.
Around the midpoint
Beyond the three meeting towns, the middle of the Las Vegas–Tulsa corridor has a few more places worth knowing. These are the seeded towns closest to Santa Fe:
The nearest major city to Santa Fe is Albuquerque, NM, about 1 h 46 southwest — handy if a third person is joining by plane from ABQ.
Point-of-interest listings — parks, museums, roadside attractions — arrive with the mapped-data upgrade. We would rather show computed neighbors than invented sights.
Las Vegas and Tulsa, 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 1130.3 mi drive.
Las Vegas, NV
Tulsa, OK
Las Vegas keeps Pacific time and Tulsa keeps Central — a 2-hour difference. Drive times are clock-agnostic, but wall clocks are not: leave Las Vegas at 9:00 am and, after the 17 h 40 estimated drive, it is about 4:40 am the following day in Tulsa. Clock-change weeks can shift this by an hour.
Fly instead?
Driving between Las Vegas and Tulsa costs an estimated 17 h 40 behind the wheel. The great-circle distance is only 1066.3 mi; at a 460 mph cruise with 90 minutes of airport overhead folded in, flying works out to roughly 3 h 49 gate-to-gate — an estimate, not a schedule. Airport transfers, security, and boarding eat some of that edge, so the honest comparison is 17 h 40 of driving versus about 3 h 49 from curb to curb when the connections behave. If the plane wins for your dates, switch the meeting-town card above to the Flights tab for a live search.
Search cars, hotels & flights
We may earn a commission when you search Kayak through our links.
Common questions
What is the halfway point between Las Vegas and Tulsa?
What is the biggest town between Las Vegas and Tulsa?
Is there a spot that is exactly 50/50?
Where should we stay overnight between Las Vegas and Tulsa?
How long is the drive from Las Vegas to Tulsa?
Should we fly between Las Vegas and Tulsa instead?
More halfway guides
From here you can branch two ways: every other halfway guide from Las Vegas or from Tulsa, or pairs whose midpoint lands near this one. Siblings share a city; the last few share the same stretch of map. Driving the whole route instead? The overnight stop plan for Las Vegas–Tulsa splits it into driving days.
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.