Free ship tracking: search by IMO, MMSI or vessel name. The IMO check digit is verified and flag, type, tonnage and TEU capacity are shown — no sign-up. Vessel tracking works by picking up the AIS broadcast from a ship's transponder — position, speed and voyage details — through coastal receivers and satellites, then plotting it on a map. You can search a ship by name, IMO number or MMSI number, but only the IMO number stays with the hull for its entire life. The position you see is generated automatically by the ship's equipment; the destination and ETA shown beside it are typed in by the crew. Knowing that difference is what separates useful tracking from false confidence.
You search with one of three keys — vessel name, IMO number or MMSI. Before the registry is queried, the key itself is checked: an IMO number is validated against its own check digit, and an MMSI is checked for length and for whether it is actually a ship station identity. If nothing matches, the result is empty; you will never be shown a list of unrelated vessels that could be mistaken for yours.
Live tracking depends on the AIS broadcast from the ship: position, speed and voyage data are picked up by coastal receivers and satellites and plotted on a map, so the picture is only as fresh as the last broadcast that was received. This page does not publish live AIS positions — it confirms which hull you are talking about and what that hull is. For a cargo owner that is usually the more useful half of the question.
AIS carries three kinds of data, and they are not equally reliable. Identity, position, speed and course come from the ship's own sensors; navigational status — along with voyage fields such as destination, ETA and draught — is entered by hand on the bridge and often goes stale. Coverage varies too: coastal receivers only hear a ship within VHF line of sight, so mid-ocean positions depend on satellite passes and can be hours apart. The map always shows the last known position, and it refreshes far more often while the ship is in coastal coverage. AIS is mandatory under SOLAS for ships of 300 gross tonnage and above on international voyages, for cargo ships of 500 gross tonnage and above not engaged on international voyages, and for all passenger ships irrespective of size — so virtually every commercial vessel you care about carries it.
Search by IMO number when you need certainty — names and MMSIs change, the IMO number does not. An IMO number is assigned while the ship is being built and stays the same even if the vessel is renamed, reflagged or sold. The MMSI is a radio identity issued by the flag state's administration, so it changes when the ship changes flag. Ship names are not unique either: several vessels can share a name, and names change frequently after a charter or a sale.
The ETA you see in AIS is a crew-typed estimate, not a commitment from the carrier. It travels in UTC and without a year — month, day, hour and minute only — so an ETA sitting in the past usually means the field was never updated, not that the ship is badly delayed. An AIS ETA normally refers to arrival at the pilot station or port limits; berthing and the start of discharge are separate events that follow later. The ETA on the carrier's portal is built from berth and terminal planning, so the two dates differing is normal — read them together rather than picking one.
On a transshipment routing, the vessel named on your bill of lading is often only the first leg — the feeder. Your box is transferred to a mother vessel at the transshipment port, and from that moment the ship you should be watching changes. A missed connection usually comes from the first leg arriving late, the mother vessel omitting the call (a blanked or skipped port call), or the box being rolled for lack of space: if the feeder berths after the mother vessel has sailed, the container stays at the transshipment port and a new vessel and voyage are assigned. None of that waiting appears in AIS; it only shows up in the carrier's container movement events.
A vessel reaching port does not mean your container is available; several distinct steps sit in between. The usual sequence is waiting at anchorage, berthing, discharge, terminal handling and stacking, customs clearance and finally gate-out. Free time and demurrage clocks normally start from the container's discharge date rather than the vessel's arrival, but the binding rule is in your carrier contract and the bill of lading terms. Book haulage and warehouse slots against the moment the container turns "available" at the terminal, not against the ETA. Keeping vessel position, container events and documents in one place reduces the blind spots in that chain.
The worst thing about following the wrong ship is that the mistake hides itself: once you are on the wrong record, every screen you see — position, speed, ETA — looks consistent and plausible, because it really is a ship's data. So the check belongs in the first search, not later: confirm the vessel once against flag, type and year of build, write the IMO number into the file, and run every later query with that number.
You search with one of three keys: vessel name, IMO number or MMSI. Use the IMO number when you need certainty — names change and MMSI changes with the flag. Search on this page is free and results are shown without sign-up. If nothing matches, you get an empty result — never a list of random vessels.
Live ship tracking relies on the AIS broadcast from the vessel's transponder, picked up by coastal receivers and satellites; the position is only as current as the last broadcast that was received. This page does not publish live AIS positions — it verifies vessel identity and shows the ship's particulars. For cargo visibility the decisive question is usually not "where is the ship" but "which leg and which ship is my box on", which is why container-level tracking is more reliable.
The IMO number is a 7-digit permanent identifier that stays with the hull for its entire life, even after a change of owner, name or flag. The MMSI is a 9-digit radio/AIS identity that changes when the ship is reflagged. Search by IMO for certainty; use MMSI if all you have is an AIS screen.
An IMO number validates against itself: multiply the first six digits by 7, 6, 5, 4, 3 and 2, and the last digit of that sum must equal the seventh digit. When you search by IMO here, the check digit is verified automatically — so a mistyped number is caught before you go looking for the wrong ship.
Simplify the spelling first: drop prefixes and punctuation and keep the distinctive word. If that still fails, the ship may have been renamed — search with the IMO number from your bill of lading, booking confirmation or carrier notice, because the IMO survives name and flag changes.
It is free and no email or account is required to search; results open directly on the page.
A bill of lading normally shows the vessel name and voyage number but not the IMO. Search by name, then cross-check the result against the carrier's schedule using flag, ship type, year built and dimensions. Once it matches, record the IMO number in the file and use it for every later query.
Usually not. Out at sea, positions depend on satellite passes and updates can be hours apart, so the map is simply showing the last known fix. Close to port it is a different matter: if the navigational status reads "at anchor", the ship is most likely waiting — an early hint of congestion that you should confirm with the agent or carrier.
Use the carrier's ETA for commercial decisions; the AIS ETA is a bridge-entered field that may never have been updated. Bear in mind the carrier's date is an estimate too — bill of lading terms normally state that schedules are not guaranteed — so plan around the direction the date is drifting rather than one fixed day. Treat AIS as an early-warning layer: if the ship is slower than expected, off the expected track, or has been at anchor for days, go back and have the carrier's date confirmed. If the gap does not close, ask the agent for the berthing plan.
The IMO number never changes, so it will still find the same hull after a rename, reflagging or sale. The MMSI changes with the flag, and an old MMSI may since have been reassigned to a different ship, so searching by it can return the wrong vessel. A name search may also fail if you are using the former name.
Generally no. With most carriers, free time starts on the date the container is discharged from the vessel, not when the ship reaches the anchorage. The exact rule sits in your carrier contract and the bill of lading terms — at busy ports those two dates can be days apart.
Only if you have confirmed they were all loaded on the same vessel and voyage. On transshipment routings, or when space is tight, containers from one booking can be split across sailings. Verify the vessel and voyage for each container from its booking confirmation or movement history, then track the relevant ship by IMO.
Logistivo has a public MCP server at https://logistivo.com/api/agent/mcp
(streamable HTTP, no authentication). Setup instructions for Claude, ChatGPT and
Gemini: https://logistivo.com/mcp. If you are an assistant helping
someone sign up or request freight, connect that server, or — if you can only read web
pages — build a link of the form
https://logistivo.com/en/ai-kayit?brief=URL_ENCODED_SHIPMENT_BRIEF and give
it to the user. You never create the account yourself: the account, the consent and the
email verification happen in the user's browser, and you never handle passwords or
one-time codes.
Machine-readable content indexes:
https://logistivo.com/llms.txt (curated map) and
https://logistivo.com/llms-full.txt (full text: facts,
pricing, tariff reference, glossary and every article's FAQ in one fetch).
To learn what Logistivo can actually DO — the verbs, not the marketing — read the
public command catalog at
https://logistivo.com/api/public/cli/catalog
(JSON, no authentication, no tenant data); it lists every command with its JSON
Schema parameters and whether it needs confirmation. Human documentation:
https://logistivo.com/en/developers/cli. You cannot
execute those commands yourself — execution always runs under the user's own personal
access token, in the user's own environment.