Port of Prigorodnoye
In short
Prigorodnoye: no ships in port now, no arrivals and 1 departure in the last 24 h (detected from AIS, as of Oct 2, 2026, 00:33 UTC).
Watch this port
Get an email when Prigorodnoye is busier than usual or is named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows Prigorodnoye.
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.
- In port now
- 0
- Arrivals, last 24 h
- 0
- Departures, last 24 h
- 1
- Ships nearby, last 6 h
- 29
Arrivals and departures AIS-detected
Ships Voydar detected in port from their AIS positions: who is in port now and who left in the last 48 hours. Calls shorter than 30 minutes are not shown, and at places without a charted harbour only ships with an IMO number count. Times UTC.
Left in the last 48 h
| Vessel | Left | Time in port |
|---|---|---|
 KALASOther | Oct 1, 2026, 04:33 UTC | 5 h 8 min |
 ZALIV BAIKALTanker (hazardous cat. A) | Sep 30, 2026, 08:44 UTC | 12 h 48 min |
As of Oct 2, 2026, 00:33 UTC.
In Plus and Pro: this board live in the Terminal, beside the harbour map and the dossier of any ship you pick.
Try the live demo, no sign-upExpected arrivals AIS-detected
Ships whose AIS destination names Prigorodnoye, with the arrival time their crew entered. Reported in the last 24 hours, due within 7 days. Crews type these by hand: a destination can be out of date and an ETA can slip.
2 ships shown, earliest first.
| Vessel | ETA (UTC) | Destination as broadcast | Matched by |
|---|---|---|---|
 XINHANG ENERGYTanker | Oct 2, 2026, 00:01 UTC | RUPGN | UN/LOCODE |
 BLUE DRAGON ITanker | Oct 4, 2026, 01:00 UTC | RUPGN | UN/LOCODE |
Source: AIS voyage reports via AISstream.io global terrestrial AIS. Times are the crew's ETA, not a Voydar estimate. As of Oct 2, 2026, 00:33 UTC.
Arrivals per day AIS-detected
Ships Voydar detected arriving at Prigorodnoye on each of the last 30 days (UTC), counted once per ship per day. A day with no bar had no detected arrivals, which can also mean a gap in our AIS coverage.
Show as a table
| Day (UTC) | Ships arriving |
|---|---|
| Sep 2, 2026 | 0 |
| Sep 3, 2026 | 1 |
| Sep 4, 2026 | 1 |
| Sep 5, 2026 | 0 |
| Sep 6, 2026 | 1 |
| Sep 7, 2026 | 1 |
| Sep 8, 2026 | 0 |
| Sep 9, 2026 | 0 |
| Sep 10, 2026 | 1 |
| Sep 11, 2026 | 0 |
| Sep 12, 2026 | 0 |
| Sep 13, 2026 | 2 |
| Sep 14, 2026 | 0 |
| Sep 15, 2026 | 1 |
| Sep 16, 2026 | 0 |
| Sep 17, 2026 | 1 |
| Sep 18, 2026 | 0 |
| Sep 19, 2026 | 0 |
| Sep 20, 2026 | 0 |
| Sep 21, 2026 | 3 |
| Sep 22, 2026 | 2 |
| Sep 23, 2026 | 1 |
| Sep 24, 2026 | 1 |
| Sep 25, 2026 | 2 |
| Sep 26, 2026 | 0 |
| Sep 27, 2026 | 2 |
| Sep 28, 2026 | 0 |
| Sep 29, 2026 | 1 |
| Sep 30, 2026 | 1 |
| Oct 1, 2026 | 0 |
Vessels near Prigorodnoye
Ships Voydar received on AIS near the port in the last 6 hours, most recent first. Being near a port is not a port call; the board above lists calls.
| Vessel | Type | IMO / MMSI | Last seen |
|---|---|---|---|
| KAPITAN BYANKINCargo | Cargo | IMO 9389291 | |
| VLADIMIR SUNGORKINTug | Tug | IMO 9988841 | |
| BAKHTEMIROther | Other | IMO 9797577 | |
| AZOVTanker | Tanker | IMO 9084401 | |
| FESCO ANASTASIACargo | Cargo | IMO 9505522 | |
| ANIVATug | Tug | IMO 9369253 | |
| SPA008 K-N MUROMTSEVCargo | Cargo | IMO 8729793 | |
| RUBINTug | Tug | IMO 8033883 | |
| KORSAKOVTug | Tug | IMO 9389590 | |
| DOBRYNYATug | Tug | IMO 8730077 | |
| GRAND COSMOSTanker | Tanker | IMO 9323675 | |
| KALASOther | Other | IMO 9797589 | |
| MERTSANAFishing | Fishing | IMO 8324165 | |
 VIDAPleasure craft | Pleasure craft | MMSI 325142300 | |
