Xeneta
Transit times data

Schedules show the plan. Vessels show what happened

Much of the transit data available today is based on carrier-published schedules. They show the plan, not what actually happened.

  1. Announced and actual

    Both transit times, side by side on the same lane.

  2. Real vessel movements

    Actual times from AIS vessel data over the past 30 days.

  3. Promises tested

    See exactly where service performance falls short of the plan.

The data behind it

Measured on real vessel movements

Announced and actual transit times, from AIS data over a rolling 30 days.

Detailed corridors
400+
Vessels tracked
10,000+
Rolling window
30 days
Xeneta transit times data

What's in the dataset

Transit time is the port-to-port travel time of a container. Xeneta gives you two views: announced, from the carrier's published schedule, and actual, from real vessel movements tracked with AIS data on a 30-day rolling window to reflect current conditions.

Announced transit time

The carrier's published schedule at launch: the planned port-to-port journey.

  • Stable baseline
  • By service

Actual transit time

30-day rolling average of real vessel transit times, from AIS data.

  • 30-day rolling
  • AIS-based

Schedules timetable

Planned services and departures by port pair, checked against AIS movements.

  • Delays
  • Blanked sailings
Announced vs actual

See the gap between plan and reality

Track announced and actual transit times on the same lane, with the spread around each and the market rate alongside, so you can see when performance drifts.

Loading page
Our data standards

Trusted and certified

Built on enterprise-grade security, privacy and independence, and quoted by the WSJ, FT and Reuters.

Certified
ISO 27001:2022
Privacy
GDPR compliant
Use cases

When you'll use this data

An objective view of cost and reliability

Compare what a carrier promised with what its vessels deliver, alongside your rates, for an objective view of cost against reliability.

Delivery

Get the data where you need it

Platform

Compare announced and actual transit times on your lanes, by carrier, service and vessel.

Xeneta Ocean

API and Datalink

Pipe transit times into your TMS, control tower or BI stack to keep lead times current.

Talk to us

Reports

Executive-ready reports from Xeneta Expert Analysis that guide decisions and report savings.

Xeneta Expert Analysis
Free ebook

Why the world's best freight teams trust Xeneta

Market Intelligence

Why Xeneta

A better way to navigate freight volatility. Discover how top-performing teams are gaining an edge with deeper, more complete market data.

Why Xeneta
FAQ

Frequently asked questions

The most common questions we hear from procurement, supply chain and freight forwarding teams evaluating Xeneta.

What's the difference between announced and actual transit time?

Announced transit time is the planned port-to-port travel time from the carrier's originally published schedule. Actual transit time is the 30-day rolling average of real vessel transit times on the same port pair, calculated from AIS arrival and departure data.

Announced tells you the plan. Actual tells you what's really happening.

Why does actual sometimes look very different from announced?

Vessels run faster or slower depending on weather, port congestion, bunker economics and how laden they are. Blank sailings and rerouting also shift actual transit.

On some lanes the gap is small and stable; on others, especially during disruption, it can be significant. That gap is the point of showing both.

Where does the data come from?

Neutral vessel movement data from terrestrial and satellite AIS, combined with carrier-published proforma schedules. Announced transit times reflect the original schedule, while actual transit times are calculated from real vessel arrivals and departures.

How often do transit times update?

Actual transit time updates continuously on a 30-day rolling window, reflecting recent vessel movements.

Announced transit time only changes when the carrier redesigns the entire service, for example with a new port rotation, so it stays stable enough to use as a baseline.