SUMMIT RIVER
Tanker · Panama · AIS Class A
In short
SUMMIT RIVER (Tanker, Panama flag) was last seen on AIS on , under way at 9.8 kn, near Pulau Sebarok (Strait of Malacca). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is SG SIN-PGBG, with an ETA of Oct 6, 2026, 03:00 UTC; its reported draught is 8.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 01:33 UTC). ISM manager: K MARINE SHIP MANAGEMENT PTE. LTD. (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).
- Vessel type
- Tanker
- Flag
- Panama
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- K MARINE SHIP MANAGEMENT PTE. LTD.
Watch this ship
SUMMIT RIVER has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 1.1644° N, 103.7642° E
- Area
- Strait of Malacca
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 9.8 kn
- Course
- 237°
- Heading
- 235°
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- SUMMIT RIVER
- IMO numberWhat is an IMO number?
- 9369461
- MMSIWhat is an MMSI?
- 370163000
- Call signWhat is a call sign?
- 3ERT4
- Flag
- Panama
- Vessel type
- Tanker
- AIS ship type
- Tanker (hazardous cat. D)
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
PanamaA 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 year 2024 · reported · confidence 0.9 · retrieved Oct 5, 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 HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Nov 27, 2015衝突 · タンカー運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)三重県鳥羽市神島南東方沖 神島灯台から真方位127°3.5海里(M)付近
LPGタンカーSUMMIT RIVER漁船傳榮丸衝突Report published Nov 24, 2016
LPGタンカーSUMMIT RIVERは、南東進中、また、漁船傳榮丸は、えい網しながら南東進中、両船が衝突した。
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典：運輸安全委員会「船舶事故等調査報告書」（https://jtsb.mlit.go.jp/）。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
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 |
|---|---|---|---|---|
| 2021 | 4,464 t | 1,427 t | 30 days | 408 kg |
| 2024 | 7,985 t | 2,543 t | 70 days | 378 kg |
Technical efficiency: EIV (8.33 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 |
|---|---|---|---|---|
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Dec 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Dec 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Oct 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Oct 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Jul 14, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Jul 12, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Jul 2, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Jul 2, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Feb 20, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Feb 14, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 14, 2015.
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 SUMMIT RIVER now?
- SUMMIT RIVER (Tanker, Panama flag) was last seen on AIS on Oct 6, 2026, 02:42 UTC, under way at 9.8 kn, near Pulau Sebarok (Strait of Malacca). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was SG SIN-PGBG (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 01:33 UTC). This report does not confirm the ship’s current route.
- What kind of ship is SUMMIT RIVER?
- SUMMIT RIVER is a tanker sailing under the flag of Panama.
- Who is recorded as the owner or manager of SUMMIT RIVER?
- K MARINE SHIP MANAGEMENT PTE. LTD. is recorded as ISM manager for SUMMIT RIVER (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for SUMMIT RIVER?
- Voydar has no matched sanctions record displayed for SUMMIT RIVER from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for SUMMIT RIVER. 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 Voydar 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/9369461Using 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.