LibraryReportsThe Storm Tax — Mumbai–Pune Corridor
IntugineIntugine · Logistics Intelligence
India Freight Data
Report No. 04

The Storm Tax on Trips Touching the Mumbai–Pune Corridor

In the first week of July, rain 253% above normal fell on a season running 7% below it. We analysed a sample of 4,586 trips drawn from the much larger volume live on the platform that week. Trips touching the Mumbai–Pune belt were delayed at nearly twice the national rate — and the median delayed trip stretched from 6 hours to 50.

A monsoon burst is a natural experiment. For seven days, one violent weather system sat over the Konkan coast and the Pune ghats — a red alert across Mumbai, Thane and Raigad, the Mumbai–Goa highway halted for over a day by flooding, a landslide on the Expressway's Missing Link. Everywhere else, it was an ordinary week.

From the much larger volume of trips running on the platform that week, we drew a sample of 4,586: 3,036 trips that started, ended or ran between Mumbai and Pune, against 1,550 trips across the rest of India — the control group. Same platform, same week, same measurement. Only the sky was different.

4,586
Trips in the sample
47%
Corridor trips delayed vs 27% nationally
50h
Median delayed trip on the red-alert day
2,621
Truck-days tied up in delayed corridor trips
01 / THE WEEK THE SKY BROKE

A violent spike on a normal season

This wasn't a wet year finally overflowing. Going into July, Maharashtra's monsoon was running slightly below normal. Then one system parked itself over the coast.

+253%
Maharashtra daily rainfall vs normal, 6 July (29.3mm vs 8.3mm)
+138%
Month-to-date rainfall vs normal
−7%
Full-season cumulative vs normal — a normal year, one violent week

IMD's subdivision outlook, issued 7 July, drew the geography precisely: the freight arteries in red, the interior in green.

Subdivision (freight relevance)7 Jul8 Jul9 Jul10 Jul11 Jul12 Jul13 Jul
Konkan & Goa — Mumbai–Goa NH, port beltREDORGYLW
Madhya Maharashtra — Pune, Expressway ghatsREDORGYLW
Mumbai metro & ThaneYLWYLWYLWYLW
Vidarbha — Nagpur interiorORGYLW
Marathwada — the dry interior

IMD district-warning outlook by meteorological subdivision · RED = extremely heavy rain · ORG = very heavy · YLW = heavy

02 / THE STORM CURVE

Delays tracked the alerts, day by day

Each day, the share of corridor trips missing their ETA climbed with the weather — peaking at 53% on the red-alert day — while the rest of the country held in the twenties. Hover any day to read it.

Share of trips delayed, by completion day · background = IMD alert level
Day 6 Jul
52.6% delayed
481 corridor trips completed. The median delayed trip ran 50.1 hours door-to-door. Control group: 23.6%.
RED — extremely heavy rain
03 / WHAT “DELAYED” MEANT

Not hours late — days long

The flag understates it. When a corridor trip missed its ETA that week, it didn't slip by a margin — it ran long. The median delayed trip's door-to-door time grew eightfold across the week, from 6 hours on 1 July to 50 hours on the 6th.

39%
Of delayed corridor trips ran 48h+ door-to-door
64%
Delay rate on the direct Mumbai↔Pune lane (111 trips)
157h
The longest delayed trip — six and a half days
Why this is an Intugine problem

The forecast was public. The ETAs didn't read it.

Every alert in this report was published by IMD before the trucks rolled. A dispatcher who saw the red band over Konkan on the outlook grid could have held loads, re-sequenced deliveries, or reset customer promises a day early. Most didn't — because weather lives in one system and trips live in another.

Intugine's Control Tower fuses the two: live IMD warning layers on every lane, ETAs that price in the alert level ahead, and exception flags the moment a route enters a red subdivision — so the storm tax shows up in the plan, not the postmortem.

See it on your lanes →
04 / THE SAME STORM, EIGHT INDUSTRIES

Network design decided who paid

The spread across industry segments ran from 19% to 74% — and it wasn't random. Short-haul, high-frequency express networks absorbed the shock; long-haul point-to-point industrial freight had nowhere to go. Time-windowed infrastructure deliveries into the flooded metro fared worst of all.

Three readings from the spread. Express & e-commerce (35%) run hub-to-hub shuttles with slack built in — a six-hour slip absorbs into the next sort cycle. Cement, chemicals and other plant-to-plant freight showed mid-range delay rates but the worst severity — once a long-haul truck was stuck, it stayed stuck for two days or more. And metals & mining (19%) looks resilient mainly by geography: its lanes enter Pune from the east, through the exact subdivisions IMD kept green all week.

05 / METHOD

How this was built

Approach. We analysed a sample of 4,586 completed trips, drawn from the much larger volume monitored on the Intugine platform between 1 and 7 July 2026. Using origin and destination coordinates, 3,036 trips were classified to the Mumbai–Pune belt (Mumbai metro including Thane, Navi Mumbai, Bhiwandi and the port belt; Pune including PCMC–Chakan); the remaining 1,550 trips nationwide form the control group. A trip counts as delayed when it missed its planned ETA on the platform; severity figures describe the door-to-door duration of delayed trips. The weather layer combines IMD daily rainfall statistics and subdivision-level warnings. Shipper identities are anonymised to industry segments.

Sources. Intugine platform trip data; India Meteorological Department (IMD).

Caveats. This covers a single event week, not a seasonal baseline; delay is measured against planned platform ETAs; the comparison shows a strong alignment between alert levels and delays over one event, and should be read as such.

THE STORM TAX · India Freight Data No. 04 · Built by Intugine · intugine.com
Multimodal supply chain visibility for cement, metal, coal & power · Control Tower · IntuTrack 2.0

More Reports