Natty
Bulk carrier · Liberia · built 2011 · AIS Class A
In short
Natty (Bulk carrier, Liberia flag) was last seen on AIS on , at anchor, in the South Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- Vessel type
- Bulk carrier
- Flag
- Liberia
- Year built
- 2011
- Gross tonnage
- 92,050
- Size (length × beam)
- 291 m × 45 m
- Registered owner
- —
Watch this ship
Get an email when Natty arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows Natty.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
Last reported position
received- Position
- 23.154° S, 43.9534° W
- Area
- South Atlantic Ocean
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0.1 kn
- Course
- 323°
- Heading
- 138°
Voydar detected no port call in the last 30 days.
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- Natty
- IMO numberWhat is an IMO number?
- 9546904
- MMSIWhat is an MMSI?
- 636021273
- Call signWhat is a call sign?
- A8YW7
- Flag
- Liberia
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 92,050
- Deadweight (DWT)
- Source: Wikidata, record Q117026128. Added to Voydar on September 23, 2026. Licence: CC0 1.0.176,000 t
- Length overall
- 291 m
- Beam
- 45 m
- Year built
- 2011
A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Reported departure from Newport NewsAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Newport NewsAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BaltimoreAuthority-reported | USACE foreign traffic vessel entrances & clearances |
Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2019 | 4,477 t | 1,436 t | 38 days | 484 kg |
| 2022 | 3,480 t | 1,101 t | 23 days | 509 kg |
Technical efficiency: EIV (3.12 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Port calls
Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Newport News USNNS | Departure | Dec 3, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Arrival | Nov 28, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Nov 22, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Nov 21, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Sep 14, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Sep 9, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Sep 3, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 3, 2011.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Natty now?
- Natty (Bulk carrier, Liberia flag) was last seen on AIS on Aug 3, 2026, 22:29 UTC, at anchor, in the South Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is Natty?
- Natty is a bulk carrier sailing under the flag of Liberia, built in 2011 by Jiangsu Rongsheng Heavy Industries. The vessel is 291 m long with a beam of 45 m and has a gross tonnage of 92,050.
- What sanctions and inspection records does Voydar hold for Natty?
- Voydar has no matched sanctions record displayed for Natty from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Natty. Missing records do not establish whether the ship has been detained.
Use this data
This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.
GET /api/v1/vessels/9546904Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.