Where is Moscow River now?

Seadar has no displayable AIS position for Moscow River in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.

What kind of ship is Moscow River?

Moscow River is a ship, built in 1999 by NKK. The vessel is 243 m long and has a gross tonnage of 56,076.

What sanctions and inspection records does Seadar hold for Moscow River?

Seadar has no matched sanctions record displayed for Moscow River 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 Moscow River. Missing records do not establish whether the ship has been detained.

Moscow River

ship · built 1999

IMO9165542No AIS position on record

Open in Terminal

In short

Moscow River (ship) has no AIS position on record with Seadar.

Vessel type: ship
Flag: —
Year built: 1999
Gross tonnage: 56,076
Size (length × beam): 243 m
Registered owner: —

Watch this ship

Get an email when Moscow River 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 Moscow River.

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

No AIS position on record for this vessel. Identity and particulars are below.

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)

Try the live demo, no sign-up

Identity & particulars

Name: Moscow River
IMO numberWhat is an IMO number?: 9165542
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: ship
Gross tonnageGross tonnage vs deadweight: 56,076
Length overall: 243 m
Beam: —
Year built: 1999

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: NKK
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 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
Oct 1, 2016	Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported	USACE foreign traffic vessel entrances & clearances
Sep 16, 2016	Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported	USACE foreign traffic vessel entrances & clearances
Sep 14, 2016	Reported arrival at 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.

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
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Oct 1, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Sep 16, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Sep 14, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRP	Departure	Jul 23, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRP	Arrival	Jul 21, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Jul 17, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Jul 16, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTR	Departure	Jul 6, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTR	Arrival	Jul 6, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTR	Departure	Jun 16, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTR	Arrival	Jun 12, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Beaumont USBPT	Departure	Apr 17, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 30, 2004.

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 Moscow River now?: Seadar has no displayable AIS position for Moscow River in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Moscow River?: Moscow River is a ship, built in 1999 by NKK. The vessel is 243 m long and has a gross tonnage of 56,076.
What sanctions and inspection records does Seadar hold for Moscow River?: Seadar has no matched sanctions record displayed for Moscow River 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 Moscow River. 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/9165542

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

Using 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.

See plans