Congestion on the Trans-China and Trans-Siberian railways is pushing Russia-bound cargo onto sea. Busan shipped 33,000+ teu to Vladivostok in August, 8,000 teu export ex-transhipment; September exports are put at 8,800 teu, up 10% on August. Rollovers are routine and Busan-Vladivostok rates average $1,700 per teu, against $1,500 in August after a $300 jump from July. The root cause is in China: typhoon backlogs pushed shippers onto rail, jamming Lianyungang, Qingdao and Tianjin.
Supply Chain Action Points
If you ship into Russia and you have been riding the China-Europe / Trans-Siberian rail corridor, the first thing to understand is that this is not a normal seasonal hiccup. The congestion that started with typhoon backlogs in China has jammed the rail gateways at Lianyungang, Qingdao and Tianjin, and that jam is now pushing cargo onto the sea. For shippers who move Russia-bound boxes, the practical question is no longer "should I book rail or sea" but "how do I keep my cargo moving when the cheapest lane is clogged and the fallback lane is filling up fast." This note lays out what the backlog means, why Busan-Vladivostok has become the release valve, how far the rate has climbed, and what you should actually do in the next 30 days.
**What the rail backlog actually means for your Russia-bound cargo**
The number everyone is quoting right now is the Busan-Vladivostok ocean rate at $1,700 per teu. It is a striking number and it is worth talking about. But before you do anything with that rate, you should understand that it is a symptom, not the disease. The disease, to borrow the Loadstar's phrasing, sits on land in China. Typhoon-season backlogs across the coastal and inland networks pushed a wave of shippers off the water and onto rail. Those shippers were not irrational. They were trying to escape port delays and schedule slips on the ocean side, and rail looked like the faster, more controllable option. The problem is that they all made that calculation at the same time, and they poured into the Trans-China and Trans-Siberian corridors at exactly the wrong moment.
The result is rail waits that have topped one week at the Chinese gateways — Lianyungang, Qingdao and Tianjin. And those waits should worry you more than the ocean freight number, for a simple reason. A week of rail dwell at the gateway is a week your inventory sits still before it ever reaches the Russian border. It is dead time. No value is created, no customer is served, and the carrying cost keeps running. When you hear "$1,700 per teu on the sea," translate that in your head to "and also a week of rail queue if you stay on land." The two numbers are two faces of the same congestion.
For an importer or exporter who moves goods into Russia on a regular basis, the practical reading is uncomfortable but clear. The land bridge you may have come to rely on — the rail corridor that let you promise customers a predictable 18-to-22-day transit — is no longer that product. When rail waits exceed a week at the Chinese end, your real transit time stops being the published rail schedule and starts being whatever the queue lets through. That means every planning assumption you built on top of the old schedule — lead times, safety stock levels, customer delivery promises, even your working-capital cycle — is resting on a number that no longer holds.
So the first action is not to chase a cheaper rate. It is to re-baseline your transit-time assumptions for Russia-bound cargo and write the rail delay into your plan explicitly, as a fixed cost of time rather than an unfortunate exception. A shipper who plans for 22 days and gets 30 is in trouble; a shipper who plans for 30 and gets 30 is fine. The delay is real either way. The only variable is whether you planned for it.
**Why sea via Busan became the release valve**
When a land corridor jams, the cargo that was supposed to flow through it has to go somewhere. In this case the release valve has been the ocean route from Busan to Vladivostok and the other Russian Far East ports. This is not a brand-new lane that appeared overnight. It has existed for years and served niche volumes. What is new is the scale, and scale is the whole story.
Busan moved more than 33,000 teu to Vladivostok and the surrounding Russian Far East ports in August alone. Within that total, roughly 8,000 teu was export cargo counted without transhipment — that is, boxes that started their journey as genuine export loads rather than repositioning or transhipment filler. Then September export volumes are estimated at 8,800 teu, up about 10% on August. Hold that 10% month-on-month figure in your mind, because it is the single clearest signal in this whole situation. It tells you that shippers are migrating off rail and onto this sea lane faster than the lane can comfortably absorb them. A 10% jump in a single month on a lane that was already handling record volume is not organic growth. It is a reroute in motion.
The reason Busan functions as the valve is geography and connectivity, not luck. Busan is one of the most connected transhipment hubs on the planet, and Vladivostok is the natural Russian Far East gateway for cargo heading to Moscow and the western regions via the eastern land bridge. For cargo that is already moving through Northeast Asia — which describes a large share of China-origin and Asia-origin Russia-bound trade — switching from a Chinese rail gateway to a Busan sailing is often a smaller detour than it sounds. More importantly, it sidesteps the Lianyungang-Qingdao-Tianjin rail queue entirely. You trade one queue for another, but the sea queue has, until recently, been the shorter one.
The catch, and it is the catch that should shape your strategy, is that as more cargo crowds into the Busan-Vladivostok sailings, the lane itself begins to show the same strain the rail corridor showed first. That is exactly what the rollover problem is telling us. A release valve only works while it has spare capacity. Once it fills, it becomes the bottleneck, and you are back where you started with a different label.
**The rate trajectory: $1,200 to $1,500 to $1,700, and what it implies**
Look at the rate path and the mechanism is obvious. July was around $1,200 per teu, more or less. August jumped to $1,500 — that is a $300 increase in a single month. September is now averaging $1,700. Put together, that is roughly a 42% increase from July to September compressed into about eight weeks. For an importer or exporter who budgets freight as a predictable line item, a lane that reprices by 40% in two months is not a fixed cost. It is a volatile spot exposure, and you have to manage it the way you would manage any volatile input.
The crucial point for your forecasting is that this trajectory is demand-driven, not cost-driven. Bunker prices, surcharges and currency all move rates around, but the dominant driver here is the volume pouring off rail and onto the Busan sailings. That distinction matters enormously for how you plan, because demand-driven spikes behave differently from cost-driven ones. A cost-driven increase tends to be sticky — when bunker goes up, it stays up. A demand-driven spike tends to climb until one of two things breaks the fever: either the rail corridor clears and cargo flows back to land, or the sea lane saturates and rates plateau at a new, higher equilibrium that reflects the lane's true scarcity.
Given that the root cause is typhoon backlogs, which are seasonal rather than structural, the realistic expectation is that pressure eases as the typhoon season passes. But "eases" is not the same as "reverses." Do not assume the rate snaps back to $1,200. Assume it finds a new plateau somewhere above where it started, and that the timing of any softening depends on weather and on how fast the Chinese gateways clear. Plan for the high rate to persist through the remainder of the congestion window, and treat any drop as a bonus you capture by being ready to switch, not as a baseline you count on.
**Rollover risk is the hidden tax you cannot see on the quote**
The Loadstar reports that rollovers are now routine on this lane. A rollover happens when your booked box does not sail on the vessel you booked it on. Instead it gets pushed to the next sailing, and sometimes the one after that, until space finally opens. For an importer or exporter, a rollover is in many ways worse than a high rate, because it is an unpredictable delay layered on top of the very rail delay you were trying to escape. You thought you had left the queue by going to sea, and instead you joined a different, less visible queue.
The practical implication is the one most shippers miss: a quoted ocean rate is no longer the full cost of the lane. The real cost includes the probability that your cargo waits an extra week or two at Busan before it sails. When you sit down to compare rail and sea, you have to compare not the published rates but the expected delivered time and the variance around it. A $1,700 sea rate with a meaningful rollover probability and a week of extra dwell is, in expected-time terms, frequently worse than a $1,500 rate on a lane that actually sails on schedule. This is why blind rate-shopping will burn you in this market. The cheap quote is not the cheap lane if it does not sail.
There is also a second-order effect worth naming. When rollovers are routine, forwarders and carriers start allocating space preferentially to their best customers and to the highest-paying bookings. If you are a small or occasional shipper, your box is more likely to be the one that rolls. That means relationship and booking discipline matter more now than they did when space was ample. A guaranteed slot costs more, but in a rollover environment it is often the difference between sailing this week and sailing in two weeks.
**How to route: rail vs sea vs transhipment, by situation**
There is no single correct answer here, and anyone who sells you one is oversimplifying a congestion problem that changes week to week. The right choice depends on where your cargo originates, how time-sensitive it is, how much buffer you carry, and which gateway is congested this particular week. Here is the practical framing we use.
Rail still makes sense if your cargo originates deep in China's interior and the rail gateway nearest you is not currently among the jammed trio, or if your shipment is genuinely not time-critical and you can absorb a week of dwell without breaking a customer promise. The one-week wait is bad, but it is at least a known bad with a visible queue. You can plan around a known delay far more easily than around a rollover you did not see coming.
Sea via Busan makes sense if your cargo is already in or near a coastal hub, if you can reach Busan economically through transhipment, and if you can book early enough to dodge rollovers. The geographic fit matters: if your goods are in southern or eastern China, the inland haul to a northern rail gateway may be longer and more expensive than a short positioning move to a transhipment feeder that connects to Busan.
Transhipment through Busan specifically makes sense because Busan's connectivity means you can consolidate volumes and find sailings even when direct options are tight. The hub-and-spoke model that makes Busan one of the world's top transhipment ports is exactly what gives you options when the direct lane is full. You may pay a small premium for the transhipment leg, but you buy access to capacity that a direct-only strategy cannot reach.
The mistake that will cost you is treating this as a permanent switch from rail to sea. This is a congestion-driven reroute, and reroutes unwind when the congestion does. The smart play is to keep both options live, split your volume deliberately, and shift the mix week by week based on what the gateways are actually doing rather than what they did last month. A shipper who puts 100% of Russia-bound volume on one lane is a shipper who will get stuck on that lane's worst day. A shipper who keeps a foot in both camps can always move to the one that is working.
**Contract versus spot: should you lock in now?**
When a lane is repricing this fast, the instinct is either to lock everything into a contract or to stay purely spot and chase the lowest weekly number. Both extremes are wrong. The case for a contract is that it caps your downside if the Busan rate keeps climbing past $1,700 and the rollover tax gets worse. The case against a contract is that if the typhoon-season congestion clears and rates fall back, you are stuck paying above-market. The pragmatic answer is a blended approach: put your committed, predictable volume under a short contract or a multi-week rate agreement that covers you through the congestion window, and keep a discretionary slice on spot so you can chase the market down once it turns. The key word is short. Do not sign a twelve-month agreement anchored to a congestion peak, because you will be paying peak rates long after the peak is gone.
**Inventory and working capital: you are now financing a longer trip**
When transit stretches from 22 days to 30, you are not just late, you are carrying more inventory in the pipe at any given moment. That is working capital you cannot deploy elsewhere. If you run lean and your Russia lane is a meaningful share of volume, the extra week of in-transit stock can tie up real cash. The move is to quantify it: take your average Russia-bound value in transit, multiply by the extra days of transit as a fraction of your cycle, and you have the cash the congestion is quietly borrowing from you. Once you see the number, you can decide whether to fund it with a small rate premium on the faster lane or with a longer payable on the slower one. The point is to make the trade explicit instead of letting it hide in your balance sheet.
**Talking to customers without losing the account**
The hardest part of a transit blowout is the phone call. Customers do not care about typhoons in China or rail queues in Lianyungang; they care that the goods are late. The shippers who keep their accounts are the ones who communicate the new expected date before the old promised date passes, and who offer a contingency — split the order, air the critical SKUs, whatever fits. Silence is what loses accounts. A dated, honest update with a plan beats a vague promise of "soon" every time. Build the customer communication into your 30-day playbook as a step, not an afterthought.
**A 30-day playbook you can actually execute**
If you are moving Russia-bound cargo right now, the window for action is this month, not next quarter. Here is a concrete sequence.
Start by re-baselining your transit expectations. Add at least 7 to 10 days to any rail-based plan and at least 5 to 7 days of rollover buffer to any Busan sea plan. Write these numbers into your customer promises so you are not the one eating the apology when the delay hits.
Next, open or reactivate a Busan sea option even if you have been a pure rail shipper for years. You do not need to use it this week. But you need it quoted, mapped and ready, because the day your rail gateway jams harder is not the day to start learning a new lane.
Then, split your upcoming volume across both lanes so that no single delay can stall your entire pipeline. Even a 70/30 split beats 100/0, because the 30% that sails keeps revenue moving while the 70% waits its turn.
After that, when you do book sea space, book at least two to three weeks ahead and confirm in writing that the booking is a guaranteed slot, not a soft allocation that can be rolled at the carrier's discretion. The guarantee is what you are paying for in a rollover environment.
Also, talk to your forwarder specifically about which Chinese rail gateway is least congested this week. Lianyungang, Qingdao and Tianjin are not congested identically or simultaneously, and a 200-kilometre repositioning to a clearer gateway can save you days.
And build a simple weekly monitor for the Busan-Vladivostok rate and the reported rollover frequency. You do not need a dashboard. A shared spreadsheet that someone updates every Friday is enough to let you see the turn before it arrives.
None of this is exotic or capital-intensive. The edge is simply that most shippers are still planning on last year's map, and you are planning on this week's reality. That gap is where the savings and the on-time deliveries live.
**Worked example: one teu, total landed cost including time**
Take a shipper moving a single teu of consumer goods valued at $40,000 from a Chinese coastal city to a Moscow-region distribution centre. Under the old rail assumption, freight might have been budgeted at around $1,200 per teu with a transit of roughly 18 to 22 days to the border. Today the picture is different on both lanes.
On rail, you add a week of gateway dwell, pushing real transit toward 25 to 30 days, and the rail rate itself has risen with the broader repricing, so your freight line is no longer $1,200. On the Busan sea option, the quote is $1,700 per teu, but you must also add the cost of inland positioning the box to Busan and a rollover buffer. If the box rolls once, delivered time slips by another week, and the carrying cost on $40,000 of inventory becomes a concrete number. At a typical monthly inventory finance rate, a week of delay on $40,000 runs about $150 to $300 in carrying cost — and that is before any lost sales if the goods were time-sensitive, which for seasonal consumer goods can be far larger.
Now compare. The apparent $500 saving of rail over sea can be erased by a single week of dwell plus the inventory carrying cost, before you even count the sales you miss by being late. Conversely, the $500 premium of sea over rail can be justified many times over if rail rolls you into a two-week gateway jam. The lesson is to compute total landed cost including time, not the freight line item in isolation. The lane that looks cheaper on the quote is often the more expensive one in the spreadsheet.
**What to monitor so you are not surprised again**
Watch four things, and check them weekly. One, the Busan-Vladivostok rate path. If it keeps climbing past $1,700, the sea lane is saturating and you should not assume it stays cheaper than rail. Two, the reported rollover frequency out of Busan. Once rollovers stop being routine and start being severe, the sea valve is closing and you need to be back on rail the moment it clears. Three, the congestion status at Lianyungang, Qingdao and Tianjin — those three ports are your early warning system for when rail might clear, because the moment they recover, cargo will flow back to land. Four, the typhoon season calendar. The root cause is seasonal, so the relief, when it comes, will come with the weather, not with any structural fix.
When the Chinese gateways finally clear, expect a reverse migration: cargo flows back to rail, the Busan rate softens, and the early movers capture the cheaper lane. Position yourself to switch back fast. The shippers who re-optimise earliest will be the ones who lock in the lower rate and the shorter transit, while everyone else is still reacting. In a congestion market, speed of re-optimisation is the only durable advantage.
- Re-baseline Russia-bound transit times now: add 7-10 days to every rail plan and 5-7 days of rollover buffer to every Busan sea plan, and write those numbers into customer promises.
- Keep both rail and Busan sea options live; split upcoming volume across both lanes so no single delay can stall your whole pipeline (even a 70/30 split beats 100/0).
- Book Busan sea space 2-3 weeks ahead and confirm a guaranteed slot in writing, not a soft allocation that a carrier can roll at its discretion.
- Ask your forwarder weekly which of Lianyungang, Qingdao and Tianjin is least congested, and reposition to the clearer gateway to save days.
- Build a simple weekly monitor for the Busan-Vladivostok rate and the reported rollover frequency so you see the turn before it arrives.
- Compute total landed cost including in-transit time and inventory carrying cost, not just the freight line item, before choosing rail or sea.