Longstone
Ro-ro ship · Netherlands · built 2019 · AIS Class A
In short
Longstone (Ro-ro ship, Netherlands flag) was last seen on AIS on , not moving, near Gravesend (North Sea). Its crew-entered AIS destination is BEZEE -> GBTIL, with an ETA of Oct 2, 2026, 05:00 UTC; its reported draught is 6.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 04:27 UTC). Registered owner: SY RORO 2Pte. Ltd (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from Gravesend (departed Oct 1, 2026, 09:37 UTC) to BEZEE -> GBTIL
- Vessel type
- Ro-ro ship
- Flag
- Netherlands
- Year built
- 2019
- Gross tonnage
- 32,770
- Size (length × beam)
- 210 m × 26 m
- Registered owner
- SY RORO 2Pte. Ltd
Watch this ship
Get an email when Longstone 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 Longstone.
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
- 51.4515° N, 0.3827° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0.2 kn
- Course
- 77°
- Heading
- 267°
Last 30 days: at least 12 port calls (Gravesend and Zeebrugge).
Port calls are detected by Voydar 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
- Longstone
- IMO numberWhat is an IMO number?
- 9848479
- MMSIWhat is an MMSI?
- 246091000
- Call signWhat is a call sign?
- PDRG
- Flag
- Netherlands
- Vessel type
- Detailed type from WikidataRo-ro ship
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 32,770
- Deadweight (DWT)
- Source: Wikidata, record Q104380061. Added to Voydar on September 23, 2026. Licence: CC0 1.0.11,000 t
- Length overall
- 209.7 m
- Beam
- 26 m
- Year built
- 2019
NetherlandsA 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.
- Registered owner
- SY RORO 2Pte. Ltd(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · confidence 0.9 · retrieved Sep 28, 2026Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · confidence 0.9 · retrieved Sep 28, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026FLENSBURGER SCHIFFSBAU GMBH(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
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 GravesendAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at GravesendAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ZeebruggeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ZeebruggeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left GravesendAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at GravesendAIS-detected | Voydar port-call detector (AIS geofence) | |
| ISM manager: P&O Ferries Holdings Ltd (previously SIEM Ship Management) | Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions) |
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 | 26,739 t | 8,575 t | 148 days | 449 kg |
| 2020 | 36,824 t | 11,805 t | 204 days | 483 kg |
| 2021 | 34,627 t | 11,097 t | 189 days | 491 kg |
| 2022 | 28,938 t | 9,271 t | 194 days | 434 kg |
| 2023 | 30,841 t | 9,877 t | 195 days | 452 kg |
| 2024 | 25,469 t | 8,152 t | 164 days | 444 kg |
| 2025 | 28,064 t | 8,989 t | 187 days | 414 kg |
Technical efficiency: EEXI (11.9 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
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 |
|---|---|---|---|
| Gravesend GBGVS | Oct 1, 2026, 04:44 UTC | Oct 1, 2026, 09:37 UTC | 4 h 53 min |
| Zeebrugge BEZEE | Sep 30, 2026, 16:46 UTC | Sep 30, 2026, 21:51 UTC | 5 h 5 min |
| Gravesend GBGVS | Sep 30, 2026, 04:33 UTC | Sep 30, 2026, 09:47 UTC | 5 h 14 min |
| Zeebrugge BEZEE | Sep 29, 2026, 16:45 UTC | Sep 29, 2026, 21:18 UTC | 4 h 33 min |
| Zeebrugge BEZEE | Sep 28, 2026, 16:50 UTC | Sep 28, 2026, 21:32 UTC | 4 h 43 min |
| Gravesend GBGVS | Sep 28, 2026, 04:40 UTC | Sep 28, 2026, 09:14 UTC | 4 h 33 min |
| Gravesend GBGVS | Sep 26, 2026, 04:41 UTC | Sep 26, 2026, 10:01 UTC | 5 h 20 min |
| Zeebrugge BEZEE | Sep 25, 2026, 16:47 UTC | Sep 25, 2026, 22:07 UTC | 5 h 20 min |
| Gravesend GBGVS | Sep 25, 2026, 04:35 UTC | Sep 25, 2026, 09:32 UTC | 4 h 57 min |
| Zeebrugge BEZEE | Sep 24, 2026, 16:42 UTC | Sep 24, 2026, 21:01 UTC | 4 h 19 min |
| Gravesend GBGVS | Sep 24, 2026, 04:37 UTC | Sep 24, 2026, 09:01 UTC | 4 h 24 min |
| Zeebrugge BEZEE | Sep 23, 2026, 16:45 UTC | Sep 23, 2026, 21:40 UTC | 4 h 54 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.
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 |
|---|---|---|
| Oct 1, 2026, 21:52 UTC | Draught change Reported draught went from 5.8 m to 6.8 m after leaving Gravesend. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 30, 2026, 09:14 UTC | Draught change Reported draught went from 6.9 m to 5.9 m while in port at Gravesend. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 29, 2026, 21:04 UTC | Draught change Reported draught went from 6 m to 6.9 m while in port at Zeebrugge. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 29, 2026, 09:58 UTC | Draught change Reported draught went from 6.8 m to 6 m after leaving Zeebrugge. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 28, 2026, 21:12 UTC | Draught change Reported draught went from 5.7 m to 6.8 m while in port at Zeebrugge. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 28, 2026, 09:25 UTC | Draught change Reported draught went from 6.4 m to 5.7 m after leaving Gravesend. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 27, 2026, 09:15 UTC | Draught change Reported draught went from 6.8 m to 5.6 m after leaving Gravesend. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 26, 2026, 20:31 UTC | Draught change Reported draught went from 5.8 m to 6.8 m after leaving Gravesend. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 26, 2026, 09:42 UTC | Draught change Reported draught went from 6.9 m to 5.8 m while in port at Gravesend. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 21:53 UTC | Draught change Reported draught went from 6.1 m to 6.9 m while in port at Zeebrugge. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 09:02 UTC | Draught change Reported draught went from 6.9 m to 6.1 m while in port at Gravesend. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 24, 2026, 20:25 UTC | Draught change Reported draught went from 5.6 m to 6.9 m while in port at Zeebrugge. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 24, 2026, 09:29 UTC | Draught change Reported draught went from 6.8 m to 5.6 m after leaving Gravesend. Voydar infers the ship probably discharged 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
- Where is Longstone now?
- Longstone (Ro-ro ship, Netherlands flag) was last seen on AIS on Oct 2, 2026, 04:50 UTC, not moving, near Gravesend (North Sea). The crew-entered destination was BEZEE -> GBTIL (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 04:27 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Longstone?
- Longstone is a ro-ro ship sailing under the flag of Netherlands, built in 2019 by Flensburger Schiffbau-Gesellschaft. The vessel is 209.7 m long with a beam of 26 m and has a gross tonnage of 32,770.
- Who is recorded as the owner or manager of Longstone?
- SY RORO 2Pte. Ltd is recorded as Registered owner for Longstone (source: ILT — Nederlands vlagregister (Netherlands flag register data)). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Longstone?
- Voydar has no matched sanctions record displayed for Longstone 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 Longstone. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by Flensburger Schiffbau-Gesellschaft, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- ACACIA SEAWAYSIMO 9809112Ro-ro ship · built 2017 · 32,770 GT
- FadiqIMO 9809590Ro-ro ship · built 2017 · 32,770 GT
- Tulipa SeawaysIMO 9809100Ro-ro ship · built 2017 · 32,336 GT
- ULUSOY-16IMO 9809095Ro-ro ship · built 2017 · 32,336 GT
- LismoreIMO 9848467Ro-ro ship · built 2018 · 32,770 GT
- LeevstenIMO 9869954Ro-ro ship · built 2019 · 32,887 GT
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9848479Using 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.