Blog

ONE Shipment Tracking: How to Track ONE Containers

Tracking shipement from Ocean Network Express (ONE) can sometimes feel confusing if you don’t know where to start. Whether you’re a freight forwarder, importer, or logistics operator, understanding how ONE container tracking works, especially using container prefixes, makes the process much simpler.

In this guide, we’ll break it down in a practical way.

What is ONE Container Tracking?

ONE is one of the world’s largest container shipping lines, formed through the integration of K Line, MOL, and NYK.

When we talk about ONE container tracking, we mean following a container’s journey across ports, vessels, and terminals from origin to final destination.

With the right tracking tool (like JsonCargo), you can access:

Latest container event
Current container location
Estimated time of arrival (ETA)
Shipment milestones (loaded, discharged, gate-in, etc.)

Understanding ONE Container Prefix:

Every container follows a standardized format defined by ISO 6346.

A typical container number looks like this:

ONEU1234567

Here’s how it breaks down:

ONE → Owner code (Ocean Network Express)
U → Equipment category (freight container)
123456 → Serial number
7 → Check digit

This is exactly what you can use when performing ONE container tracking.

How to Track ONE Containers?

Tracking a ONE container is straightforward when you have the full container number.

Step-by-step:

Enter the container number (e.g. ONEU1234567)
Query a tracking system (like JsonCargo API)
Retrieve structured data, including:
- Last event + timestamp
- Current country/port
- ETA to destination
- Vessel information

Unlike carrier websites, an API-based approach gives you:

Unified tracking across multiple carriers
Structured JSON responses
Easy Excel or system integration

Why Prefix Matters in Container Tracking?

The container prefix is more important than most people think.

It helps:

Identify the shipping line instantly
Route the request to the correct data source
Avoid mismatches between carriers
Improve tracking accuracy

For example:

ONEU → ONE (Ocean Network Express)
MSCU → MSC
MAEU → Maersk

Without the prefix, tracking becomes unreliable or even impossible.

Check our available prefix for ONE line.

Common Use Cases for ONE Shipment Tracking:

Companies using ONE container tracking typically need:

Automated Excel updates for shipments
Internal dashboards with live container status
Alerts when containers reach a port
Visibility over imports from Asia (China, Japan, Southeast Asia)

JsonCargo simplifies this by aggregating tracking data into one consistent API.

Example: What Shipment Tracking Data You Can Get

When you track a ONE container, you can retrieve:

Last event: “Discharged at Port of Valencia”
Event date: Timestamp of last update
Current country: Spain
ETA: Estimated arrival at next port
Transport mode: Vessel / rail / truck

This is exactly the type of data logistics teams need to operate efficiently.

				
					{
    "data": {
        "container_id": "GCXU2258738",
        "container_type": "20'DRY ST.",
        "container_status": "Empty Container Returned from Customer",
        "shipping_line_name": "Ocean Network Express",
        "shipping_line_id": "0013",
        "tare": "16,480.000",
        "shipped_from": "YUEYANG, HUNAN, CHINA",
        "shipped_from_terminal": "YUEYANG CHENGLINGJI  INTERNATIONAL CONTAINER TERMI",
        "shipped_to": "PIRAEUS, GREECE",
        "shipped_to_terminal": "PIRAEUS CONTAINER TERMINAL S.A",
        "atd_origin": "2026-04-18 19:45",
        "eta_final_destination": "2026-06-11 20:15",
        "last_location": "PIRAEUS, GREECE",
        "last_location_terminal": "PIRAEUS CONTAINER TERMINAL S.A",
        "next_location": null,
        "next_location_terminal": null,
        "atd_last_location": "2026-04-18 19:45",
        "eta_next_destination": null,
        "timestamp_of_last_location": "2026-06-11 20:15",
        "last_movement_timestamp": "2026-06-16 14:06",
        "loading_port": "SHANGHAI, SHANGHAI, CHINA",
        "discharging_port": "PIRAEUS, GREECE",
        "last_vessel_name": "YM WELLNESS",
        "last_voyage_number": "0048",
        "current_vessel_name": null,
        "current_voyage_number": null,
        "last_updated": "2026-06-30 10:16"
    }
}

ONE Containers 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.

Frequently Asked Questions About ONE Containers Data via API

1. Can I track only ONE containers?
The API supports multiple carriers, including ONE and other major shipping lines.

2. How often is the data updated?
Tracking data is updated frequently, depending on carrier event reporting.

3. What if I don’t have the full container number?
A full container number is recommended, but Bill of Lading tracking is also available.