How many STS cranes does a container berth need?

If you're sizing up a competitor's terminal from the outside, the crane count on the quay is the first number you reach for. But "how many STS cranes per berth" doesn't have one answer. It depends on berth length, vessel calling pattern, and how aggressively the terminal operator wants to turn ships. Here's how the ratio shakes out, and why counting gantries from a distance gets you closer to the truth than most people assume.

The working range, and why it moves

Most container berths built for mainline vessels run two to four ship-to-shore cranes. A berth sized for a 300-to-350-meter vessel typically carries three; push past 400 meters for ULCS calls and four is common, sometimes five if the terminal is chasing fast turnaround on megamax strings. Feeder-only berths can get by on one or two.

Crane outreach and the boom spacing a terminal operator is willing to accept drive the number more than berth length on paper. Cranes working the same vessel need enough lateral room that the trolleys don't collide and the gangs aren't tripping over each other's bays. Terminals that bought taller, longer-boom cranes for ultra-large vessels sometimes run fewer units per berth at wider spacing and still hit the same box count, because each crane is covering more of the vessel's beam.

Ownership structure matters too. A dedicated terminal serving one alliance tends to crane up harder, because idle berth time has a direct cost to one operator. A multi-user or landlord-model terminal splitting berths across several lines often runs a leaner crane-to-meter ratio and relies on berth scheduling instead of raw gantry count to keep vessels moving.

Reading crane density from outside the fence

Crane density, total STS units divided by total berth length, tells you more about a terminal's capital commitment than any single berth's ratio does, and it's the number worth tracking if you're building competitive intelligence rather than running the yard. A terminal running dense (say, a crane roughly every 90 to 100 meters of quay) has typically made a deliberate bet on throughput and is a live buyer for new gantries. One running sparse is either capacity-constrained by choice, mid-upgrade, or quietly losing calls to a denser neighbor down the coast.

None of this requires a site visit. Berth length is public from port authority documents or AIS-derived vessel traffic. Crane count and spacing are visible from above: a clear satellite or aerial pass at sub-meter resolution shows you the gantry rail line, how many booms sit on it, and roughly how tall and how far each one reaches. Attributing each crane to a manufacturer and turning that into a dataset you can track year over year across every terminal in a market is the harder part, and a different problem than spotting cranes on one image.

That's the gap Crane Fleet Mapping is built around: a terminal-by-terminal inventory of STS and yard cranes, with maker attribution where it's visible and a height/reach estimate from photogrammetry, refreshed annually so you can watch a terminal's crane count and mix change year over year instead of reconstructing it from scratch every time a competitor announces an order.

A quick gut-check, not a formula

If you're trying to sanity-check a single terminal from a photo or a satellite frame, a rough rule holds: count the berths, multiply by three for mainline-capable quays, adjust down for feeder berths and up for any berth clearly built for ULCS calls with wide crane spacing and long booms. It won't replace a real count, but it tells you fast whether a terminal looks under-cranned for the vessels it's advertising it can take, which is often the first sign an OEM order is coming.

Want the real count instead of the gut-check, across every terminal in a market, updated every year? That's the dataset Crane Fleet Mapping builds.