Maersk and Hapag-Lloyd restart FM1 Asia-Middle East loop with Oct 17 Qingdao sailing

The Analysis

Maersk and Hapag-Lloyd are restarting FM1, one of the Gemini network's Asia to Middle East loops. The published rotation is Qingdao, Ningbo, Tanjung Pelepas, Khor Fakkan and Singapore. The first sailing is the Maersk Athabasca, voyage 642W, departing Qingdao on 17 October and arriving Khor Fakkan on 16 November. Thirty days, port to port.

Maersk's language around the restart is careful in a way that matters. Security precautions in the Middle East continue. Existing booking restrictions and cargo acceptance rules remain in effect. Landside services cover the upper Gulf. Both carriers say further adjustments will depend on the local situation. That is a restart announcement written with one foot still on the brake.

Four words in that statement carry more weight than the rest of the paragraph: remain in effect. A loop can restart while your cargo still cannot be booked. Before anyone treats this as good news, we take the rest of it apart: the thirty days, the five ports, and what the rotation actually restores for somebody with cargo to move.

Thirty days is where I start, and this is a number with something missing from it. Qingdao to Ningbo, Ningbo to Tanjung Pelepas, Tanjung Pelepas to Khor Fakkan: by chart that is roughly 6,300 to 6,800 nautical miles, and I am estimating from the map, not quoting anyone. At sixteen knots, about sixteen and a half days of steaming. Add two working calls and you land near eighteen to twenty days. The announcement says thirty. That leaves roughly ten days in the schedule which are not steaming time at anything like normal speed.

Two readings, and they point the same way. Either the ship runs at ten or eleven knots, which is slow steaming on a lane where the bunker maths rarely demands it, or those ten days are buffer the carrier wrote into the proforma before publishing it. A carrier that has just come through a period of schedule damage and is re-entering a sensitive trade will do exactly that: pad the schedule so the published number is one it can actually hit. Read thirty days as the optimistic end of a range rather than a promise, and read it as an admission that nobody intends to be held to a twenty-day run on this lane right now.

The port list is the second thing to take apart, and it is the part the headline flattens into Asia to Middle East. Khor Fakkan sits on the Gulf of Oman side of the United Arab Emirates, outside the Strait of Hormuz. Jebel Ali, Dammam, Kuwait and the Iraqi corridors are all inside it. So this loop does not deliver into the Gulf. It delivers to the Gulf's front door, and Maersk's own statement confirms the shape by telling you that landside services cover the upper Gulf upstream. Sixteen November is a date at Khor Fakkan. It is not a date at your consignee's gate, and every hour after that is a road leg or a feeder leg that this announcement does not cover.

Layered on top of that is the line most coverage will skip: booking restrictions and cargo acceptance rules remain in effect. A rotation is not a service. If your commodity sits inside those rules, this press release changes nothing at all for you, and the only way to find out is to attempt a booking and read carefully what comes back. I have watched shippers plan around a resumed service for two weeks before discovering their cargo was never bookable in the first place, which is a particularly avoidable kind of waste.

Reading the bones of a loop, meaning which hub it feeds and which one it bypasses, is Tomás Ferreira's instinct, and on this rotation the interesting fact is the order of the calls. Khor Fakkan comes before Singapore. Gulf cargo is worked on the outbound leg and never touches the Singapore hub, while Southeast Asian transshipment volume is handled on the way back. That is deliberate design: keep the exposed leg short and keep redistribution volume off it. It also locates your risk. If the Gulf call is pulled again, your box is not sitting in Singapore; it is sitting at Tanjung Pelepas on the way out, and the question of who pays for that week is the one you should settle before you ship.

Five ports, and who is missing tells you who the loop is for. Qingdao and Ningbo are North and East China load centres, so the design is aimed at Chinese export volume rather than at Southeast Asian transshipment. Tanjung Pelepas and Singapore are the two hubs that redistribute to the rest of the region. What is absent matters more: there is no call anywhere inside the Gulf. A shipper in Shanghai is not covered directly and will move by feeder to Ningbo or Qingdao, and that feeder leg, with its own cut-off and its own delay distribution, sits in front of the thirty days, not inside it. Anyone quoting a door-to-door date off this announcement needs to add the load-port feeder before adding the ocean leg.

