Where is B No 255 now?

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

What kind of ship is B No 255?

B No 255 is a ship, built in 1979. The vessel is 137 m long.

What sanctions and inspection records does Voydar hold for B No 255?

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

B No 255

ship · built 1979

IMO8640519No AIS position on record

Open in Terminal

In short

B No 255 (ship) has no AIS position on record with Voydar.

Vessel type: ship
Flag: —
Year built: 1979
Gross tonnage: —
Size (length × beam): 137 m
Registered owner: —

Watch this ship

B No 255 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.

We email you a link and a code. That creates a free account, no password or card, and follows B No 255.

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

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)

Try the live demo, no sign-up

Identity & particulars

Name: B No 255
IMO numberWhat is an IMO number?: 8640519
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: ship
Gross tonnageGross tonnage vs deadweight: —
Length overall: 137 m
Beam: —
Year built: 1979

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
May 6, 2009	Reported arrival at MiamiAuthority-reported	USACE foreign traffic vessel entrances & clearances
May 5, 2009	Reported departure from Port EvergladesAuthority-reported	USACE foreign traffic vessel entrances & clearances
May 5, 2009	Reported arrival at Port EvergladesAuthority-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.

Incidents & investigations Authority-reported

Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.

Occurred Oct 20, 2017ACC · Towing/BargeNTSB marine investigations (CAROL)Port Aransas, TX, USA
B. NO. 255, Port Aransas, TX, USA (NTSB DCA18FM002)Report published Apr 18, 2019
The National Transportation Safety Board determines that the probable cause of the explosion aboard the barge B. No. 255 was the lack of effective maintenance and safety management of the barge by Bouchard Transportation, which resulted in crude oil cargo leaking through a corroded bulkhead into the forepeak void space, forming vapor, and igniting. Contributing to the accident were the ineffective

Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.

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
Miami USMIA	Arrival	May 6, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Port Everglades USPEF	Departure	May 5, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Port Everglades USPEF	Arrival	May 5, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Departure	Apr 25, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 25, 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 B No 255 now?: Voydar has no displayable AIS position for B No 255 in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is B No 255?: B No 255 is a ship, built in 1979. The vessel is 137 m long.
What sanctions and inspection records does Voydar hold for B No 255?: Voydar has no matched sanctions record displayed for B No 255 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 B No 255. 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/8640519

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