Skip to content

SIRIUS

Tug · United States · AIS Class A

IMONo IMOMMSI367181040Call signWDM8810Last AIS position Oct 6, 2026, 17:18 UTC

In short

SIRIUS (Tug, United States flag) was last seen on AIS on , under way at 5.2 kn, near Edgartown (North Atlantic Ocean). Its crew-entered AIS destination is NEW BEDFORD; its reported draught is 1.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 16:42 UTC). Managing owner (USCG): TISBURY TOWING & TRANSPORTATION CO INC (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)).

Current voyage: from New Bedford (departed Oct 6, 2026, 14:48 UTC) to NEW BEDFORD

Vessel type
Tug
Year built
—
Gross tonnage
—
Size (length × beam)
—
Managing owner (USCG)
TISBURY TOWING & TRANSPORTATION CO INC

Watch this ship

Get an email when SIRIUS arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position

received
Position
41.4925° N, 70.6118° W
Area
North Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
5.2 kn
Course
120°
Heading
109°
41.4925° N, 70.6118° W
Open the full live map →

Last 30 days: 1 port call (New Bedford).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Pro shows SIRIUS's track before the last 30 days. Voydar has recorded its port calls since June 15, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
SIRIUS
MMSIWhat is an MMSI?
367181040
Call signWhat is a call sign?
WDM8810
Vessel type
Tug
AIS ship type
Towing
Length overall
—
Beam
—
Year built
—

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.

Managing owner (USCG)
TISBURY TOWING & TRANSPORTATION CO INC(not linked to a company record)
Source: US Coast Guard — Merchant Vessels of the United States (documented vessels) · reported · confidence 0.9 · retrieved Oct 6, 2026Coast Guard documentation record (2026-09 file) matched to this ship by call sign and vessel name. The managing owner is the company the Coast Guard has on record for the ship's certificate of documentation.
Ship radio licensee (FCC)
Tisbury Towing and Transportation(not linked to a company record)
Source: FCC Universal Licensing System — ship station licences · since 2022 · reported · confidence 0.9 · retrieved Oct 6, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.

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.

DateEventSource
Left New BedfordAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at New BedfordAIS-detectedVoydar port-call detector (AIS geofence)
Left New BedfordAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at New BedfordAIS-detectedVoydar port-call detector (AIS geofence)
Left New BedfordAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at New BedfordAIS-detectedVoydar 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.

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

PortArrivedDepartedTime in port
New Bedford USNBDOct 6, 2026, 09:36 UTCOct 6, 2026, 14:48 UTC5 h 11 min
New Bedford USNBDJun 15, 2026, 17:32 UTCJun 19, 2026, 05:39 UTC3 d 12 h
New Bedford USNBDJun 15, 2026, 16:29 UTCJun 15, 2026, 17:21 UTC52 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.

Frequently asked questions

Where is SIRIUS now?
SIRIUS (Tug, United States flag) was last seen on AIS on Oct 6, 2026, 17:18 UTC, under way at 5.2 kn, near Edgartown (North Atlantic Ocean). The crew-entered destination was NEW BEDFORD (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 16:42 UTC). This report does not confirm the ship’s current route.
What kind of ship is SIRIUS?
SIRIUS is a tug sailing under the flag of United States.
Who is recorded as the owner or manager of SIRIUS?
TISBURY TOWING & TRANSPORTATION CO INC is recorded as Managing owner (USCG) for SIRIUS (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for SIRIUS?
Voydar has no matched sanctions record displayed for SIRIUS 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 SIRIUS. 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/mmsi-367181040
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

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.

See plans