Routing North India Exports: Evaluating Mundra vs Nhava Sheva Dwell Times and Ocean Freight Schedules

Routing North India Exports: Evaluating Mundra vs Nhava Sheva Dwell Times and Ocean Freight Schedules

If your supplier sits in Ludhiana, Panipat, Jaipur, Noida, or Moradabad, the ocean leg does not start at the factory gate. It starts after a truck or a rail rake, a yard wait, and a vessel cutoff. Mundra and Nhava Sheva are the two gateways that usually decide that clock for North India cargo. Picking the nearer pin on a map, or accepting a quote that only says FOB India, is how you inherit a lead time that was never real.

At Netyex, export logistics sits in the same file as supplier verification and quality control. India sourcing only stays predictable when the factory, the inspection, and the ship are on one timeline. We do not hand you a directory and a sailing slogan. We name the port, check the string, and tell you where the days actually go. If you want the buyer-side model before the port detail, the short version is on About Netyex.

Two ports, two different jobs

Mundra (INMUN) is on the Gujarat coast. A briefing on platton.ai describes it as India's largest container port and the primary gateway for west and north India suppliers, with its strongest direct coverage aimed at the US West Coast. Nhava Sheva (INNSA) is Jawaharlal Nehru Port, across the harbor from Mumbai. Buyers still say JNPT. The authority is now JNPA. A quote that says Mumbai, with no terminal name, is not a booking. The code on the bill of lading should read INNSA if the box actually loads at Nhava Sheva.

Both ports can take your cargo. They do not take it on the same day, on the same ship, or at the same yard cost. indianxporter.com draws a useful split: Gujarat, Punjab, and Haryana cargo often fits Mundra, while Maharashtra and much of central India fits Nhava Sheva. North India is the overlap. Delhi, Haryana, Punjab, western Uttar Pradesh, and Rajasthan can feed either gateway. The choice is a calculation, not a habit your forwarder inherited from the last file.

Closer on the map is not faster on the water

Straight-line distance favors Mundra for every northern cluster mapped by sourcingfrom.com. The gap runs from about 87 km at Agra to about 337 km at Srinagar. A few working examples from that same map:

These are straight-line figures. Road and rail runs are longer. The direction of the gap still holds. A truck from a Punjab or Haryana mill usually has fewer kilometers if it heads to Mundra.

That inland saving only helps if the ship does not give the days back. A port that is a day closer by road is a poor choice if the sailing from it is two weeks slower. We see this most often in wholesale supply programs priced as factory ex-works plus a generic four weeks to the US. The sea number was copied from a different string, and the haul was never priced.

Rail, ICDs, and what the freight corridor actually moves

Most North India export cargo does not drive to the quay on day one. It stages at an inland container depot, and that depot has its own dwell.

ICD Tughlakabad in Delhi serves Punjab, Haryana, and Uttar Pradesh and can feed both ports. ngpillai.com puts the rail feeder from ICD Tughlakabad to JNPT at about 3 to 4 days, with daily rail. ICD Patparganj is the other Delhi node often used for electronics and higher-value goods moving toward Nhava Sheva. ICD Sabarmati, near Ahmedabad, is the usual inland feeder into Mundra for Gujarat cargo, and it also pulls some Rajasthan shipments that are already on the western side of the map.

The Western Dedicated Freight Corridor is often talked about as if it already runs into Nhava Sheva. It does not. The final section, Vaitarna to JNPT, is still incomplete, so the dedicated corridor does not yet fully reach Nhava Sheva port. Rail that does arrive at the port is still largely on the existing railway network, with ordinary path constraints and rake cutoffs. sourcingfrom.com notes that only about 11.7 percent of JNPA containers arrived by rail in August 2026. The track headlines are ahead of the volumes. If a forwarder says the corridor erases road time, ask what share of their last month of North India boxes actually moved by rail, which line those boxes used, and what the rake cutoff was. A future connection is not a booking.

Road into Mundra can still win on a short production window, especially when the factory is in Punjab, Haryana, or northern Rajasthan and the sailing you want is already calling Mundra. Rail into Nhava Sheva can win when the vessel, not the kilometers, is the constraint, and only when that rail move is a real slot, not a corridor claim. We price both legs before we lock the purchase order. A cheaper ocean rate that needs an extra ICD dwell and a missed cutoff is not a saving. It is a different shipment.

Dwell time is the part of the lead time nobody quotes

Dwell is the time a container sits at the port, or at a container freight station, before it loads or after it discharges. It is not steaming time. It is waiting, and it is where congestion shows up on your calendar.

