BANCROFT 24
Tug · United States · AIS Class B
In short
BANCROFT 24 (Tug, United States flag) was last seen on AIS on , moored, in the port of Philadelphia. Its crew-entered AIS destination is PORTLAND, with an ETA of Nov 19, 2026, 17:00 UTC; its reported draught is 2.5 m (voyage report via AISstream.io global terrestrial AIS, received Nov 20, 2026, 07:40 UTC). It arrived there on Nov 20, 2026, 00:35 UTC. Managing owner (USCG): VANE LINE BUNKERING LLC (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)).
- Vessel type
- Tug
- Flag
- United States
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- 32 m × 9 m
- Managing owner (USCG)
- VANE LINE BUNKERING LLC
Last reported position: 43.6404° N, 70.2842° W · North Atlantic Ocean · See on the map
Watch this ship
Get an email when BANCROFT 24 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 BANCROFT 24 over the last 24 hours would have sent 6 messages.
- ArrivedPhiladelphia
- ArrivedPortland
- LeftPhiladelphia
Detected from AIS, as of Nov 20, 2026, 11:38 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for BANCROFT 24 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: the Voydar app
Last reported position
received- Position
- 43.6404° N, 70.2842° W
- Area
- North Atlantic Ocean
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- —
- Heading
- —
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Philadelphia, Portland, and Marcus Hook).
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)Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 32 mone tick every 5 m
Beam 9 mPlan outline, to scale
- Name
- BANCROFT 24
- IMO numberWhat is an IMO number?
- 8644383
- MMSIWhat is an MMSI?
- 367092740
- Call signWhat is a call sign?
- WDP7248
- Flag
- United States
- Vessel type
- Tug
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 32 m
- Beam
- 9 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.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Managing owner (USCG)
- VANE LINE BUNKERING LLC(not linked to a company record)Source: US Coast Guard — Merchant Vessels of the United States (documented vessels) · reported · high confidence · retrieved Oct 6, 2026Coast Guard documentation record (2026-09 file) matched to this ship by IMO number and call sign. The managing owner is the company the Coast Guard has on record for the ship's certificate of documentation.
- Ship radio licensee (FCC)
- Vane Line Bunkering LLC(not linked to a company record)Source: FCC Universal Licensing System — ship station licences · since 2025 · reported · high confidence · retrieved Nov 17, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.Bancroft Marine & Pile(not linked to a company record)Source: FCC Universal Licensing System — ship station licences · since 2024 · reported · high confidence · retrieved Nov 17, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.
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 |
|---|---|---|
| Arrived at PhiladelphiaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PortlandAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left PhiladelphiaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PhiladelphiaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from WDI4974 to WDI4977 | AIS, seen by Voydar | |
| Former name: LONG ISLAND | AIS, seen by Voydar | |
| Reported arrival at MORGAN CITY, LA, PORT OFAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at GalvestonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from GalvestonAuthority-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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| LONG ISLAND | Former name, change seen on AIS | Oct 31, 2026 | AIS (vessel's own broadcast) |
A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.
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 |
|---|---|---|---|
| Philadelphia USPHL | Nov 20, 2026, 00:35 UTC | in port | — |
| Portland USPWM | Nov 19, 2026, 22:26 UTC | in port | — |
| Philadelphia USPHL | Nov 19, 2026, 16:58 UTC | Nov 19, 2026, 21:34 UTC | 4 h 36 min |
| Philadelphia USPHL | Nov 19, 2026, 12:11 UTC | Nov 19, 2026, 14:25 UTC | 2 h 14 min |
| Philadelphia USPHL | Nov 19, 2026, 05:29 UTC | Nov 19, 2026, 09:49 UTC | 4 h 20 min |
| Philadelphia USPHL | Nov 18, 2026, 02:45 UTC | Nov 19, 2026, 01:52 UTC | 23 h 7 min |
| Marcus Hook USMAH | Nov 17, 2026, 20:34 UTC | Nov 18, 2026, 02:45 UTC | 6 h 11 min |
| Philadelphia USPHL | Nov 17, 2026, 14:16 UTC | Nov 17, 2026, 18:33 UTC | 4 h 17 min |
| Philadelphia USPHL | Nov 16, 2026, 23:51 UTC | Nov 17, 2026, 11:26 UTC | 11 h 35 min |
| Marcus Hook USMAH | Nov 16, 2026, 02:52 UTC | Nov 16, 2026, 23:11 UTC | 20 h 19 min |
| Philadelphia USPHL | Nov 15, 2026, 22:42 UTC | Nov 15, 2026, 23:52 UTC | 1 h 10 min |
| Philadelphia USPHL | Nov 14, 2026, 11:35 UTC | Nov 15, 2026, 17:01 UTC | 29 h 26 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| MORGAN CITY, LA, PORT OF | Arrival | Mar 29, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Arrival | Mar 24, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Departure | Mar 23, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GULF INTRACOASTAL WATERWAY, MISSISSIPPI RIVER, LA., TO SABINE RIVER, TX (INCLUDED IN GULF INTRACOASTAL WATERWAY CONSOLIDATED REPORT) | Arrival | Jan 17, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Departure | Jan 16, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Departure | Jan 8, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 8, 2015.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 |
|---|---|---|
| Nov 20, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 583 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 19, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 596 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 18, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 581 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 17, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 602 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 16, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 583 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 15, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 585 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 14, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 570 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 13, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 583 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 12, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 626 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 10, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 911 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 9, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 888 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 8, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 583 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 7, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 583 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 6, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 583 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 5, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 583 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 4, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 611 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Nov 2, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 592 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 31, 2026, 22:50 UTC | Draught change Reported draught went from 4.9 m to 4.3 m after leaving Baltimore. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 30, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 720 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
| Oct 29, 2026, 00:00 UTC | IMO used twice IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | High (80%) |
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.
Frequently asked questions
- What kind of ship is BANCROFT 24?
- BANCROFT 24 is a tug sailing under the flag of United States. The vessel is 32 m long with a beam of 9 m.
- Who is recorded as the owner or manager of BANCROFT 24?
- VANE LINE BUNKERING LLC is recorded as Managing owner (USCG) for BANCROFT 24 (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for BANCROFT 24?
- Voydar has no matched sanctions record displayed for BANCROFT 24 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 BANCROFT 24. Missing records do not establish whether the ship has been detained.
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
More Tugs
Other tugs with full Voydar profiles. A different set each day. All tugs
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/8644383Cite this page
BANCROFT 24. Voydar (voydar.com). https://www.voydar.com/vessel/8644383-bancroft-24. Retrieved November 20, 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 includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.