Skip to content

KAYMAR

Tug · Canada · built 1973 · AIS Class A

IMO7397737MMSI316003982Call signCZ3627Last AIS position Oct 4, 2026, 05:08 UTC

In short

KAYMAR (Tug, Canada flag) was last seen on AIS on , not moving, near New Westminster (North Pacific Ocean). Its crew-entered AIS destination is LOCAL TOWING; its reported draught is 3.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 14:14 UTC).

Vessel type
Tug
Flag
Canada
Year built
1973
Gross tonnage
146
Size (length × beam)
21 m × 6 m
Registered owner
—

Watch this ship

Get an email when KAYMAR 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 KAYMAR.

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
49.1553° N, 123.0063° W
Area
North Pacific Ocean
Speed
0 kn
Course
260°
Heading
62°
49.1553° N, 123.0063° 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)

Try the live demo, no sign-up

Identity & particulars

Name
KAYMAR
IMO numberWhat is an IMO number?
7397737
MMSIWhat is an MMSI?
316003982
Call signWhat is a call sign?
CZ3627
Flag
Canada
Vessel type
Tug
Length overall
21 m
Beam
6 m

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.

No owner, operator or manager is recorded for this vessel yet.

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
Port State Control inspection at Seattle, WashingtonUSCG PSIX / CGMIX inspections
Reported departure from TacomaAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at TacomaAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from SeattleAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Port State Control inspection at Seattle, WashingtonUSCG PSIX / CGMIX inspections

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.

Safety & inspections

2
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
May 17, 2019Vessel InspectionPSCSeattle, Washingtonclean
Jul 9, 2016Vessel InspectionPSCSeattle, Washingtonclean

Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.

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
Tacoma USTIWDepartureNov 4, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWArrivalNov 4, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEADepartureJul 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEAArrivalJul 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEADepartureJul 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEAArrivalJul 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEADepartureJul 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEAArrivalJul 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWDepartureJul 8, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWArrivalJul 8, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEADepartureJul 5, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEAArrivalJul 5, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: March 2, 2010.

Frequently asked questions

Where is KAYMAR now?
KAYMAR (Tug, Canada flag) was last seen on AIS on Oct 4, 2026, 05:08 UTC, not moving, near New Westminster (North Pacific Ocean). The crew-entered destination was LOCAL TOWING (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 14:14 UTC). This report does not confirm the ship’s current route.
What kind of ship is KAYMAR?
KAYMAR is a tug sailing under the flag of Canada, built in 1973. The vessel is 21 m long with a beam of 6 m and has a gross tonnage of 146.
What sanctions and inspection records does Voydar hold for KAYMAR?
Voydar has no matched sanctions record displayed for KAYMAR 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. KAYMAR has 2 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.

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/7397737
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