A comparison published by container-news.com puts Nhava Sheva export dwell at 4.0 days, with import dwell at 2.5 days and transshipment dwell at 2.8 days. The same reading has Mundra ahead on dwell in every category they compared, which fits the port's reputation for yard flow and infrastructure. Four export days at Nhava Sheva is a planning number, not a scandal. What hurts you is gating in after the cutoff and then sitting those four days plus a full week for the next ship.

Older public studies show the same shape in hours rather than days. A December 2018 FIEO timeline study filed through jnport.gov.in measured container timelines at Jawaharlal Nehru Port Trust, Chennai, and APSEZ Mundra. CFS and ICD time often outweighed the hours spent on the quay. A June 2018 companion note, also on jnport.gov.in, shows dwell moving by hours from one month to the next. Treat any single dwell figure as a snapshot. Use it to build a buffer. Do not print it on a customer promise.

Ask for four lines, not one transit number: planned gate-in, container yard (CY) cutoff, export dwell assumption, and estimated time of departure. Uninspected production runs make this worse. A failed quality check on the morning of cutoff turns a normal dwell into a wait for the next weekly sailing. That is the delay we refuse to discover at the port gate.

Ocean schedules disagree, and that disagreement is the point

Published transit times for the same port pair can differ by a week or more. That is not sloppy rounding. It is direct service versus a relay, a weekly call versus three calls a week, and one carrier's string versus another's. If you want a date you can give a retailer, you have to name the string.

One carrier's public schedule, with departures from 24 September 2026, was read by sourcingfrom.com as median port-to-port days:

Read that table as one string on one date, not as the market. Other published ranges point the other way on some of the same lanes, and a buyer who treats either set as law will miss ships.

platton.ai puts India to USA ocean freight in a broad band of about 22 to 34 days port to port, then splits the pairs differently. Mundra to Los Angeles or Long Beach is listed at 22 to 28 days. Mundra to New York or New Jersey is 25 to 30. Nhava Sheva to New York or New Jersey is 22 to 26. Nhava Sheva to Los Angeles or Long Beach is 24 to 30. Nhava Sheva to Norfolk or Savannah is 24 to 28. On that reading, Nhava Sheva is the quicker US East Coast gateway, and Mundra looks stronger into Southern California. The September 2026 single-carrier median said the opposite on New York, and it had both ports transshipping into Los Angeles at 45 and 49 days. A quote of 22 days Mundra to Los Angeles is a different product from a relay at 49 days. Ask which one you are buying.

The Gulf split is just as sharp, which matters if you ship to the UAE. ngpillai.com lists JNPT to Jebel Ali as a direct service in 10 to 14 days for a full container, with daily sailings, and Mundra to Jebel Ali as direct in 8 to 12 days, three times a week. indianxporter.com is in a similar band: Dubai or Jebel Ali around 9 to 11 days in their lane list, with Middle East transit described as about 10 days via Nhava Sheva and slightly faster, about 8 days, via Mundra. The September 2026 carrier median, at 26 days from Mundra and 11 from Nhava Sheva, is not describing those direct strings. It is describing a slower booking, very likely a transshipment. Geography did not change between the sources. The service did.

Europe leans toward Nhava Sheva on more than one published reading. The single-carrier median was 33 days to Rotterdam from Nhava Sheva against 38 from Mundra, and 41 against 46 into London Gateway. ngpillai.com shows JNPT to Hamburg or Rotterdam as a direct service in 20 to 26 days for a full container, twice a week. indianxporter.com lists Rotterdam at 22 to 26 days and Felixstowe at 24 to 28 days in the same set of working ranges, with New York at 27 to 32 and Singapore at 18 to 22. If your buyer is in the UK or the Netherlands, do not give away a faster Europe string only because the truck to Mundra is shorter.

Australia and New Zealand need a port-level answer, not a country answer. In that September reading, Fremantle favored Mundra. Sydney and Melbourne were close, with Nhava Sheva ahead. Auckland was a wide gap for Nhava Sheva only because of a Port Klang relay, 30 days against 79. The same source flagged Pipavav as the slowest Indian gateway they read for Australia. If a rate sheet offers Pipavav as a cheap third option on an Australia order, ask for the relay ports before you treat the freight as a win.

Carriers publish the detail you actually need, and those files go stale. oocl.com has posted an IEX outbound schedule from Nhava Sheva toward the US East Coast, with named vessels, gate cutoffs, and arrival dates. Use that kind of file as the method, not as a permanent calendar: vessel name, voyage, cutoff, transshipment port if any, and the arrival port written out. US East Coast is not an arrival port. Neither is the Middle East.

FCL, LCL, and the extra days left off the slide

