Where is AMATZIA II now?

AMATZIA II (Tug, Israel flag) was last seen on AIS on Oct 6, 2026, 14:50 UTC, moored, near Haifa (Mediterranean Sea). The crew-entered destination was HAIFA (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 13:54 UTC). This report does not confirm the ship’s current route.

What kind of ship is AMATZIA II?

AMATZIA II is a tug sailing under the flag of Israel.

What sanctions and inspection records does Voydar hold for AMATZIA II?

Voydar has no matched sanctions record displayed for AMATZIA II 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 AMATZIA II. Missing records do not establish whether the ship has been detained.

AMATZIA II

Tug · Israel · AIS Class A

IMO9279252MMSI428007000Call sign4XJRLast AIS position Oct 6, 2026, 14:50 UTC

Open in Terminal

In short

AMATZIA II (Tug, Israel flag) was last seen on AIS on Oct 6, 2026, 14:50 UTC, moored, near Haifa (Mediterranean Sea). Its crew-entered AIS destination is HAIFA (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 13:54 UTC).

Current voyage: from Haifa Bayport (departed Sep 22, 2026, 10:42 UTC) to HAIFA

Vessel type: Tug
Flag: Israel
Year built: —
Gross tonnage: —
Size (length × beam): —
Registered owner: —

Watch this ship

Get an email when AMATZIA II 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 Oct 6, 2026, 14:50 UTC

Position: 32.8221° N, 35.0111° E
Area: Mediterranean Sea
StatusWhat do AIS statuses mean?: Moored
Speed: 0.8 kn
Course: 193°
Heading: —

32.8221° N, 35.0111° E

Open the full live map →

Last 30 days: 11 port calls (Haifa Bayport).

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

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

Try the live demo, no sign-up

Identity & particulars

Name: AMATZIA II
IMO numberWhat is an IMO number?: 9279252
MMSIWhat is an MMSI?: 428007000
Call signWhat is a call sign?: 4XJR
Flag: Israel
Vessel type: Tug
Gross tonnageGross tonnage vs deadweight: —
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.

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.

Date	Event	Source
Sep 22, 2026, 10:42 UTC	Left Haifa BayportAIS-detected	Voydar port-call detector (AIS geofence)
Sep 21, 2026, 22:58 UTC	Arrived at Haifa BayportAIS-detected	Voydar port-call detector (AIS geofence)
Sep 20, 2026, 11:16 UTC	Left Haifa BayportAIS-detected	Voydar port-call detector (AIS geofence)
Sep 20, 2026, 03:28 UTC	Arrived at Haifa BayportAIS-detected	Voydar port-call detector (AIS geofence)
Sep 20, 2026, 03:24 UTC	Left Haifa BayportAIS-detected	Voydar port-call detector (AIS geofence)
Sep 19, 2026, 15:15 UTC	Arrived at Haifa BayportAIS-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.

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
Haifa Bayport ILHBT	Sep 21, 2026, 22:58 UTC	Sep 22, 2026, 10:42 UTC	11 h 44 min
Haifa Bayport ILHBT	Sep 20, 2026, 03:28 UTC	Sep 20, 2026, 11:16 UTC	7 h 48 min
Haifa Bayport ILHBT	Sep 19, 2026, 15:15 UTC	Sep 20, 2026, 03:24 UTC	12 h 9 min
Haifa Bayport ILHBT	Sep 18, 2026, 02:23 UTC	Sep 18, 2026, 03:17 UTC	54 min
Haifa Bayport ILHBT	Sep 16, 2026, 04:01 UTC	Sep 16, 2026, 10:33 UTC	6 h 33 min
Haifa Bayport ILHBT	Sep 14, 2026, 23:22 UTC	Sep 15, 2026, 02:31 UTC	3 h 9 min
Haifa Bayport ILHBT	Sep 14, 2026, 07:01 UTC	Sep 14, 2026, 15:19 UTC	8 h 19 min
Haifa Bayport ILHBT	Sep 13, 2026, 22:47 UTC	Sep 13, 2026, 23:19 UTC	32 min
Haifa Bayport ILHBT	Sep 12, 2026, 07:36 UTC	Sep 12, 2026, 13:19 UTC	5 h 43 min
Haifa Bayport ILHBT	Sep 10, 2026, 01:25 UTC	Sep 10, 2026, 02:37 UTC	1 h 11 min
Haifa Bayport ILHBT	Sep 9, 2026, 19:08 UTC	Sep 9, 2026, 21:12 UTC	2 h 4 min
Haifa Bayport ILHBT	Sep 1, 2026, 20:36 UTC	Sep 2, 2026, 21:39 UTC	25 h 3 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
Sep 23, 2026, 10:04 UTC	Position jump Reported position moved 154 km in 4 min, faster than any ship can travel. The broadcast position was wrong for a time; GNSS interference, equipment faults and manipulation are all possible causes. 13 other ships were shown at the same place at the same time, which points to area-wide GNSS interference. Method seadar.behaviour.position_jump v1	Medium (65%)

When

What we observed

Confidence

Sep 23, 2026, 10:04 UTC

Position jump

Reported position moved 154 km in 4 min, faster than any ship can travel. The broadcast position was wrong for a time; GNSS interference, equipment faults and manipulation are all possible causes.

13 other ships were shown at the same place at the same time, which points to area-wide GNSS interference.

Method seadar.behaviour.position_jump v1

Medium (65%)

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.

How these are computed →

Frequently asked questions

Where is AMATZIA II now?: AMATZIA II (Tug, Israel flag) was last seen on AIS on Oct 6, 2026, 14:50 UTC, moored, near Haifa (Mediterranean Sea). The crew-entered destination was HAIFA (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 13:54 UTC). This report does not confirm the ship’s current route.
What kind of ship is AMATZIA II?: AMATZIA II is a tug sailing under the flag of Israel.
What sanctions and inspection records does Voydar hold for AMATZIA II?: Voydar has no matched sanctions record displayed for AMATZIA II 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 AMATZIA II. 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/9279252

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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