Kpler's "Flows function" has a feature called the "by route" split, which helps users analyze the main routes that vessels travel. It’s important to know that this feature relies on the presence of a future Port Call (when vessels signal for a specific zone) or passes through one of the pre-defined checkpoints. The timing of the Flows split “by route” is also grouped by their Export or Import date (as opposed to the time of crossing of the canals).

Therefore, when you split flows by route, the data will be continually changing for ongoing voyages, as vessels move through these zones. In the example below, 356 kbd exports from Western Russian ports to India appear to be via ‘other routes’. However, these flows via ‘other routes’ are likely to be updated to the ‘Suez Canal’ once the vessel signals a specific zone or passes through the pre-defined checkpoint.

Vessels that have not signaled a specific zone or passed through a pre-defined checkpoint will only appear under ‘other routes’. However, once the vessel passes through the pre-defined checkpoint, our algorithm will include the specific route used. Eg. Paros signaled for its destination i.e Mangalore. Therefore, there was no Suez Canal port call created and therefore Paros will appear under ‘other routes’ when searching for flows, split by route.

For the same vessel, Paros, once the vessel started to transit through the checkpoint, our algorithm included the specific route used. Therefore, our flows, split by route, will then include the vessel Paros under the Suez Canal route and no longer under ‘other routes’.

Vessels will also be considered as passing through a route if they send a signal for the specific zone. For instance, Cangjie transmitted an AIS signal for the Suez Canal. Therefore, our route-based analysis of flows will account for this specific trade to be via the Suez Canal.