| BUSSETug | Tug | IMO 9389605 | |
| FLAGMANTanker | Tanker | IMO 8135215 | |
 KAIWO MARU | — | IMO 8869696 | |
| ADONISFishing | Fishing | IMO 9031002 | |
| SEVERNAYA TENPleasure craft | Pleasure craft | MMSI 273325210 | |
| DOMEYAFishing | Fishing | IMO 8864658 | |
| SEVENPleasure craft | Pleasure craft | MMSI 325129500 | |
| ALMAZ | — | IMO 8725541 | |
| KAPITAN SERGEEVTug | Tug | IMO 9871919 | |
| OTTOSHMIDTTug | Tug | IMO 8418590 | |
| SPASATEL KAVDEJKINSearch and rescue | Search and rescue | IMO 9593933 | |
| PAVEL LEONOVPassenger | Passenger | IMO 9872432 | |
| ONWA35314Pleasure craft | Pleasure craft | MMSI 9135314 | |
| ADMIRAL NEVELSKOYPassenger | Passenger | IMO 9872420 | |
| ZAPRAVSHCHIK-05Tanker | Tanker | IMO 8930744 |
Forecast
Model forecast for Prigorodnoye over the next 72 hours, every 6 hours: wind, gusts, waves and visibility. Times in UTC.
| Time (UTC) | Wind (kn) | From | Gusts (kn) | Waves (m) | Period (s) | Visibility (km) |
|---|---|---|---|---|---|---|
| 20 | 251° | 33 | 2 | 6 | 22 | |
| 17 | 287° | 29 | 1.8 | 6 | 23 | |
| 18 | 303° | 27 | 1.6 | 5 | 24 | |
| 16 | 318° | 25 | 1.2 | 4 | 24 | |
| 12 | 318° | 22 | 0.8 | 4 | 24 | |
| 12 | 299° | 20 | 0.7 | 4 | 24 | |
| 5 | 282° | 10 | 0.4 | 3 | 24 | |
| 7 | 265° | 14 | 0.6 | 3 | 24 | |
| 8 | 249° | 13 | 0.6 | 4 | 24 | |
| 11 | 272° | 19 | 0.8 | 4 | 24 | |
| 8 | 258° | 13 | 0.7 | 4 | 24 |
Forecast: ECMWF IFS 0.25° + ECMWF WAM, run of Oct 1, 2026, 12:00 UTC. Visibility: NOAA GFS 0.25° + GFS-Wave (WAVEWATCH III), run of Oct 1, 2026, 18:00 UTC. Waves are taken from the wave model's nearest sea point, 15 km away.
Source: ECMWF open data (IFS 0.25° forecasts, ECMWF WAM waves). This service is based on data and products of the European Centre for Medium-Range Weather Forecasts (ECMWF). Source: www.ecmwf.int. Licence: CC BY 4.0. Licence: CC-BY-4.0 + ECMWF Terms of Use.
Source: NOAA GFS 0.25° and GFS-Wave (WAVEWATCH III) forecasts. Forecast: NOAA NCEP GFS / GFS-Wave (WAVEWATCH III). Licence: US Government work (public domain); NOAA Open Data Dissemination.
A model forecast, not an observation. Not for navigation.
Tools for this port
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/ports/RUPGNUsing 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.