MULTI CHALLENGER
Norway · AIS Class A
In short
MULTI CHALLENGER (Other, Norway flag) was last seen on AIS on , moored, in the Baltic Sea. Its crew-entered AIS destination is FISHFARMS / CH16; its reported draught is 3.5 m (voyage report via BarentsWatch AIS API, received Nov 16, 2026, 09:23 UTC).
Current voyage: from Vikna (departed Nov 16, 2026, 08:45 UTC) to FISHFARMS / CH16
- Vessel type
- —
- Flag
- Norway
- Year built
- —
- Gross tonnage
- —
- Size, AIS-reported (length × beam)
- 20 m × 10 m
- Registered owner
- —
Last reported position: 64.972° N, 11.4464° E · Baltic Sea · See on the map
Watch this ship
Get an email when MULTI CHALLENGER arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Following MULTI CHALLENGER over the last 24 hours would have sent 1 message.
- LeftVikna
Detected from AIS, as of Nov 16, 2026, 15:27 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for MULTI CHALLENGER reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
Last reported position
received- Position
- 64.972° N, 11.4464° E
- Area
- Baltic Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0.1 kn
- Course
- 116°
- Heading
- 193°
- Compass: course over ground 116°, heading 193°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 5 port calls (Vikna).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Data delivered by BarentsWatch
Pro shows MULTI CHALLENGER's track before the last 30 days. Voydar has recorded its port calls since September 10, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- MULTI CHALLENGER
- IMO numberWhat is an IMO number?
- 1049534
- MMSIWhat is an MMSI?
- 258031200
- Call signWhat is a call sign?
- JXZC
- Flag
- Norway
- Vessel type
- —
- Gross tonnageGross tonnage vs deadweight
- —
- Length (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via BarentsWatch AIS API on November 16, 2026.20 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via BarentsWatch AIS API on November 16, 2026.10 m
- 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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via BarentsWatch AIS API on November 16, 2026.
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.
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 ViknaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ViknaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ViknaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ViknaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ViknaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ViknaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at BOSTON, Massachusetts | USCG PSIX / CGMIX inspections | |
| Inspection at ROCKLAND, Maine | USCG PSIX / CGMIX inspections | |
| Inspection at ROCKLAND, Maine | USCG PSIX / CGMIX inspections | |
| Inspection at ROCKLAND, Maine | USCG 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
| Date | Type | Port | Findings |
|---|---|---|---|
| Jan 17, 2024 | Vessel Inspection | BOSTON, Massachusetts | clean |
| May 24, 2010 | Boarding | ROCKLAND, Maine | clean |
| Jun 25, 2009 | Boarding | ROCKLAND, Maine | clean |
| May 12, 2002 | Boarding | ROCKLAND, Maine | clean |
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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Vikna NOVKN | Nov 14, 2026, 13:19 UTC | Nov 16, 2026, 08:45 UTC | 43 h 26 min |
| Vikna NOVKN | Nov 13, 2026, 17:53 UTC | Nov 14, 2026, 05:53 UTC | 12 h 0 min |
| Vikna NOVKN | Nov 8, 2026, 20:28 UTC | Nov 9, 2026, 11:28 UTC | 15 h 0 min |
| Vikna NOVKN | Nov 1, 2026, 04:53 UTC | Nov 2, 2026, 10:43 UTC | 29 h 50 min |
| Vikna NOVKN | Oct 23, 2026, 10:51 UTC | Oct 29, 2026, 19:01 UTC | 6 d 8 h |
| Vikna NOVKN | Oct 15, 2026, 01:00 UTC | Oct 15, 2026, 08:48 UTC | 7 h 48 min |
| Gutvik NOGUT | Oct 13, 2026, 09:31 UTC | Oct 13, 2026, 20:20 UTC | 10 h 49 min |
| Vikna NOVKN | Oct 4, 2026, 01:52 UTC | Oct 6, 2026, 07:06 UTC | 2 d 5 h |
| Vikna NOVKN | Sep 29, 2026, 17:30 UTC | Sep 30, 2026, 05:43 UTC | 12 h 13 min |
| Vikna NOVKN | Sep 24, 2026, 14:09 UTC | Sep 25, 2026, 15:07 UTC | 24 h 58 min |
| Rorvik NORVK | Sep 15, 2026, 14:07 UTC | Sep 22, 2026, 10:57 UTC | 6 d 20 h |
| Rorvik NORVK | Sep 10, 2026, 14:06 UTC | Sep 15, 2026, 14:06 UTC | 5 d 0 h |
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
- What kind of ship is MULTI CHALLENGER?
- MULTI CHALLENGER is a other sailing under the flag of Norway.
- What sanctions and inspection records does Voydar hold for MULTI CHALLENGER?
- Voydar has no matched sanctions record displayed for MULTI CHALLENGER 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. MULTI CHALLENGER has 4 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
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/1049534Cite this page
MULTI CHALLENGER. Voydar (voydar.com). https://www.voydar.com/vessel/1049534-multi-challenger. Retrieved November 16, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
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.