Less-than-container-load cargo waits for consolidation at origin and for deconsolidation at destination. On the ngpillai.com table, JNPT to Jebel Ali moves from 10 to 14 days on a full container to 14 to 18 days on LCL. Mundra to Jebel Ali moves from 8 to 12 to 12 to 16. JNPT to New York or Baltimore moves from 24 to 32 on FCL to 28 to 35 on LCL. JNPT to Hamburg or Rotterdam moves from 20 to 26 to 25 to 30.

LCL is often the right first move when you are testing private label manufacturing and you do not yet know the repeat rate. Copy the FCL transit into the launch calendar and you will spend the first season explaining a delay that was already on the rate sheet. Tell the retailer the LCL number, including origin CFS time. When the repeat order is real, check FCL space again. Do not assume the first routing still wins.

Frequency can beat raw steaming time. A direct Mundra to Jebel Ali service three times a week can still lose to a daily JNPT sailing if your cargo misses the only cutoff that fits production. That is why we will not quote a country-to-country lead time before the ready date and the mode are known. A confident average is how misleading lead time promises get into a buyer's plan.

A lower ocean rate is not a lower landed cost

indianxporter.com reports Mundra ocean freight as typically 5 to 8 percent lower than Nhava Sheva. Check that gap on your lane. It is often real. It is also small next to a missed week, a reefer plug shortage, or a haulage bill from Delhi to the wrong coast.

Reefer cargo is the clearest commodity split in that comparison. Mundra is the preferred load port for reefer exports. Nhava Sheva plug capacity tightens in peak season. If you are moving agro goods that must stay cold, the ports are not substitutes just because both can issue a bill of lading.

Documentation-heavy cargo pulls the other way. Pharma, specialty chemicals, and precision parts often benefit from the denser trade finance and forwarder market around Mumbai. A letter of credit that needs a same-day document set is a poor place to chase a small ocean discount and then lose two days moving papers from Kutch to a bank desk in Mumbai. For most textile, home, leather, and kitchenware programs, the banking load is lighter. The sailing and the haulage should decide.

Name the port in the purchase order. sourcingfrom.com puts the rule cleanly: write FOB Mundra, or FOB Nhava Sheva, not FOB India. If the handover is at the inland depot, say that too. FCA ICD Tughlakabad is a different risk split from FOB Mundra. Vague incoterms are one of the quieter ways middleman price inflation hides. You cannot see which leg was marked up if the leg was never named.

Match the gateway to the goods, not to last year's habit

North India is not one commodity. A Panipat rug mill, a Ludhiana knit unit, a Jaipur block-print workshop, and a Noida leather line can share a region and still need different routings. Put the port choice in the supply chain India file before the goods are packed. The failure sits in the gap between those decisions, not in the brochure.

For textiles, start with the destination port. A Europe buyer taking cloth from the northern yarn-to-finished chain may still be better on a Nhava Sheva direct to Rotterdam, even after a longer rail haul. A US West Coast buyer of the same cloth may be better on a Mundra string if that string is actually direct. Read top textile products exported from India and the textile value chain in the same meeting as the port choice, not after the goods are packed.

Leather and home goods have the same trap in a different order. A safe leather buy is a factory question first, which we cover in how to source leather products safely from India, and a routing question second. Home decor and kitchenware moving to US and UK retailers, the lines in why Indian home decor products are rising in demand and kitchenware in high demand, fail more often on a missed cutoff than on the design. Hospitality buyers have a room opening date. That date does not care that the factory finished early if the vessel was weekly and the box missed it.

Agro is stricter. UAE and Saudi programs need the Gulf string you actually booked, plus the papers. Use how to export agro products to the UAE and Saudi Arabia beside the port choice, and check EU agro certification before a Rotterdam transit time becomes the reason you book. Cold chain plus a 4-day export dwell is a quality issue, not only a freight issue. The value case in why Indian agro products offer better value still depends on the goods arriving in spec.

If you are still choosing the market, pair this routing note with top export-friendly countries for Indian products and the fastest growing export markets. A fast market on a slow relay is not fast for your cash cycle. US demand in Indian products in the American market only pays off if the East Coast or West Coast gateway matches the warehouse you use.

How we put the routing inside the sourcing file

Netyex is a buyer-side team on the ground in India. You are not buying a list of factories, and you should not be working from unverified supplier directories. You are buying oversight: supplier verification, in-line and final quality control, custom product development when you need it, and export coordination through to the vessel. The port is not a footnote we add after the goods exist.

The sequence we run is short, and we keep it visible.

1. Confirm the factory and the cluster. Ludhiana is not Jaipur, and we do not pretend the haul is the same.
2. Inspect before anyone calls the cargo ready. An uninspected run that fails at the port is the most expensive dwell you can buy.
3. Pick the gateway from your destination port, the direct or relay status, reefer need, and the inland cost. Not from a default saved in someone's email.
4. Write the port and the incoterm into the order. FOB Mundra, FOB Nhava Sheva, or FCA at a named ICD.
5. Book against a named sailing, with cutoff dates that sit after quality control, not before it.
6. Price the full path: ocean freight, haulage, ICD or CFS, and a dwell buffer. Then compare that number with the selling price using how to price your products for international markets.

