Tigr 2
Reefer ship · Russia · built 1993 · AIS Class A
In short
Tigr 2 (Reefer ship, Russia flag) was last seen on AIS on , under way at 12.9 kn, in the Sea of Okhotsk. Seadar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- Vessel type
- Reefer ship
- Flag
- Russia
- Year built
- 1993
- Gross tonnage
- 7,329
- Size (length × beam)
- 134 m × 20 m
- Registered owner
- —
Watch this ship
Get an email when Tigr 2 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 Tigr 2.
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
- 46.2706° N, 143.1658° E
- Area
- Sea of Okhotsk
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 12.9 kn
- Course
- 168°
- Heading
- 163°
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
- Tigr 2
- IMO numberWhat is an IMO number?
- 9061198
- MMSIWhat is an MMSI?
- 273385170
- Call signWhat is a call sign?
- UBFP9
- Flag
- Russia
- Vessel type
- Reefer ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 7,329
- Deadweight (DWT)
- Source: Wikidata, record Q117080414. Added to Seadar on September 23, 2026. Licence: CC0 1.0.7,748 t
- Length overall
- 134 m
- Beam
- 20 m
- Year built
- 1993
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 Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Reported departure from PonceAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at PonceAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PonceAuthority-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 |
|---|---|---|---|---|
| Ponce PRPSE | Departure | Aug 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Arrival | Aug 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Departure | Aug 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TONGASS NARROWS, AK | Arrival | Aug 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Departure | Jul 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Arrival | Jul 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Departure | Jun 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| UNALASKA ISLAND, ALASKA (INCLUDING DUTCH & ILIULIUK HARBORS) | Arrival | Jun 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BELLINGHAM BAY AND HARBOR, WA | Departure | Jun 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BELLINGHAM BAY AND HARBOR, WA | Arrival | Jun 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW BEDFORD AND FAIRHAVEN HARBOR, MA | Departure | Jan 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW BEDFORD AND FAIRHAVEN HARBOR, MA | Arrival | Dec 28, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: March 16, 2005.
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 Tigr 2 now?
- Tigr 2 (Reefer ship, Russia flag) was last seen on AIS on Sep 15, 2026, 05:35 UTC, under way at 12.9 kn, in the Sea of Okhotsk. Seadar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is Tigr 2?
- Tigr 2 is a reefer ship sailing under the flag of Russia, built in 1993 by Kanasashi Heavy Industries. The vessel is 134 m long with a beam of 20 m and has a gross tonnage of 7,329.
- What sanctions and inspection records does Seadar hold for Tigr 2?
- Seadar has no matched sanctions record displayed for Tigr 2 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 Tigr 2. 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/9061198Using 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.