WINDAR
Oil tanker · Panama · built 2007 · AIS Class A
In short
WINDAR (Oil tanker, Panama flag) was last seen on AIS on , at anchor, in the Baltic Sea. Its crew-entered AIS destination is FOR ORDERS; its reported draught is 7 m (voyage report via Digitraffic marine AIS, received Nov 16, 2026, 14:27 UTC). ISM manager: SYNERGY MARITIME PRIVATE LIMITED (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).
Current voyage: from Vysotsk (departed Nov 15, 2026, 01:21 UTC) to FOR ORDERS
- Vessel type
- Oil tanker
- Flag
- Panama
- Year built
- 2007
- Gross tonnage
- 30,042
- Size (length × beam)
- 183 m × 32 m
- ISM manager
- SYNERGY MARITIME PRIVATE LIMITED
Last reported position: 60.0071° N, 28.4636° E · Baltic Sea · See on the map
Watch this ship
Get an email when WINDAR arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 16, 2026, 14:37 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for WINDAR reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
Last reported position
received- Position
- 60.0071° N, 28.4636° E
- Area
- Baltic Sea
- Status
- At anchorWhat do AIS statuses mean?
- Speed
- 0.6 kn
- Course
- 114°
- Heading
- 162°
- Compass: course over ground 114°, heading 162°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 2 port calls (Vysotsk and Tanger Med).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows WINDAR's track before the last 30 days. Voydar has recorded its port calls since October 14, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 183 mone tick every 25 m
Beam 32.2 mPlan outline, to scale
- Name
- WINDAR
- IMO numberWhat is an IMO number?
- 9365362
- MMSIWhat is an MMSI?
- 372777000
- Call signWhat is a call sign?
- 3EKO7
- Flag
- Panama
- Gross tonnageGross tonnage vs deadweight
- 30,042
- Deadweight (DWT)
- Source: Wikidata, record Q83654646. Added to Voydar on October 24, 2026. Licence: CC0 1.0.50,561 t
- Length overall
- 183 m
- Beam
- 32.2 m
- Year built
- 2007
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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 |
|---|---|---|
| Left VysotskAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VysotskAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Tanger MedAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Tanger MedAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left MersinAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MersinAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Texas CityAuthority-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 | 10,689 t | 3,370 t | 117 days | 344 kg |
| 2019 | 5,814 t | 1,853 t | 66 days | 346 kg |
| 2021 | 7,241 t | 2,285 t | 78 days | 357 kg |
| 2022 | 2,513 t | 791 t | 16 days | 716 kg |
| 2023 | 4,648 t | 1,484 t | 64 days | 276 kg |
| 2024 | 7,729 t | 2,464 t | 105 days | 294 kg |
Technical efficiency: EEXI (4.94 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2024 sits among the ships EU MRV lists as “Oil tanker”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile8.99 g per tonne-nautical mile
- Lowest reportedHighest reported
58% of the 1,808 ships in this group reported a lower figure.
Group: lower quartile 5.88 · median 8.11 · upper quartile 12.71
- CO₂ per nautical mile sailed294.1 kg per nautical mile
- Lowest reportedHighest reported
21% of the 1,917 ships in this group reported a lower figure.
Group: lower quartile 316.6 · median 406.3 · upper quartile 494.9
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Vysotsk RUVYS | Nov 13, 2026, 11:09 UTC | Nov 15, 2026, 01:21 UTC | 38 h 12 min |
| Tanger Med MAPTM | Nov 1, 2026, 12:43 UTC | Nov 3, 2026, 21:22 UTC | 2 d 8 h |
| Mersin TRMER | Oct 14, 2026, 06:01 UTC | Oct 20, 2026, 18:58 UTC | 6 d 12 h |
Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | May 11, 2025, 15:08 UTC | EMTY | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Aug 27, 2022, 07:31 UTC | SLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Texas City USTXT | Departure | Nov 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Texas City USTXT | Arrival | Nov 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Oct 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Departure | Oct 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Oct 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Oct 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Guayanilla PRGUY | Departure | Sep 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Guayanilla PRGUY | Arrival | Sep 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: December 30, 2007.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Behaviour at sea Voydar-derived
Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.
| When | What we observed | Confidence |
|---|---|---|
| Nov 15, 2026, 21:21 UTC | Draught change Reported draught went from 6 m to 7 m after leaving Vysotsk. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 3, 2026, 21:52 UTC | Draught change Reported draught went from 7 m to 10 m after leaving Tanger Med. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.
Frequently asked questions
- What kind of ship is WINDAR?
- WINDAR is an oil tanker sailing under the flag of Panama, built in 2007 by SPP Shipbuilding Co., Ltd.. The vessel is 183 m long with a beam of 32.2 m and has a gross tonnage of 30,042.
- Who is recorded as the owner or manager of WINDAR?
- SYNERGY MARITIME PRIVATE LIMITED is recorded as ISM manager for WINDAR (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 WINDAR?
- Voydar has no matched sanctions record displayed for WINDAR 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 WINDAR. Missing records do not establish whether the ship has been detained.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Oil tankers
Other oil tankers with full Voydar profiles. A different set each day. All oil tankers
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/9365362Cite this page
WINDAR. Voydar (voydar.com). https://www.voydar.com/vessel/9365362-windar. Retrieved November 16, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
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.