Richards Bay Coal: Who Controls Berthing Controls the Demurrage
Quote from chief_editor on May 25, 2026, 3:30 pmAt Richards Bay Coal Terminal, berthing order is managed by the terminal, not vessel arrival. The mechanism determines who bears demurrage and who avoids it.
Richards Bay Coal Terminal on South Africa's KwaZulu-Natal coast handles more than 70 million tonnes of export coal per year in peak capacity periods, making it one of the largest coal export facilities in the world. The terminal operates through an allocation system where coal producers and traders book export capacity in advance. Vessel berthing is managed by the terminal operator.
For charterers loading coal at RBCT, the critical fact is this: the order in which vessels berth is not solely determined by the order in which they arrive. The terminal's scheduling takes into account stock availability, train deliveries from the inland mines, and the coordination of multiple coal types and grades. A vessel that arrived first may berth after a vessel that arrived later, if the later vessel's cargo was ready and the first vessel's cargo had supply chain delays from inland.
Laytime, in most charterparties for RBCT loading, begins counting from NOR acceptance — which occurs when the vessel is within the port limits and reports ready. If a vessel waits at anchor for seven days before a berth is assigned, and the charterparty has a three-day laytime allowance with WIBON terms, the vessel has consumed all its laytime in the anchorage before loading even begins. Every day of loading then accrues demurrage.
Terminal Scheduling Is Not a Force Majeure Event
The key question for demurrage disputes at RBCT is whether terminal-controlled delays — berth allocation decisions, stock build-up delays, coal type prioritization — qualify as events that suspend laytime under the charterparty. Most standard bulk charterparties do not contain specific RBCT congestion exceptions, because these charterparties are negotiated as generic documents and the specific terminal's scheduling behavior is not contemplated in the boilerplate terms.
The result: a charterer who loses a berthing slot due to terminal scheduling decisions and consequently accumulates demurrage bears that cost, even though the delay was not caused by anything the charterer did. From the shipowner's perspective, the vessel was ready, the NOR was tendered, laytime was running. The cause of the delay — terminal scheduling — is between the charterer and the terminal, not between the charterer and the shipowner.
For coal traders loading at RBCT, the practical implication is that charterparty negotiation needs to include RBCT-specific provisions if the trader wants protection against terminal-scheduling delays. These provisions — port congestion clauses, terminal scheduling exceptions, or provisions that suspend laytime for terminal-caused delays — are available and are included in better-negotiated charterparties. They require knowledge of RBCT's specific operational behavior and the willingness to negotiate them into the charterparty.
Industry estimates for RBCT loading operations suggest that vessel waiting times of 3 to 8 days have been documented during periods when train deliveries from inland have fallen behind terminal export schedules, creating a situation where coal is being booked for export but not yet available at the terminal. During these periods, vessels accumulate demurrage that was entirely beyond either party's direct control but was allocated to the charterer by standard charterparty terms.
The Transparency Gap
RBCT publishes operational data — vessel queues, stock levels, throughput rates — that experienced RBCT operators use to schedule vessel nominations more carefully. A trader who monitors the terminal's public data before nominating vessels can, to some degree, anticipate congestion periods and adjust laycan windows accordingly. This does not eliminate congestion risk, but it reduces the probability of nominating a vessel into a peak congestion period without the charterparty protection to match.
Traders who load at RBCT repeatedly without understanding the terminal's scheduling system and without monitoring its operational data are accepting demurrage exposure that is at least partially foreseeable. The congestion profile at RBCT — which months are typically busy, which inland supply disruptions have historically caused terminal stockouts — is documented information available to anyone who participates in the South African coal export market with enough frequency to build that knowledge base.
At Richards Bay Coal Terminal, berthing order is managed by the terminal, not vessel arrival. The mechanism determines who bears demurrage and who avoids it.
Richards Bay Coal Terminal on South Africa's KwaZulu-Natal coast handles more than 70 million tonnes of export coal per year in peak capacity periods, making it one of the largest coal export facilities in the world. The terminal operates through an allocation system where coal producers and traders book export capacity in advance. Vessel berthing is managed by the terminal operator.
For charterers loading coal at RBCT, the critical fact is this: the order in which vessels berth is not solely determined by the order in which they arrive. The terminal's scheduling takes into account stock availability, train deliveries from the inland mines, and the coordination of multiple coal types and grades. A vessel that arrived first may berth after a vessel that arrived later, if the later vessel's cargo was ready and the first vessel's cargo had supply chain delays from inland.
Laytime, in most charterparties for RBCT loading, begins counting from NOR acceptance — which occurs when the vessel is within the port limits and reports ready. If a vessel waits at anchor for seven days before a berth is assigned, and the charterparty has a three-day laytime allowance with WIBON terms, the vessel has consumed all its laytime in the anchorage before loading even begins. Every day of loading then accrues demurrage.
Terminal Scheduling Is Not a Force Majeure Event
The key question for demurrage disputes at RBCT is whether terminal-controlled delays — berth allocation decisions, stock build-up delays, coal type prioritization — qualify as events that suspend laytime under the charterparty. Most standard bulk charterparties do not contain specific RBCT congestion exceptions, because these charterparties are negotiated as generic documents and the specific terminal's scheduling behavior is not contemplated in the boilerplate terms.
The result: a charterer who loses a berthing slot due to terminal scheduling decisions and consequently accumulates demurrage bears that cost, even though the delay was not caused by anything the charterer did. From the shipowner's perspective, the vessel was ready, the NOR was tendered, laytime was running. The cause of the delay — terminal scheduling — is between the charterer and the terminal, not between the charterer and the shipowner.
For coal traders loading at RBCT, the practical implication is that charterparty negotiation needs to include RBCT-specific provisions if the trader wants protection against terminal-scheduling delays. These provisions — port congestion clauses, terminal scheduling exceptions, or provisions that suspend laytime for terminal-caused delays — are available and are included in better-negotiated charterparties. They require knowledge of RBCT's specific operational behavior and the willingness to negotiate them into the charterparty.
Industry estimates for RBCT loading operations suggest that vessel waiting times of 3 to 8 days have been documented during periods when train deliveries from inland have fallen behind terminal export schedules, creating a situation where coal is being booked for export but not yet available at the terminal. During these periods, vessels accumulate demurrage that was entirely beyond either party's direct control but was allocated to the charterer by standard charterparty terms.
The Transparency Gap
RBCT publishes operational data — vessel queues, stock levels, throughput rates — that experienced RBCT operators use to schedule vessel nominations more carefully. A trader who monitors the terminal's public data before nominating vessels can, to some degree, anticipate congestion periods and adjust laycan windows accordingly. This does not eliminate congestion risk, but it reduces the probability of nominating a vessel into a peak congestion period without the charterparty protection to match.
Traders who load at RBCT repeatedly without understanding the terminal's scheduling system and without monitoring its operational data are accepting demurrage exposure that is at least partially foreseeable. The congestion profile at RBCT — which months are typically busy, which inland supply disruptions have historically caused terminal stockouts — is documented information available to anyone who participates in the South African coal export market with enough frequency to build that knowledge base.