Why now, and why like this? Neither carrier is claiming the security picture has improved; both say further adjustments depend on the local situation. That phrasing tells you what kind of decision this was. Restarting one loop on a hub-and-spoke design is a low-commitment move: you add a string that can be withdrawn without dismantling the network, you keep the sensitive call outside the Strait, and you hand the last leg to trucks you control. It restores capability without restoring exposure. That is a sensible piece of network design, and it is also a warning about how reversible it is. Note what the two carriers did not announce: no call inside the Gulf, no date for a second loop, no commitment to a weekly fixed-day service beyond the first string. A restart published with this many qualifiers is a probe, and a probe can be withdrawn in one advisory notice. Price that reversibility into your planning rather than treating the announcement as a floor under your supply chain.

When does any of this reach your warehouse? The first discharged box under this loop lands at Khor Fakkan on 16 November. Add the onward movement. Khor Fakkan to Dubai is roughly 120 kilometres by road, call it a day. To Dammam it is a cross-border run of about 1,500 kilometres plus Saudi clearance; call it three to five days. Both are my estimates from a map, not figures from the announcement. Earliest realistic gate dates are therefore around 17 November for Dubai and 20 to 21 November for Dammam. Anything you need in the upper Gulf before the end of November has roughly nine days of slack on the Dubai side and almost none on the Dammam side. That is the entire decision, and it is a narrow one.

Let us put a number on the pipeline, because thirty days instead of twenty is working capital sitting on the water. Assume forty FEU a month from Qingdao to the upper Gulf, assume fifty thousand dollars of goods per FEU; both are assumptions, substitute your own. Thirty days of ocean plus five days landside is thirty-five days in transit, so the pipeline carries about forty-seven boxes at any moment, roughly two point three million dollars of inventory afloat. Against a twenty-day run, the extra ten days tie up roughly thirteen boxes, about six hundred and sixty thousand dollars. At eight percent annual carrying cost that is around forty-four hundred dollars a month. Not fatal, and worth knowing, because it is the one cost of this routing you can forecast exactly.

That hub question is worth pushing one step further, because it changes what you should ask your forwarder to do. If your box is transshipped at Tanjung Pelepas, the connection is a second vessel with its own schedule and its own reliability, and the thirty days already assumes it works. Ask for the connecting vessel name and voyage, not just the mother vessel, and ask what happens if the connection is missed: on a monthly loop, a missed connection is not a day, it is a full rotation, which is thirty days. That is the difference between a delay and a disaster, and it is buried in the transshipment leg nobody puts on the quotation.

Whether that premium is worth paying depends entirely on what the alternative is, and this is where people get the comparison wrong. If the alternative is a transshipment through another hub with a longer inland leg, thirty days to Khor Fakkan plus a day of road may still beat it door to door. If the alternative is waiting for a direct call inside the Gulf that does not currently exist, then routing is not the question at all, timing is. Compare door to door and never port to port, because this loop is built precisely so that the port-to-port number flatters the door-to-door reality by several days.

There is a quoting problem buried in all this that bites later rather than sooner. Your sales team will read Asia to Middle East service restarts and start committing dates, and the dates they commit will be port-to-port dates, because that is the only number in the announcement. What your customer hears is a gate date. On this loop the two are separated by an entire road leg through a restricted corridor, so the gap between what you promised and what you can deliver is not a few days of slippage, it is a different leg of the journey. Write the committed date as a gate date, write the discharge port next to it, and make sure whoever signs the contract understands that Khor Fakkan is not the destination.

There is a second-order effect on order policy that most people miss. At thirty-five days door to door, a monthly shipment cycle means your reorder point sits five weeks out, and every error in demand forecasting is amplified by the length of the pipeline. Splitting the same forty boxes into two shipments three weeks apart does not change the transit time, but it cuts the average pipeline inventory and, more importantly, it means one bad sailing damages half the month instead of all of it. On a lane this uncertain, frequency is cheaper insurance than buffer.

