FERICEK
Chemical tanker · Türkiye · built 1996 · AIS Class A
In short
FERICEK (Chemical tanker, Türkiye flag) was last seen on AIS on , at anchor, near Ambarli (Sea of Marmara). Its crew-entered AIS destination is ESVIL (Villagarcia de Arosa), with an ETA of Nov 30, 2026, 09:00 UTC; its reported draught is 8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 15, 2026, 22:04 UTC). ISM manager: BEYKIM DENIZCILIK GEMI ISLETMECILIGI SAN. VE TIC. A.S. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Varna (departed Nov 14, 2026, 23:38 UTC) to ESVIL (Villagarcia de Arosa)
- Vessel type
- Chemical tanker
- Flag
- Türkiye
- Year built
- 1996
- Gross tonnage
- 6,737
- Size (length × beam)
- 126 m × 19 m

Last reported position: 40.9543° N, 28.7718° E · Sea of Marmara · See on the map
Watch this ship
Get an email when FERICEK reaches Villagarcia de Arosa, and when it 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 17, 2026, 17:13 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for FERICEK 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
- 40.9543° N, 28.7718° E
- Area
- Sea of Marmara
- Status
- At anchorWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 23°
- Heading
- 136°
- Compass: course over ground 23°, heading 136°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 3 port calls (Varna, Kumport, and Koper).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows FERICEK's track before the last 30 days. Voydar has recorded its port calls since July 15, 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 126 mone tick every 25 m
Beam 19 mPlan outline, to scale
- Name
- FERICEK
- IMO numberWhat is an IMO number?
- 9125267
- MMSIWhat is an MMSI?
- 271046574
- Call signWhat is a call sign?
- TCA5362
- Flag
- Türkiye
- Vessel type
- Detailed type from WikidataChemical tanker
- Gross tonnageGross tonnage vs deadweight
- 6,737
- Length overall
- 126 m
- Beam
- 19 m
- Year built
- 1996
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 years 2024–2025 · 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 VarnaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VarnaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KumportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KumportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KoperAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KoperAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from PAULSBORO, NJAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at PAULSBORO, NJAuthority-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.
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 |
|---|---|---|---|---|
| 2019 | 4,990 t | 1,594 t | 119 days | 177 kg |
| 2020 | 8,037 t | 2,507 t | 205 days | 170 kg |
| 2021 | 6,414 t | 2,013 t | 164 days | 167 kg |
| 2022 | 6,605 t | 2,096 t | 169 days | 178 kg |
| 2023 | 6,591 t | 2,098 t | 173 days | 174 kg |
| 2024 | 3,560 t | 1,134 t | 88 days | 171 kg |
| 2025 | 3,192 t | 1,004 t | 144 days | 160 kg |
Technical efficiency: EIV (16.35 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 2025 sits among the ships EU MRV lists as “Chemical tanker”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile36.09 g per tonne-nautical mile
- Lowest reportedHighest reported
85% of the 1,489 ships in this group reported a lower figure.
Group: lower quartile 10.24 · median 15.04 · upper quartile 25.97
- CO₂ per nautical mile sailed160.3 kg per nautical mile
- Lowest reportedHighest reported
8% of the 1,516 ships in this group reported a lower figure.
Group: lower quartile 203.4 · median 250.2 · upper quartile 301
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 |
|---|---|---|---|
| Varna BGVAR | Nov 14, 2026, 04:56 UTC | Nov 14, 2026, 23:38 UTC | 18 h 42 min |
| Kumport TRKMX | Nov 8, 2026, 19:18 UTC | Nov 11, 2026, 18:03 UTC | 2 d 22 h |
| Koper SIKOP | Oct 30, 2026, 22:03 UTC | Oct 31, 2026, 21:08 UTC | 23 h 5 min |
| Cartagena ESCAR | Oct 6, 2026, 08:55 UTC | Oct 7, 2026, 15:04 UTC | 30 h 9 min |
| Barcelona ESBCN | Sep 22, 2026, 05:25 UTC | Sep 28, 2026, 21:08 UTC | 6 d 15 h |
| Gibraltar GIGIB | Sep 13, 2026, 00:38 UTC | Sep 13, 2026, 08:43 UTC | 8 h 5 min |
| Scheveningen NLSCE | Jul 15, 2026, 18:15 UTC | Jul 18, 2026, 20:18 UTC | 3 d 2 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 |
|---|---|---|---|---|
| PAULSBORO, NJ | Departure | Mar 29, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Arrival | Mar 29, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jan 25, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jan 20, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT HESS ST. CROIX ISLAND, VI | Arrival | Jan 14, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT HESS ST. CROIX ISLAND, VI | Departure | Jan 12, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Oct 26, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Oct 24, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Sep 28, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Sep 28, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Sep 27, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Sep 22, 2004(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 24, 2002.
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 14, 2026, 22:32 UTC | Draught change Reported draught went from 7.1 m to 8 m while in port at Varna. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 7, 2026, 14:32 UTC | Draught change Reported draught went from 7.2 m to 5.3 m while in port at Cartagena. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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 FERICEK?
- FERICEK is a chemical tanker sailing under the flag of Türkiye, built in 1996 by Cantiere Navale de Poli S.p.A.. The vessel is 126 m long with a beam of 19 m and has a gross tonnage of 6,737.
- Who is recorded as the owner or manager of FERICEK?
- BEYKIM DENIZCILIK GEMI ISLETMECILIGI SAN. VE TIC. A.S. is recorded as ISM manager for FERICEK (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for FERICEK?
- Voydar has no matched sanctions record displayed for FERICEK 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 FERICEK. 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
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/9125267Cite this page
FERICEK. Voydar (voydar.com). https://www.voydar.com/vessel/9125267-fericek. Retrieved November 17, 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 includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.