INDUSTRIAL URSULA
General cargo ship · Antigua & Barbuda · built 2008 · AIS Class A
In short
INDUSTRIAL URSULA (General cargo ship, Antigua & Barbuda flag) was last seen on AIS on , under way at 13.6 kn, in the Gulf of Mexico. Seadar has no more recent AIS position for this ship. Its current location cannot be established from this report. ISM manager: SAL Shipping UG (haftungsbeschrankt) & Co. KG MS "INDUSTRIAL URSULA" (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- General cargo ship
- Year built
- 2008
- Gross tonnage
- 9,618
- Size (length × beam)
- 138 m × 21 m
Watch this ship
Get an email when INDUSTRIAL URSULA 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 INDUSTRIAL URSULA.
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
- 29.4647° N, 93.2331° W
- Area
- Gulf of Mexico
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 13.6 kn
- Course
- 175°
- Heading
- 173°
Seadar detected no port call in the last 30 days.
Port calls are detected by Seadar 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
- INDUSTRIAL URSULA
- IMO numberWhat is an IMO number?
- 9435117
- MMSIWhat is an MMSI?
- 305245000
- Call signWhat is a call sign?
- V2DK8
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 9,618
- Deadweight (DWT)
- Source: Wikidata, record Q84261475. Added to Seadar on September 23, 2026. Licence: CC0 1.0.12,743 t
- Length overall
- 138.5 m
- Beam
- 21.3 m
- Year built
- 2008
Antigua & BarbudaA 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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · confidence 0.9 · retrieved Sep 28, 2026
Timeline
Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| ISM manager: SAL Shipping UG (haftungsbeschrankt) & Co. KG MS "INDUSTRIAL URSULA" (previously Krey Schiffahrts GmbH & Co. MS "FRIEDA" KG) | Seadar relationship-change derivation (derived by Seadar from EU MRV (THETIS-MRV) emissions) | |
| Reported arrival at LongviewAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from LongviewAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from SeattleAuthority-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 |
|---|---|---|---|---|
| 2018 | 4,925 t | 1,575 t | 123 days | 176 kg |
| 2019 | 10,320 t | 3,283 t | 209 days | 175 kg |
| 2020 | 1,678 t | 533 t | 33 days | 165 kg |
| 2022 | 3,706 t | 1,183 t | 62 days | 231 kg |
| 2023 | 3,138 t | 1,000 t | 59 days | 204 kg |
| 2024 | 7,568 t | 2,420 t | 148 days | 174 kg |
| 2025 | 3,145 t | 1,002 t | 63 days | 178 kg |
Technical efficiency: EIV (13.5 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 Seadar 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 |
|---|---|---|---|---|
| Longview USLOG | Arrival | Nov 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Departure | Nov 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Nov 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Oct 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Panama City USPFN | Departure | Jan 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Panama City USPFN | Arrival | Jan 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jan 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jan 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Departure | Dec 30, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lake Charles USLCH | Arrival | Dec 28, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jul 9, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jul 8, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: December 15, 2008.
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 INDUSTRIAL URSULA now?
- INDUSTRIAL URSULA (General cargo ship, Antigua & Barbuda flag) was last seen on AIS on Sep 4, 2026, 04:02 UTC, under way at 13.6 kn, in the Gulf of Mexico. Seadar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is INDUSTRIAL URSULA?
- INDUSTRIAL URSULA is a general cargo ship sailing under the flag of Antigua & Barbuda, built in 2008. The vessel is 138.5 m long with a beam of 21.3 m and has a gross tonnage of 9,618.
- Who is recorded as the owner or manager of INDUSTRIAL URSULA?
- SAL Shipping UG (haftungsbeschrankt) & Co. KG MS "INDUSTRIAL URSULA" is recorded as ISM manager for INDUSTRIAL URSULA (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Seadar hold for INDUSTRIAL URSULA?
- Seadar has no matched sanctions record displayed for INDUSTRIAL URSULA 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 INDUSTRIAL URSULA. Missing records do not establish whether the ship has been detained.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Seadar profile.
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/9435117Using 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.