Two Far East–India Loops Launch June 21. Both Drop Colombo; One Drops Singapore.

From 21 June, a long-running Far East–India joint service breaks into two, and the change that matters most for planning isn’t who partners with whom — it’s the port calls quietly disappearing from the rotation. Both new loops drop Colombo. One drops Singapore too. If you have cargo moving on this lane, your transshipment assumptions just changed with about two weeks’ notice.

Here’s what’s actually happening, and the specific routing assumptions worth rechecking before the new strings go live.

What’s splitting

The joint Far East–Western India service operated by Gold Star Line, KMTC, Evergreen, and Emirates Shipping Line is separating into two independent products from 21 June, according to The Loadstar, citing Alphaliner.

Gold Star Line leaves the cooperation to partner with Global Feeder Shipping on a revised New India Express loop. The rotation runs Shanghai, Ningbo, Dachan Bay, Port Klang, Nhava Sheva, Hazira, Mundra, Port Klang, Haiphong, and back to Shanghai — five ships of 4,300–5,600 TEU on a six-week turn. The notable part: this loop removes Colombo and Singapore calls.

KMTC, Evergreen, and Emirates Shipping Line keep their cooperation, redeploying onto six larger vessels of 5,500–9,500 TEU. Their rotation covers Shanghai, Ningbo, Shekou, Port Klang, Nhava Sheva, Hazira, Mundra, Port Klang, and Shanghai. Two changes here: the South China call shifts from Dachan Bay to Shekou, and Colombo is dropped.

So across both loops, the consistent move is the removal of intermediate hub calls — Colombo from both, Singapore from the Gold Star/GFS string. Direct port-pair coverage between the named Chinese and Indian ports stays; what changes is what happens to cargo that was relying on those dropped calls for transshipment connections.

Why carriers are redrawing these loops now

This split isn’t happening in isolation. It’s part of a broader redrawing of Asian networks away from the Middle East, where capacity has pulled back sharply. Drewry’s Philip Damas told The Loadstar that capacity on North Asia–Middle East and South-east Asia–Middle East routes has collapsed 70.6% and 67% year on year. Carriers are redeploying that capacity onto growing East Asia, South-east Asia, and Indian subcontinent lanes — the Gold Star/GFS reshuffle is one piece of that pivot, and Cosco separately launched a new South-east Asia–India service the same week.

The demand side is pulling the same direction. Drewry’s Intra-Asia Container Index put the China–India lane up 49% in a fortnight, to $1,753 per 40ft as of 29 May. When a lane is both repricing upward and restructuring its port calls at the same time, the routing changes are easy to miss underneath the rate headline.

The assumptions worth rechecking

If you book or manage cargo on the Far East–India corridor, the dropped calls are the operational trigger. A few things change in practice:

Transshipment routing via Colombo or Singapore. Cargo that previously connected through those hubs on this service now either moves direct or has to find another transshipment path. If your routing assumed a Colombo or Singapore relay, confirm how the cargo actually moves after 21 June.
Transit times on affected port pairs. Removing calls can shorten transit on the direct pairs and lengthen it for anything that depended on the dropped connection. The loops still turn in six weeks, but the door-to-door picture for specific origin–destination pairs may shift.
The transshipment hubs themselves are congested. Damas flagged Singapore port utilization at critical levels, with pools of displaced containers forcing carriers to prioritize westbound traffic and slowing empty repositioning into South Asia. Cargo rerouted onto alternative transshipment paths is moving through hubs that are already strained — which is where dwell and delay tend to accumulate.
Empty-return and equipment timing. With Gold Star moving to a new partner and vessel sizes changing on both loops, empty-return windows and equipment availability assumptions tied to the old service string are worth reconfirming rather than carrying over.

When a service drops a transshipment call, the cargo most at risk is the cargo that was quietly relying on it — and that exposure is hard to see if you’re tracking by booking reference against a schedule that no longer matches the live rotation. See how teams keep container-level visibility on transshipment legs when carriers reshuffle their service strings.

The pattern behind the single event

This is one corridor, but the mechanism is general. Carrier cooperations form and dissolve constantly, and each reshuffle quietly rewrites port rotations, transshipment points, and vessel sizes. The China–South Africa network is reshaping the same week after Evergreen and PIL exit, with new services launching to fill the gap. The headline reads as carrier news; the operational consequence lands on whoever has standing bookings on the lane and assumed the rotation was stable.

The practical takeaway for the Far East–India lane is narrow and dated: the new strings go live 21 June, two calls are coming out of the rotation, and the cargo to check first is anything that was transshipping through Colombo or Singapore on the old joint service. The rate increase on this lane will get the attention. The dropped calls are the part that actually changes how your boxes move.

Service details reflect reporting by The Loadstar (citing Alphaliner) and Container News as of 4–7 June 2026, with the split effective 21 June 2026. Rotations, vessel deployments, and effective dates are set by the carriers and may be revised; confirm current schedules directly with your carrier before booking. Rate figures reflect Drewry’s Intra-Asia Container Index as of 29 May 2026 and move weekly.