What would make me wrong? Mostly the security variable, and both carriers have said as much. With a thirty-day transit, a booking placed this week lands in a security environment four weeks from now, and no carrier can underwrite that. If the situation tightens mid-voyage, the exposure is quite specific: your box is either still at Tanjung Pelepas or already discharged at Khor Fakkan, and in both cases it is the onward leg that stops, not the ocean leg. The risk is not that the container is lost at sea. It is that the container arrives and then does not move, which is a far duller and considerably more expensive outcome, because storage at a discharge port with restricted onward capacity accrues whether or not anybody is at fault.

Ask yourself what you would do with forty boxes sitting at Khor Fakkan with the road leg suspended: you cannot reroute them easily, you cannot sell them locally, and you cannot leave them there for long. If you do not have an answer to that question, you are not ready to book this loop, regardless of what the rate looks like.

The other reversal is commercial. If the security picture improves, capacity returns to this trade quickly and rates soften, and anybody who signed a twelve-month commitment on the strength of the first sailing will spend the rest of the year paying for optionality they never used. Lock the sailing, not the year. There is no version of this trade in October where a long commitment is the cheap choice.

A word about first sailings, since 642W is one. The first couple of rotations on a restarted loop have the worst schedule record on the entire network: new port windows, new feeder connections, new inland slots, and a proforma nobody has run once. If ten of the thirty days are buffer, a good part of that buffer will be eaten by the first sailing alone. Treat 16 November as the earliest possible arrival rather than the expected one, and if your project schedule cannot absorb another week, either ship earlier on another routing or split the volume across this sailing and the next.

Before you book, get three answers in writing. Whether your commodity is bookable at all under the rules that remain in effect. What the onward leg from Khor Fakkan actually is: feeder or road, which operator, and whose contract it moves under. And what happens if the onward leg is suspended after discharge, including who carries the storage from that moment. That third answer is the one that decides whether you have bought transport or bought an option on transport, and it is the answer carriers are least keen to put in an email.

Then the commercial mechanics, which are unusual on this lane. When the last leg is landside, the through rate matters more than the ocean rate, because the ocean rate is the part you can benchmark and the landside is the part you cannot. Ask for the through rate to the final inland point broken out leg by leg, and check free time at Khor Fakkan specifically. A discharge port outside the Gulf, feeding a restricted corridor by road, is exactly the place boxes sit, and the free time granted for a normal turn will not cover a week of waiting. Ask what war risk and any security-related surcharges are being applied to the Gulf leg and on what basis they are recalculated, because those are the line items that move without notice.

Then check how the through rate is quoted: if the ocean leg and the landside leg are on separate invoices with separate validity, you do not have a through rate at all, you have two exposures and the second one is the one that can be repriced while your box is at sea. Ask for a single validity date covering both legs, and if the carrier will not give you one, assume the landside portion can move and put a contingency number in your cost sheet.

My threshold here is about dates rather than rates. If the cargo must be in the upper Gulf before the end of November, book 642W this week and book the landside capacity in the same conversation, because the next sailing in the string runs about a week behind it and lands around 28 November at Khor Fakkan, which misses the window entirely. If the deadline is January or later, do not commit on the strength of one announcement; wait for the second and third sailings and their actual arrivals, then decide on data rather than on a press release. And whichever way you go, compare door to door and put the carrying cost of the extra ten days into the comparison.

One more number to carry into that conversation: the cost of being a week late on this corridor is usually not the freight, it is the project penalty or the idle site at the other end, and that number is often ten times the freight. If that is true for you, the decision stops being a freight decision and becomes a scheduling one, and the right question is not which carrier is cheapest but which sailing leaves you the most slack against the date you cannot move.

A restart announcement tells you a vessel will sail. It does not tell you a service exists. The four least glamorous words in this document are the ones that should shape your plan: restrictions and cargo acceptance rules remain in effect. Everything past Khor Fakkan is still a road trip through somebody else's risk map, and you are buying that road trip whether or not anybody says so.

Book the date you can defend in front of your customer, not the date on the press release. And when your deadline sits inside thirty days of ocean plus five days of road, that is the moment to lock the space and the truck together, not the moment the freight quote starts looking friendly. The arithmetic is short: sailing date plus thirty, plus the road leg, minus the earliest date your customer can actually move. Under ten days of slack and you are not buying freight, you are buying a coin toss, in which case renegotiate the date instead of the rate.

↑ Back to the key points

— By Vivian Zhao