This is also how we stay clear of the failures that cost importers real money: unverified supplier directories, middleman markups hiding inside FOB India, and lead times copied from a different string. How Netyex ensures authenticity and how to ensure compliance when buying Indian products sit upstream of the port. A clean box that cannot clear is still a late box. Secured trading keeps the commercial side as explicit as the routing side, without a layer of markup you cannot see.

A typical export calendar, as sketched by satvaexport.com, already includes production of roughly 5 to 15 days and quality testing of 2 to 3 days before documentation and the vessel window. Sea transit comes after that. Destination clearance often takes another 2 to 5 days. If your plan starts with a sea transit of three weeks, you have skipped the part a sourcing partner can actually control.

Browse categories in the product directory if you are still scoping what to make. For a spec that does not exist off the shelf, start with custom product sourcing. Put the destination port in that brief. Do not leave it for a panic email the week of sailing.

A checklist before you confirm the order

• Origin city and ICD, not a vague North India label.
• Destination port, not only the country. New York is not Savannah. Jebel Ali is not the whole Gulf.
• Direct or transshipment, written on the quote, with any relay port named.
• FCL or LCL, with the LCL days shown on their own line.
• Export dwell assumption. Use about 4 days as a Nhava Sheva planning figure from recent reporting, and do not assume Mundra is zero.
• Rail or road. A freight-corridor claim is a brochure until it is a booking. The Vaitarna to JNPT section is still incomplete, and the August 2026 rail share at JNPA was about 11.7 percent.
• Reefer plugs if the goods need cold.
• CY cutoff and documentation cutoff, both dated, and both after quality control.
• Vessel name and voyage, not a country average.
• A buffer you can explain if the weekly ship is missed.

Close the file before you promise a date

Mundra and Nhava Sheva can both carry North India cargo. They will not carry it on the same day, on the same ship, or at the same yard cost. Distance favors Mundra for most northern clusters. A real Europe string, some Gulf bookings, and a direct US East Coast call can still favor Nhava Sheva. Australia needs a port name. Reefer cargo is not interchangeable just because both gates can print a bill of lading.

Plan the gateway with the same care, starting at the factory cluster, through inspection, and on to a named cutoff. Stop only when the quote shows the string, the mode, and the dwell you are actually buying. That is how the date you give a buyer stays a date you can ship.

FAQ

Is Mundra always the faster gateway for North India?

No. Road and rail distance often favor Mundra from Punjab, Haryana, Delhi, and Rajasthan. The ship can give those days back. Compare haulage, export dwell, direct or relay status, and the cutoff against your real ready date. A nearer port with a slower string is a longer order.

Does the Western Dedicated Freight Corridor reach Nhava Sheva?

Not yet as a finished link into the port. The final Vaitarna to JNPT section remains incomplete, so the corridor does not fully reach Nhava Sheva. Ask which railway line the box will actually use, and what the rake cutoff is. Do not accept a corridor headline in place of a rail booking.

Why do two quotes from the same Indian port show different transit times?

They are usually different products. One may be direct and weekly. The other may relay through a third port, or it may be LCL with extra CFS time. A 22 day Mundra to Los Angeles figure is not the same booking as a 49 day transshipment. Make the forwarder name the vessel, the voyage, and any relay port.

Should a first private label order move as LCL?

Often, yes, if you do not yet know the repeat rate. Use the LCL transit on the rate sheet, including origin consolidation, not the FCL number. When the reorder is real, price FCL again. The first routing does not automatically win the second.

What should the purchase order say about the port?

Name the gateway and the incoterm. Write FOB Mundra, FOB Nhava Sheva, or FCA at a named ICD such as Tughlakabad. FOB India hides the leg. Hidden legs are where middleman price inflation sits, and they are also how misleading lead time promises survive a first read of the quote.

Where does quality control sit relative to the cutoff?

Before it. Supplier verification and an in-line or final inspection have to finish with enough time to gate in before CY cutoff. A fail on cutoff morning is not a small delay. On a weekly string it is often a full extra week, plus dwell. We will not call cargo ready in order to protect a sailing that the goods have not earned.

Ask us to map the gateway before you lock the order

Send the origin city, the ICD if you already have one, the destination port, and the date the factory can truly be ready. We will tell you which of Mundra or Nhava Sheva fits, what dwell buffer to carry, and whether the sailing in your quote is direct. Start with Contact us. If the commercial terms need to be as plain as the routing, read secured trading services before you compare numbers.