Blog
Track MSC Containers With API
When you think of container shipping giants, MSC (Mediterranean Shipping Company) stands at the top. Founded in 1970, the company has grown from a single vessel into the world’s largest container carrier. Let’s break down how big MSC really is, the routes it dominates, the size of its fleet, and how companies can use JS Cargo to simplify working with MSC’s vast network.
How Big Is MSC?
MSC is a privately owned company headquartered in Geneva, Switzerland. Over the years, it has become the largest container line by capacity, holding roughly 20% of the global market share.
- Operates in 155+ countries
- Employs 200,000+ people worldwide
- Moves millions of containers annually, shaping trade flows across all major markets
In short, MSC isn’t just big. It’s the cornerstone of global trade. However, managing shipments with a company of this size can be overwhelming for businesses.
What Are MSC’s Main Shipping Routes?
MSC runs services across nearly every major ocean corridor. Some of the most important trade lanes include:
- Asia ↔ Europe: Linking Asian manufacturing hubs with European consumer markets
- Asia ↔ North America (Trans-Pacific): Essential for U.S. imports and exports to Asia
- Europe ↔ North America (Trans-Atlantic): Connecting ports like Rotterdam, Antwerp, Hamburg, and New York
- Latin America ↔ Europe / North America: Covering exports of commodities, perishables, and manufactured goods
- Intra-Mediterranean & Africa: Strong feeder and regional networks, reflecting MSC’s Mediterranean roots
What Are MSC’s Container Prefixes?
Containers are identified using MSC’s registered prefixes.
This prefix system ensures containers can be tracked, billed, and managed accurately across global logistics networks.
With JsonCargo, you don’t need to memorize or manually check these prefixes, our system automatically recognizes and tracks them for you.
| Prefix | |
|---|---|
MSCU | MSRU |
MEDU | MSVU |
MSDU | CAIU |
MSMU | FCIU |
GTIU | FFAU |
MSNU | BEAU |
MSPU | TTNU |
MSTU | TRLU |
MSYU | TRIU |
MSZU | SZLU |
MADU | OTPU |
MSBU | FRB0 |
MSGU | EMU9 |
MSRU | CRXU |
MSVU | CRSU |
CAIU | CRLU |
FCIU | CHIU |
What MSC Container Data Can You Access with API?
Instead of building a custom integration with MSC’s system, you can retrieve container statuses with a single API call.
Here are the benefits of the process:
- Track by container number or Bill of Lading: Simply enter the container ID, and the API returns the latest status, events, and location.
- Different Shipping Lines: Whether it’s MSC, Maersk, Hapag-Lloyd, or CMA CGM, the response format is always the same.
- Detailed events: Find out where your MSC container is, where it has been, and what’s next (e.g., “Vessel departed,” “Discharged”).
Additionally, you’ll receive timestamps for the latest port events, the estimated time of arrival at the next port, confirmation that the shipping line is MSC, and technical details such as container type (20ft, 40ft, reefer, etc.).
Example Response: How to Track an MSC Container via API
"data": {
"container_id": "MSCU5285725",
"container_type": "40' HIGH CUBE",
"container_status": "Full Transshipment Discharged",
"shipping_line_name": "Mediterranean Shipping Company",
"shipping_line_id": "0015",
"tare": null,
"shipped_from": "Liverpool, GB",
"shipped_from_terminal": "Maritime Liverpool Cd",
"shipped_to": "Jakarta, JAVA",
"shipped_to_terminal": null,
"atd_origin": "2025-08-30 00:00",
"eta_final_destination": null,
"last_location": "Le Havre, FR",
"last_location_terminal": "Tn Msc",
"next_location": "Singapore, SG",
"next_location_terminal": "Tuas Terminal",
"atd_last_location": "2025-09-15 00:00",
"eta_next_destination": "2025-10-25 00:00",
"timestamp_of_last_location": "2025-09-07 00:00",
"last_movement_timestamp": "2025-09-07 00:00",
"loading_port": "Liverpool, GB",
"discharging_port": "Jakarta, JAVA",
"customs_clearance": null,
"bill_of_lading": null,
"last_vessel_name": "MSC SPRING III",
"last_voyage_number": "RS534A",
"current_vessel_name": "MSC SPRING III",
"current_voyage_number": "RS534A",
"last_updated": "2025-09-08 22:42"
}
}
MSC Container API Tracking Setup:
1. Register for API access
Create your account and get your API key to start using the Container API.
2. Authenticate your requests
Check our API documentation and set the API key in your headers for secure access and to track usage.
3. Configure container tracking
Add your container IDs, IMO, or MMSI numbers to begin tracking specific shipments or vessels.
4. Set up event monitoring
Create milestone events such as gate in/out, stuffing, vessel loading/unloading, and transshipment from our dynamic API data.
5. Integrate with your system
Connect the Maritime API to your platform or dashboard following DCSA standards for structured data exchange.
6. Go live
Start using real-time container tracking with full visibility and automated notifications.
MSC Container Real-Time Tracking Features:
- API access for live container status and current location updates.
Multi-carrier container tracking in one unified dashboard.
Dynamic ETAs calculated from historical delay benchmarks.
Each update includes a timestamp_of_last_location and a date/time stamp.
ETA performance insights help predict arrivals more accurately.
Common Questions About MSC Container Data via API
1. Can I track containers from any shipping line, or only MSC?
The API supports multiple major shipping lines, including MSC, Maersk, CMA CGM, Hapag-Lloyd, and others. You can check the full list of supported carriers in our documentation.
2. How often is MSC container data updated?
Container tracking data for MSC is updated in near real time, depending on the source and events reported by the carrier.
3. What if I don’t know the full MSC container number?
A complete container number (e.g., MSCU1234567) is required for accurate tracking. Alternatively, you can search using the Bill of Lading if you don’t have the full container ID.