BASTO ELECTRIC
Ferry · Norway · built 2020 · AIS Class A
In short
BASTO ELECTRIC (Ferry, Norway flag) was last seen on AIS on , not moving, in the Baltic Sea. Its crew-entered AIS destination is NO MSS>NO HOR; its reported draught is 3.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 20:23 UTC). Its last detected port call was at Moss: arrived Oct 4, 2026, left Oct 4, 2026. ISM manager: Torghatten Sør AS (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025). It can carry up to 600 passengers (source: Wikidata).
- Vessel type
- Ferry
- Flag
- Norway
- Year built
- 2020
- Gross tonnage
- 7,911
- Size (length × beam)
- 143 m × 21 m
- ISM manager
- Torghatten Sør AS
Watch this ship
Get an email when BASTO ELECTRIC 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 BASTO ELECTRIC.
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
- 59.4112° N, 10.4897° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- 206°
- Heading
- 148°
Last 30 days: at least 12 port calls (Moss and Borre).
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
- BASTO ELECTRIC
- IMO numberWhat is an IMO number?
- 9878993
- MMSIWhat is an MMSI?
- 257122880
- Call signWhat is a call sign?
- LFVD
- Flag
- Norway
- Vessel type
- Detailed type from WikidataFerry
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 7,911
- Net tonnage
- 2,395
- Deadweight (DWT)
- Source: Wikidata, record Q106307145. Added to Voydar on September 23, 2026. Licence: CC0 1.0.1,350 t
- Length overall
- 143.2 m
- Beam
- 20.7 m
- Year built
- 2020
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.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 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 MossAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MossAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BorreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BorreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left MossAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MossAIS-detected | Voydar port-call detector (AIS geofence) |
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 |
|---|---|---|---|---|
| 2021 | 3,215 t | 1,003 t | 139 days | 91 kg |
| 2022 | 3,067 t | 957 t | 178 days | 64 kg |
| 2023 | 1,255 t | 391 t | 188 days | 26 kg |
| 2024 | 2,207 t | 688 t | 183 days | 47 kg |
| 2025 | 1,846 t | 576 t | 183 days | 40 kg |
Technical efficiency: Not Applicable. 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 |
|---|---|---|---|
| Moss NOMSS | Oct 4, 2026, 19:46 UTC | Oct 4, 2026, 20:24 UTC | 38 min |
| Borre NOBRR | Oct 4, 2026, 18:57 UTC | Oct 4, 2026, 19:38 UTC | 40 min |
| Moss NOMSS | Oct 4, 2026, 18:16 UTC | Oct 4, 2026, 18:51 UTC | 35 min |
| Borre NOBRR | Oct 4, 2026, 17:30 UTC | Oct 4, 2026, 18:07 UTC | 37 min |
| Moss NOMSS | Oct 4, 2026, 16:46 UTC | Oct 4, 2026, 17:23 UTC | 37 min |
| Borre NOBRR | Oct 4, 2026, 15:59 UTC | Oct 4, 2026, 16:38 UTC | 39 min |
| Borre NOBRR | Oct 4, 2026, 14:30 UTC | Oct 4, 2026, 15:07 UTC | 37 min |
| Moss NOMSS | Oct 4, 2026, 13:45 UTC | Oct 4, 2026, 14:23 UTC | 38 min |
| Borre NOBRR | Oct 4, 2026, 13:00 UTC | Oct 4, 2026, 13:37 UTC | 37 min |
| Moss NOMSS | Oct 4, 2026, 12:16 UTC | Oct 4, 2026, 12:53 UTC | 37 min |
| Borre NOBRR | Oct 4, 2026, 11:29 UTC | Oct 4, 2026, 12:07 UTC | 39 min |
| Moss NOMSS | Oct 4, 2026, 10:45 UTC | Oct 4, 2026, 11:23 UTC | 38 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.
Predicted arrival
Voydar estimates arrival at Horten around Oct 5, 2026, 05:04 UTC, most likely between Oct 4, 2026, 18:58 UTC and Oct 11, 2026, 03:03 UTC. Based on 74 past transits between NOMSS and Horten seen in our port calls. The crew-reported ETA is Aug 15, 2027, 22:22 UTC.
Medium (56%) · Method seadar.behaviour.eta_prediction v1
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 BASTO ELECTRIC now?
- BASTO ELECTRIC (Ferry, Norway flag) was last seen on AIS on Oct 4, 2026, 20:34 UTC, not moving, in the Baltic Sea. The crew-entered destination was NO MSS>NO HOR (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 20:23 UTC). This report does not confirm the ship’s current route.
- What kind of ship is BASTO ELECTRIC?
- BASTO ELECTRIC is a ferry sailing under the flag of Norway, built in 2020 by Sefine Shipyard. The vessel is 143.2 m long with a beam of 20.7 m and has a gross tonnage of 7,911.
- Who is recorded as the owner or manager of BASTO ELECTRIC?
- Torghatten Sør AS is recorded as ISM manager for BASTO ELECTRIC (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 BASTO ELECTRIC?
- Voydar has no matched sanctions record displayed for BASTO ELECTRIC 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 BASTO ELECTRIC. Missing records do not establish whether the ship has been detained.
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/9878993Using 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.