Where is IVS Shikra now?

Voydar has no displayable AIS position for IVS Shikra in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.

What kind of ship is IVS Shikra?

IVS Shikra is a ship, built in 2008 by Shikoku Dockyard. The vessel is 170.7 m long and has a gross tonnage of 17,979.

What sanctions and inspection records does Voydar hold for IVS Shikra?

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

IVS Shikra

ship · built 2008

IMO9370329No AIS position on record

Open in Terminal

In short

IVS Shikra (ship) has no AIS position on record with Voydar.

Vessel type: ship
Flag: —
Year built: 2008
Gross tonnage: 17,979
Size (length × beam): 171 m
Registered owner: —

Watch this ship

IVS Shikra 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

No AIS position on record for this vessel. Identity and particulars are 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: IVS Shikra
IMO numberWhat is an IMO number?: 9370329
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: ship
Gross tonnageGross tonnage vs deadweight: 17,979
Length overall: 170.7 m
Beam: —
Year built: 2008

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.

Builder: Shikoku Dockyard
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.

Date	Event	Source
Aug 30, 2016	Reported departure from Corpus ChristiAuthority-reported	USACE foreign traffic vessel entrances & clearances
Aug 26, 2016	Reported arrival at Corpus ChristiAuthority-reported	USACE foreign traffic vessel entrances & clearances
Aug 17, 2016	Reported departure from Port ArthurAuthority-reported	USACE foreign traffic vessel entrances & clearances

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.

Reported by authorities Authority-reported

Port	Record	Date (UTC)	Berth	Source
Corpus Christi USCRP	Departure	Aug 30, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRP	Arrival	Aug 26, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Port Arthur USPOA	Departure	Aug 17, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Port Arthur USPOA	Arrival	Aug 15, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Departure	Aug 13, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Departure	Aug 6, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Arrival	Aug 4, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Savannah USSAV	Departure	Apr 8, 2014(date only)	—	USACE foreign traffic vessel entrances & clearances
Savannah USSAV	Arrival	Mar 31, 2014(date only)	—	USACE foreign traffic vessel entrances & clearances
Astoria USAST	Departure	Jun 12, 2013(date only)	—	USACE foreign traffic vessel entrances & clearances
Astoria USAST	Arrival	Jun 6, 2013(date only)	—	USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)	Departure	Apr 6, 2013(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: February 4, 2009.

Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.

Frequently asked questions

Where is IVS Shikra now?: Voydar has no displayable AIS position for IVS Shikra in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is IVS Shikra?: IVS Shikra is a ship, built in 2008 by Shikoku Dockyard. The vessel is 170.7 m long and has a gross tonnage of 17,979.
What sanctions and inspection records does Voydar hold for IVS Shikra?: Voydar has no matched sanctions record displayed for IVS Shikra 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 IVS Shikra. 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/9370329

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