Skip to content

SEAPEAK GLASGOW

LNG carrier · Bahamas · built 2018 · AIS Class A

IMO9781918MMSI311000665Call signC6DG2Last AIS position Oct 3, 2026, 06:03 UTC

In short

SEAPEAK GLASGOW (LNG carrier, Bahamas flag) was last seen on AIS on , under way at 13.6 kn, in the Caribbean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is FOR ORDERS, with an ETA of Oct 16, 2026, 00:01 UTC; its reported draught is 9.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 04:57 UTC). ISM manager: Seapeak Maritime Limited (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Vessel type
LNG carrier
Year built
2018
Gross tonnage
117,162
Size (length × beam)
294 m × 48 m

Watch this ship

SEAPEAK GLASGOW has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

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

Last reported position

received
Position
10.8183° N, 61.7389° W
Area
Caribbean Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
13.6 kn
Course
3°
Heading
357°
10.8183° N, 61.7389° W
Open the full live map →

Voydar detected no port call in the last 30 days.

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
SEAPEAK GLASGOW
IMO numberWhat is an IMO number?
9781918
MMSIWhat is an MMSI?
311000665
Call signWhat is a call sign?
C6DG2
AIS ship type
Tanker (hazardous cat. D)
Gross tonnageGross tonnage vs deadweight
117,162
Length overall
293.9 m
Beam
47.5 m
Year built
2018

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 year 2025 · reported · confidence 0.9 · retrieved Oct 5, 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.

DateEventSource
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong 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.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
201918,023 t6,408 t114 days564 kg
20227,213 t2,476 t29 days617 kg
202310,155 t3,656 t58 days532 kg
202510,681 t3,818 t70 days461 kg

Technical efficiency: EEXI (3.38 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalJun 27, 2020, 14:09 UTCSLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: June 27, 2020.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

Frequently asked questions

Where is SEAPEAK GLASGOW now?
SEAPEAK GLASGOW (LNG carrier, Bahamas flag) was last seen on AIS on Oct 3, 2026, 06:03 UTC, under way at 13.6 kn, in the Caribbean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was FOR ORDERS (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 04:57 UTC). This report does not confirm the ship’s current route.
What kind of ship is SEAPEAK GLASGOW?
SEAPEAK GLASGOW is an LNG carrier sailing under the flag of Bahamas, built in 2018 by HD Hyundai Samho. The vessel is 293.9 m long with a beam of 47.5 m and has a gross tonnage of 117,162.
Who is recorded as the owner or manager of SEAPEAK GLASGOW?
Seapeak Maritime Limited is recorded as ISM manager for SEAPEAK GLASGOW (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for SEAPEAK GLASGOW?
Voydar has no matched sanctions record displayed for SEAPEAK GLASGOW 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 SEAPEAK GLASGOW. 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/9781918
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