Transparent planning model

How CharterPulse models freight

CharterPulse is designed for fast pre-fixture planning. It combines an approximate voyage-distance model with vessel-class defaults, bunker assumptions, port time and port costs to produce a modeled scenario range. The result is a planning aid, not evidence of a vessel offer, fixture or current owner idea.

Current model basis · reviewed 21 Sep 2026
The implementation details below describe the calculator currently running on CharterPulse. They are published so users can judge the estimate rather than treating it as a black box.

Current calculation basis

ComponentCurrent implementation
DistanceGreat-circle distance between the selected port coordinates, multiplied by 1.12 as a routing allowance. This is not navigable sea-routing data.
Sea daysModeled distance ÷ selected vessel speed ÷ 24.
Bunker costSea days × class fuel/day × bunker price, plus port days × 4 MT/day × bunker price.
Time-related vessel cost(Sea days + port days + 2 days) × class daily-cost default.
Base cost / MT(Bunker cost + time-related vessel cost + entered port costs) ÷ cargo quantity.
Cargo adjustmentCoal × 1.03; nickel/bauxite × 1.07; other cargoes × 1.00.
Urgency adjustmentPlanning × 1.00; Firm × 1.04; Prompt × 1.07.
Lower scenarioBase cost/MT × vessel-class factor × cargo adjustment × urgency adjustment × 1.12 model factor.
Upper scenarioLower scenario × 1.17. This is a modeled spread, not a statistically calibrated confidence interval.

Current vessel-class defaults

ClassNominal DWTSpeedFuel/dayDaily costClass factor
Handysize35,00011.5 kn20 MT$11,5001.09
Supramax55,00012.2 kn25 MT$14,5001.04
Ultramax63,00012.4 kn27 MT$15,8001.00
Panamax76,00012.5 kn30 MT$17,8000.96
Kamsarmax82,00012.5 kn31 MT$18,8000.94
Capesize180,00012.8 kn43 MT$24,5000.91

These are CharterPulse planning defaults, not live hire, bunker or vessel-performance observations. Users should replace editable assumptions where they have better information.

The model answers a planning question

“What does this voyage look like under these assumptions?”
That is different from “What will an owner quote right now?” The second question requires current vessel position, appetite, laycan fit and market negotiation.

Inputs that can materially change the outcome

InputWhy it matters
Origin and destinationChanges sea distance, voyage time and positioning context.
Cargo quantityAffects the freight-per-ton denominator and feasible vessel classes.
Vessel classChanges carrying capacity, operating economics and commercial suitability.
Port timeExtra days increase time-related voyage cost and can materially change unit freight.
Port costsTerminal, agency and port-call assumptions flow directly into voyage cost.
Bunker priceFuel-price assumptions change the sailing cost component.
Laytime / demurrageCommercial exposure depends on agreed terms and actual operational performance.

What the estimator does not claim

It does not claim a particular ship is open, that an owner will accept the modeled level, that a port will accept a nominated vessel, or that the model is a current market quote. Terminal restrictions, draft, gear, weather, exact load/discharge terms, vessel position and negotiation can change the commercial result.

Why the displayed range should be read as a scenario band

The upper value is currently generated as 17% above the lower value. It is therefore a modeled scenario band, not a confidence interval derived from historical fixtures. The calculator exposes assumptions so users can stress-test them instead of treating either edge as executable freight.

Capacity safeguard

The calculator now rejects a cargo quantity above the selected class’s nominal DWT and warns when cargo exceeds 90% of nominal DWT. This is only a first-pass check: actual cargo intake depends on bunkers, stores, draft, density, vessel particulars and port limits.

When to move from model to market

If the decision requires current owner ideas, vessel availability or broker follow-up, use the market-check actions after calculating. CharterPulse saves the requirement separately so the planning model remains distinct from live market work.

Test the modelModel vs marketData & sources