IMO 9424649
The vessel TOKYO was selected as Vessel Spotlight due to its ranking of #14 among 3,267 monitored vessels, with key metrics over the past 90 days including 13 STS proximity events, 6 AIS gaps, 147 loitering events, and 383 zone dwell events. The top operating zones included the Eastern Mediterranean Surveillance Zone, osint_cyprus_south_sts, Danish Straits/Skagerrak, Bosphorus/Dardanelles Approach, and Istanbul Black Sea Surveillance Zone. Data indicated that the vessel was detected in the vicinity of terminal zones, but no direct terminal visits were recorded during this period. These observations are based on AIS-derived behavioral indicators.
Vessel information
Movement & AIS Track
The vessel TOKYO was detected in the Eastern Mediterranean Surveillance Zone most frequently, with a total of 329 events, including 182 zone dwell events, 130 loiter events, and 16 STS proximity events. Additional notable detections occurred in the osint_cyprus_south_sts zone (71 events) and the Danish Straits/Skagerrak zone (70 events). The vessel was detected in the vicinity of various terminal zones; however, no direct terminal visits were recorded during this period.
| Zone | Events | Types | First Seen | Last Seen |
|---|---|---|---|---|
| Eastern Mediterranean Surveillance Zone | 329 | zone_dwell: 182, loiter: 130, sts: 16, ais_gap: 1 | Jul 23, 2026 | Aug 1, 2026 |
| osint_cyprus_south_sts | 71 | zone_dwell: 62, loiter: 9 | Jan 28, 2026 | Feb 1, 2026 |
| Danish Straits/Skagerrak | 70 | zone_dwell: 54, loiter: 16 | Mar 13, 2026 | Jun 16, 2026 |
| Bosphorus/Dardanelles Approach | 57 | zone_dwell: 40, loiter: 17 | Jan 26, 2026 | Jul 19, 2026 |
| Istanbul Black Sea Surveillance Zone | 42 | zone_dwell: 32, loiter: 10 | Feb 1, 2026 | Feb 4, 2026 |
| discovered_002 | 25 | zone_dwell: 25 | Mar 12, 2026 | Jun 18, 2026 |
| Southern Öresund Surveillance Zone | 20 | zone_dwell: 20 | Mar 15, 2026 | Jul 3, 2026 |
| Baltic Exit/Tallinn Approach | 18 | zone_dwell: 18 | Mar 16, 2026 | Jun 13, 2026 |
| Alboran Sea Surveillance Zone | 16 | zone_dwell: 15, ais_gap: 1 | Mar 11, 2026 | Jun 15, 2026 |
| Archipelago Sea Surveillance Zone | 12 | zone_dwell: 12 | Jun 8, 2026 | Jun 13, 2026 |
| Barents Sea Surveillance Zone | 10 | zone_dwell: 10 | Jun 4, 2026 | Jun 18, 2026 |
| Atlantic Midway Monitoring Zone | 9 | zone_dwell: 9 | Mar 12, 2026 | Mar 27, 2026 |
| English Channel Surveillance Zone | 8 | zone_dwell: 8 | Mar 16, 2026 | Jun 7, 2026 |
| discovered_027 | 7 | zone_dwell: 7 | Jun 6, 2026 | Jun 16, 2026 |
| Crimean Peninsula Surveillance Zone | 7 | zone_dwell: 7 | Mar 13, 2026 | Mar 26, 2026 |
STS Proximity Partners
The vessel TOKYO recorded a total of 13 STS proximity detections involving 2 distinct partner vessels. The most frequent partner was the vessel TOKYO itself, detected in proximity 11 times, followed by E PIONEER, which was detected in proximity 5 times. Both partner vessels are not sanctioned.
Ownership & Management
Sea Trade Marine SA is a Greek ship management company based in Voula, Athens, and appears to provide commercial and technical management services for a tanker/bulk carrier fleet. Public company-directory sources describe it as a ship management firm with offices in the southern suburbs of Athens and a long-standing maritime services presence.[1][2][12][15]
⚠ Red Flags
- Multiple maritime directory records use the same Voula address, indicating a shared-office environment.[2][3][5][6][12]
- One source shows the company is linked to vessel management for POLLUX and another source ties the same address to a different vessel company, which suggests a common management-office structure rather than a unique operating site.[8][9]
- Corporate structure and beneficial ownership are not visible in the provided sources.[12][19]
Classification & Safety
Disclaimer
This vessel profile is compiled from publicly available information sources including maritime databases, government sanctions lists, and AIS position data. Information may be incomplete, delayed, or contain inaccuracies.
This content is for informational purposes only and does not constitute legal, financial, or compliance advice. FleetLeaks makes no warranties regarding the accuracy or completeness of the information presented. Users should independently verify all information before making decisions.
Data Scope & Currency
This dossier reflects automated analysis of publicly available data sources as of August 7, 2026 (UTC). FleetLeaks does not assert intent or wrongdoing. Observations are derived from AIS behavioral signals, registry records, and other open sources, each subject to inherent latency and reporting limitations.
Data Refresh
This dossier can be re-generated using the same automated pipeline with the most current available data. A refresh re-executes the standard selection, enrichment, and analysis process and does not alter methodology or thresholds. To request a refreshed version of this dossier, please contact us. A nominal fee may apply to cover compute and data access costs.
Generated: 2026-08-07T10:03:43.939751Z