Chattanooga
Container ship · Singapore · built 2012 · AIS Class A
In short
Chattanooga (Container ship, Singapore flag) was last seen on AIS on , moored, in the port of Haifa. Its crew-entered AIS destination is ILASH>ILHFA; its reported draught is 7.8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 13:14 UTC). It arrived there on Nov 15, 2026, 07:34 UTC. ISM manager: Papay Shipping Pte. Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Container ship
- Flag
- Singapore
- Year built
- 2012
- Gross tonnage
- 9,743
- Size (length × beam)
- 143 m × 23 m
- ISM manager
- Papay Shipping Pte. Ltd.
Last reported position: 32.8165° N, 35.0112° E · Mediterranean Sea · See on the map
Watch this ship
Get an email when Chattanooga 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, 15:05 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Chattanooga 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
- 32.8165° N, 35.0112° E
- Area
- Mediterranean Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 0°
- Heading
- 349°
- Compass: course over ground 0°, heading 349°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 9 port calls (Haifa, Ashdod, and Piraeus).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Chattanooga's track before the last 30 days. Voydar has recorded its port calls since October 7, 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 143.2 mone tick every 25 m
Beam 22.8 mPlan outline, to scale
- Name
- Chattanooga
- IMO numberWhat is an IMO number?
- 9611034
- MMSIWhat is an MMSI?
- 563004400
- Call signWhat is a call sign?
- 9V5025
- Flag
- Singapore
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 9,743
- Deadweight (DWT)
- Source: Wikidata, record Q84262781. Added to Voydar on October 23, 2026. Licence: CC0 1.0.12,580 t
- Length overall
- 143.2 m
- Beam
- 22.8 m
- Year built
- 2012
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 |
|---|---|---|
| Arrived at HaifaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AshdodAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AshdodAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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 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 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) |
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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred May 14, 2015衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)広島県呉市斎島南方沖 来島梶取鼻灯台から真方位242°5.1海里付近
コンテナ船CHATTANOOGAケミカルタンカーSTO IRIS衝突Report published Jan 28, 2016
コンテナ船CHATTANOOGAは、漂泊中、また、ケミカルタンカーSTO IRISは、南西進中、両船が衝突した。 CHATTANOOGAは、左舷外板に凹損等を生じ、また、STO IRISは、右舷船首部に凹損等を生じた。
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典:運輸安全委員会「船舶事故等調査報告書」(https://jtsb.mlit.go.jp/)。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
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 |
|---|---|---|---|---|
| 2024 | 8,217 t | 2,605 t | 166 days | 190 kg |
| 2025 | 6,466 t | 2,045 t | 140 days | 203 kg |
Technical efficiency: EEXI (23.4 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 “Container ship”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile33.13 g per tonne-nautical mile
- Lowest reportedHighest reported
78% of the 2,233 ships in this group reported a lower figure.
Group: lower quartile 9.85 · median 16.45 · upper quartile 29.35
- CO₂ per nautical mile sailed203 kg per nautical mile
- Lowest reportedHighest reported
3% of the 2,256 ships in this group reported a lower figure.
Group: lower quartile 313.5 · median 541.9 · upper quartile 768.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 |
|---|---|---|---|
| Haifa ILHFA | Nov 15, 2026, 07:34 UTC | in port | — |
| Ashdod ILASH | Nov 14, 2026, 09:08 UTC | Nov 14, 2026, 23:24 UTC | 14 h 15 min |
| Piraeus GRPIR | Nov 10, 2026, 17:51 UTC | Nov 12, 2026, 00:27 UTC | 30 h 36 min |
| Haifa ILHFA | Nov 6, 2026, 08:03 UTC | Nov 6, 2026, 12:31 UTC | 4 h 28 min |
| Haifa ILHFA | Nov 5, 2026, 17:20 UTC | Nov 6, 2026, 07:26 UTC | 14 h 6 min |
| Ashdod ILASH | Nov 4, 2026, 09:53 UTC | Nov 5, 2026, 07:40 UTC | 21 h 47 min |
| Piraeus GRPIR | Oct 29, 2026, 18:05 UTC | Oct 31, 2026, 21:54 UTC | 2 d 3 h |
| Ashdod ILASH | Oct 22, 2026, 07:22 UTC | Oct 22, 2026, 20:12 UTC | 12 h 51 min |
| Haifa ILHFA | Oct 21, 2026, 11:30 UTC | Oct 21, 2026, 18:06 UTC | 6 h 36 min |
| Piraeus GRPIR | Oct 17, 2026, 11:14 UTC | Oct 21, 2026, 05:08 UTC | 3 d 17 h |
| Abu Alandah JODAH | Oct 7, 2026, 15:30 UTC | Oct 7, 2026, 16:31 UTC | 1 h 1 min |
| Haifa ILHFA | Oct 7, 2026, 08:54 UTC | Oct 7, 2026, 13:53 UTC | 4 h 59 min |
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 24, 2022, 20:54 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | May 8, 2022, 20:48 UTC | KC8 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Apr 21, 2022, 23:06 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 5, 2022, 18:49 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Mar 25, 2022, 09:07 UTC | NWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 21, 2022, 01:09 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Mar 8, 2022, 07:33 UTC | KC4 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Feb 27, 2022, 08:53 UTC | KC6 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 13, 2022, 00:32 UTC | TSK | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Feb 7, 2022, 11:43 UTC | KC4 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jan 20, 2022, 20:25 UTC | KC4 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jan 14, 2022, 08:30 UTC | WA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: October 3, 2020.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 11, 2026, 22:51 UTC | Draught change Reported draught went from 6.4 m to 8.6 m while in port at Piraeus. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 6, 2026, 10:11 UTC | Draught change Reported draught went from 8.3 m to 7.3 m while in port at Haifa. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 23, 2026, 00:09 UTC | Draught change Reported draught went from 8.8 m to 8.2 m after leaving Ashdod. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 21, 2026, 05:50 UTC | Draught change Reported draught went from 7.2 m to 9.1 m after leaving Piraeus. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
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 Chattanooga?
- Chattanooga is a container ship sailing under the flag of Singapore, built in 2012 by Taizhou Kouan Shipbuilding Co Ltd. The vessel is 143.2 m long with a beam of 22.8 m and has a gross tonnage of 9,743.
- Who is recorded as the owner or manager of Chattanooga?
- Papay Shipping Pte. Ltd. is recorded as ISM manager for Chattanooga (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 Chattanooga?
- Voydar has no matched sanctions record displayed for Chattanooga 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 Chattanooga. 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 Container ships
Other container ships with full Voydar profiles. A different set each day. All container ships
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/9611034Cite this page
Chattanooga. Voydar (voydar.com). https://www.voydar.com/vessel/9611034-chattanooga. 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.