# Pune–Mumbai Expressway Report 2026: 1,158 Trips Measured | Orbitmiles Source: https://orbitmiles.in/expressway-report/ Trip data to 16 September 2026 · page updated 8 October 2026 ### The Pune–Mumbai Expressway Report Almost everything written about this corridor quotes a route-planner estimate. This page does not. It reports what actually happened on **1,158 completed Pune–Mumbai trips** we operated between 26 February 2026 and 16 September 2026 — measured from our drivers' own odometers and trip timestamps. **Median door-to-door journey** 3h 23m n = 299 measured trips **Median distance actually driven** 146 km middle half: 138–154 km **Cost of leaving at the wrong hour** +67 min afternoon vs late night Corridor news #### Corridor updates, October 2026 Last updated: 8 October 2026 What changed on the Pune–Mumbai route recently, checked against official notices or at least two news reports. We refresh this list every month. Orbitmiles' fixed ₹2,700 fare already includes the Mumbai–Pune Expressway toll: ₹320 one-way for a car, and ₹0 for our three electric cars, which are toll-exempt in Maharashtra. The hybrid Innova Hycross pays the toll, and that is inside its fare too. 1. 8 October 2026 · **Diwali 2026: Lakshmi Pujan on Sunday 8 November, Padwa on Tuesday 10 November** · The Maharashtra government's 2026 holiday list puts Lakshmi Pujan on Sunday 8 November and Diwali Padwa (Bali Pratipada) on Tuesday 10 November, with Bhaubeej on 11 November. Expect the Pune to Mumbai and Mumbai to Pune runs to be busiest on the days just before and after that stretch. Our trip data on this page shows afternoon starts are the slowest on any day, so a late-night or early-morning departure is the safer choice during the festival week. Orbitmiles fares are fixed and do not rise on festival days; one-way fares start at ₹2,700. · Sources: Maharashtra General Administration Department 2026 holiday list, as reported by LatestLY and Sakshi Post; Drik Panchang (Lakshmi Pujan date) 2. 7 October 2026 · **MSRTC starts e-Shivai electric buses from Navi Mumbai airport to Pune** · The Maharashtra State Road Transport Corporation began e-Shivai electric bus services from Navi Mumbai International Airport (NMI) on 7 October, with routes to Dadar, Borivli and Pune. Services to Thane and Nashik are planned by mid-November. For travellers landing at NMIA, this adds a scheduled public option on the Pune run alongside private cabs. It does not change Orbitmiles fares; our fixed one-way fare to or from NMIA is the same as for any Mumbai pickup. · Sources: Swarajya; Maritime Gateway 3. 9 September 2026 · **Rockfall mesh going up at the Missing Link landslide site** · MSRDC has started fitting Swiss-made steel rockfall mesh on the hill slope above Tunnel 2 of the Missing Link, following IIT Bombay's recommendations after the July landslide. About 15% of the mesh work was complete in early September, and the plan also includes rock anchors, stepped slopes and diverted rainwater channels above the tunnel. Our fare does not depend on which alignment the driver takes. · Sources: Free Press Journal; Swarajya 4. 15 July 2026 · **Navi Mumbai International Airport starts international flights** · Navi Mumbai International Airport (IATA code NMI) began scheduled international operations on 15 July 2026, with Air India Express flying to Abu Dhabi. The airport opened for domestic flights on 25 December 2025. Pune travellers flying abroad now have a second Mumbai-region airport to check; it sits closer to the Expressway than the main Mumbai airport. Orbitmiles charges the same fixed one-way fare to NMIA as to any Mumbai drop. · Sources: NBM&CW; Outlook Traveller; Aletihad 5. 6 July 2026 · **Landslide closes the Missing Link near Tunnel 2 for about 19 hours** · Heavy overnight rain brought down part of the hill slope near the exit of Tunnel 2 on the Missing Link at about 3:30 am on 6 July, killing three people. Traffic was diverted to the old ghat route and resumed on the Missing Link at 10:10 pm, initially on only two lanes while water kept flowing off the hillside. On days like this the old Khandala ghat road takes over and the drive runs longer. Orbitmiles fares stay fixed when the route is diverted. · Sources: Free Press Journal; Business Standard; The Wire 6. 1 May 2026 · **Missing Link opens, with no extra toll; the car toll stays ₹320** · The 13.3 km Missing Link between Khopoli and Kusgaon opened on 1 May 2026. It bypasses the Khandala ghat section through two tunnels and a cable-stayed bridge over Tiger Valley, cutting about 6 km and, by MSRDC's estimate, 20 to 30 minutes off the trip. No separate toll is charged for it, so cars still pay ₹320 one way at Urse and Khalapur, and electric cars have been toll-exempt on the Expressway since 22 August 2025. Orbitmiles' fixed fare already includes the toll and did not change. · Sources: Moneylife; ETV Bharat; Free Press Journal; The Tribune (EV toll exemption) Finding 01 #### Departure hour costs more than direction, day or season We grouped all 299 measured trips by the hour the driver actually started, in IST. The gap between the best and worst block is **67 minutes** — more than an hour of your day, decided before you get in the car. Bars show the median. The black whisker spans the middle half of trips (25th to 75th percentile), so you can see how much the block varies, not just its average. Total sample 299 trips. The practical reading: a 2 PM departure is the one to avoid. Leaving before 6 AM buys back about an hour against it, and the late-night block is also the most predictable — its middle half sits inside a 44-minute band, against 46 minutes for the afternoon but starting an hour earlier. If your arrival time genuinely matters, that consistency is worth as much as the raw saving. Finding 02 #### A Pune–Mumbai trip is a 3h 23m day, not a two-hour drive The expressway itself is the short part. Measured from the moment the driver starts the trip to the moment it is closed at the destination, the median Pune–Mumbai journey runs **203 minutes**. The middle half of trips land between 2h 54m and 3h 58m. That figure includes everything a route planner leaves out: reaching you in city traffic, loading, the approach to the expressway, any stop en route, and the crawl at the far end. We are publishing it precisely because it is the number people actually plan badly around — treat the corridor as a two-hour drive and you will miss flights. 3h 35m Pune to Mumbai median · n=165 3h 17m Mumbai to Pune median · n=134 18 min Direction penalty Pune→Mumbai runs slower The 18-minute direction gap is real but modest — roughly a quarter of the 67-minute swing from departure hour. Choose your hour before you worry about your direction. Finding 03 #### The real trip is 146 km — and it varies by 16 km either way Odometer readings from 299 trips give a median driven distance of **146 km**, with the middle half between 138 km and 154 km and the full range running 106–183 km. The spread is the point. "Pune to Mumbai" is not one journey — a Hinjewadi-to-Andheri run and a Kothrud-to-Panvel run differ by more than 40 km, and per-kilometre pricing quietly passes that variation to whoever happens to be travelling. It is the single clearest argument for pricing the corridor as a fixed route rather than by the metre, which is how we do it. One cost on this route does not vary at all: the expressway toll is **₹320 one way** for a car, collected at two plazas — ₹240 at Urse and ₹80 at Khalapur. Battery-electric vehicles are exempt under Maharashtra's EV policy and pay ₹0; our hybrid Innova Hycross pays the full ₹320. You can work through the whole toll picture on our [Mumbai–Pune toll calculator](https://orbitmiles.in/toll-calculator/). Finding 04 #### Weekends are not slower. That surprised us too. The corridor's reputation says Friday evening and Sunday are the bad times. In our data they are not: the median weekday journey is **202 minutes** (n=196) against **205 minutes** on Saturdays and Sundays (n=103). A three-minute difference across 299 trips is noise. We are reporting this because a null result is still a result, and because it reinforces Finding 01: on this corridor, *when in the day* you leave matters far more than *which day* you leave. If you are shifting a trip to dodge weekend traffic, you are optimising the wrong variable. The operating record behind the data #### 1,158 corridor trips, 997 of them electric 1,158 Completed corridor trips 26 February 2026 – 16 September 2026 997 Run on an electric vehicle 86% of corridor trips ~25–30 t CO₂ not emitted at 25–30 kg per petrol trip The CO₂ figure is arithmetic, not measurement: 997 electric corridor trips multiplied by the 25–30 kg a comparable petrol car emits over the same route. We show it as a range because the per-trip figure is one. The workings are in our [Mumbai–Pune carbon footprint comparison](https://orbitmiles.in/blogs/carbon-footprint-mumbai-pune-travel/). #### How this was measured ##### Where the numbers come from Every figure on this page comes from Orbitmiles' own booking records — our drivers' recorded start and end odometer readings and their trip start and end timestamps, stored in our operations system. Nothing here is modelled, estimated by a route planner, or drawn from a third party. Route-planner distance and duration estimates are stored alongside these records; we deliberately do not use them, because they are predictions rather than observations. ##### How the sample was built 1. Start with all completed bookings between 26 February 2026 and 16 September 2026, and keep those whose pickup and drop fall on opposite ends of the Pune–Mumbai corridor: **1,158 trips**. 2. Keep only one-way trips, so a round trip's return leg cannot be counted as a slow single journey: **1,129 trips**. 3. Keep only trips where the driver recorded *both* a start and end odometer reading *and* a start and end trip timestamp: **374 trips**. 4. Discard records that cannot describe a real corridor run — distance outside 100–220 km, or duration outside 75–300 minutes. These are mis-keyed odometers and trips a driver forgot to close; one record shows 150 km covered in 19 seconds. This removed **75 records (20%)**. 5. Final measured sample: **299 trips**. Every duration and distance statistic on this page is drawn from exactly this set. ##### What "door to door" means here It means trip-open to trip-close in the driver's app: from the start of the journey to the driver closing it at the destination. It therefore includes city driving at both ends, loading, and any stop en route. It is *not* expressway running time, and it should not be compared with one. Because it depends on a driver closing the trip promptly, the upper tail is likely a little generous — which is why we lead with the median rather than the mean, and publish the quartiles beside it. ##### Why medians, not averages Journey times have a long right tail — a handful of very slow trips would drag an average somewhere no traveller ever experiences. The median is the middle trip, and the quartiles either side show the honest spread. ##### What we are not claiming yet We also run in-car telemetry across part of the fleet, sampling position, speed and battery state every few minutes. At the time of writing that data spans a single week across four vehicles — enough to sanity-check these findings, nowhere near enough to publish. So this report contains **no** claim about expressway-only running time, battery consumption per trip, the effect of air conditioning on range, or any before-and-after comparison around the Missing Link opening: our telemetry begins months after it opened, so an honest comparison is not available to us. We would rather publish four findings we can defend than eight we cannot. Those sections will appear here when the sample supports them. ##### Sample size, stated plainly 299 measured trips is a real sample but a modest one, and the per-block counts behind Finding 01 range from 48 to 71 trips. Treat the block medians as solid and the finer splits as indicative. Our capture rate is the limiting factor: 33% of one-way corridor trips carry complete driver records, and improving that is the fastest route to a stronger report. #### Using these figures You are welcome to quote or republish any figure on this page, in print or online, with attribution to Orbitmiles and a link back. If you need a cut we have not published — a specific corridor pair, a month-by-month series, or the underlying distribution — write to [orbitmiles@gmail.com](mailto:orbitmiles@gmail.com) and we will share what the sample honestly supports. > Orbitmiles, *The Pune–Mumbai Expressway Report* , 16 September 2026. Based on 299 measured trips from 1,158 completed Pune–Mumbai journeys. https://orbitmiles.in/expressway-report/ #### Related guides - [Best time to travel the Mumbai–Pune Expressway](https://orbitmiles.in/blogs/mumbai-pune-expressway-best-time-to-travel/) The practical version of Finding 01. - [Mumbai–Pune toll calculator](https://orbitmiles.in/toll-calculator/) ₹320 one way at two plazas, and why EVs pay ₹0. - [The Missing Link, explained](https://orbitmiles.in/blogs/mumbai-pune-missing-link-opening-2026/) What changed on the route in May 2026. - [Expressway rest stops](https://orbitmiles.in/blogs/mumbai-pune-expressway-rest-stops/) Where the stops in our journey times actually happen. - [Monsoon travel on the corridor](https://orbitmiles.in/blogs/mumbai-pune-monsoon-travel-guide/) The season that runs through most of this sample. - [Mumbai–Pune carbon footprint](https://orbitmiles.in/blogs/carbon-footprint-mumbai-pune-travel/) Where the 25–30 kg per trip figure comes from. #### Travelling the corridor yourself? Fixed fares, no surge, and a driver who knows which hour to leave. Same route, measured 1,158 times. [Book your cab](https://orbitmiles.in/book/) [WhatsApp us](https://wa.me/918484876369) [Call +91 90676 76369](tel:+919067676369)