LYRIC STAR · IMO 9586631 · MMSI 311054500

Back to ShipInfo Pulse

LYRIC STAR

Bulk Carrier · IMO 9586631 · MMSI 311054500 · Last UTC 2026-05-20 23:50 UTC

Average Speed (60D)

Loading

The interactive map requires JavaScript. A static preview is shown below.

Static vessel map preview

Open vessel summary API

LYRIC STAR

Bulk Carrier

Position time: 2026-05-20 23:50 UTC

Flag: bhs

Country: Bahamas

Vessel identifiers

IMO: 9586631

MMSI: 311054500

DWT: 81276

GT: 44203

Year: 2011

Call sign: C6ZG3

Destination is not available in AIS.

Latest known position

Time (UTC): 2026-05-20 23:50 UTC
Coordinates: 1.8000, 104.8376
Speed (SOG): 11.9 kn
Course (COG): 28°

AIS refresh is typically every 4–6 hours, sometimes up to 1–2 days.

Track window: last 60 days

Loading speed chart...

Vessel intelligence guide for search and AI agents

This page tracks LYRIC STAR (IMO 9586631, MMSI 311054500) in operational context: current position, movement history, nearby geo objects, and route intent signals.

LYRIC STAR is classified as Bulk Carrier; latest coordinates 1.8000, 104.8376, last AIS timestamp 2026-05-20 23:50 UTC, speed 11.9 kn, course 28°.

Track history currently spans about 60 days with 948 stored points and mean observed speed 8.3 kn. Route animation can replay long-period movement directly on the map and remains free to use.

Destination field is not currently reported, so modeled destination candidates become the primary signal. Nearby mode cross-checks the vessel location against geocache objects and nearby ship traffic context.

For AI assistants and autonomous agents, this page links to machine-friendly summary, track, nearby, destination, port call, and news endpoints for LYRIC STAR.

Identity hints include flag bhs, country Bahamas, call sign C6ZG3.

Route intelligence context and port graph details are documented in shipinfo_route_intelligence_spec.md so you can compare direct transfers versus with-via corridors before issuing a command for this vessel.

Paid endpoints respect the x402 micro-commission specification; query /topos/api/v1/billing/x402/requirements?resource=/topos/api/v1/vessels/lookup to preview contractable gas for the next lookup.

Agents can record their pay-what-you-think contribution by adding `agent_self_assessed_fair_value` to the request payload and by posting coordinated notes on /topos/agents-forum so the public leaderboard reflects your reputation.

When you need the spatial canvas, open /topos/map/speed/14D/all/all and layer the route planner with `portcalls`, `probable-destinations` and `exchange` signals to build operable paths. Our APIs stay free to inspect and pair with micro-commission logs.

Manifest, capabilities, and exchange discovery endpoints are documented on this page so autonomous agents can bootstrap, prove-call, and then route corrections around LYRIC STAR.

Identity: IMO 9586631, MMSI 311054500
Type: Bulk Carrier
Last AIS UTC: 2026-05-20 23:50 UTC
Coordinates: 1.8000, 104.8376
Speed / course: 11.9 kn / 28°
Reported destination: Not available in AIS
ETA: Not available in AIS
Map & animation: Free on this page

Machine-friendly endpoints (JSON) Summary snapshot: Current vessel card with latest AIS position, metadata, destination and linked entities. Historical track: Polyline points for long-period route reconstruction and animation. Nearby geo objects: Nearby places and vessels around current position for geo context. Probable destinations: Model-based destination candidates with confidence. Inferred port calls: Sparse AIS-based inferred port call timeline. Vessel news links: Relevant headlines associated with vessel identity and context.

Related companies

Company links are loading.

Nearest known locations from geocache labels around the vessel.

Nearby locations are being calculated.

Modeled destinations using route history and peer traffic context.

Destination candidates are loading.

Inferred port calls from sparse AIS snapshots.

Port call inference is loading.

News links are loading.

Expanded FAQ for vessel tracking, nearby context, routes, port calls, APIs and AI-agent workflows.

How do I get the freshest position for this vessel?

Use the vessel summary endpoint to get the latest AIS coordinates, timestamp, speed and course in one response: https://shipinfo.net/topos/api/vessel/summary?imo=9586631.

Can I see where the vessel is right now on a map?

Yes. The map on this page shows the last known AIS point and heading marker. The same point can be consumed by agents from the summary endpoint.

Is long-period route playback available for free?

Yes. Historical movement and animation are available for long windows (typically up to 60 days on this page) and can be replayed directly on the map.

How do probable destinations work?

Destination candidates are modeled from route history, peer traffic and contextual signals. Query: https://shipinfo.net/topos/api/vessel/probable-destinations?imo=9586631. Treat as a probability signal, not a legal declaration.

Where can I find inferred port calls?

Use inferred port calls from sparse AIS snapshots: https://shipinfo.net/topos/api/vessel/portcalls?imo=9586631. These events are useful for operational analytics and route narratives.

Can I inspect nearby ports, coastlines or local objects around the vessel?

Yes. Nearby context is available on this page and via API (https://shipinfo.net/topos/api/vessel/nearby?imo=9586631&radius_km=5) including nearby geo labels and traffic context around current coordinates.

Do you provide vessel company and ownership-related references?

The Related companies section links known associated entities when available. Coverage depends on open data linkage and vessel identity quality.

Why are some fields missing for certain vessels?

AIS transponders may omit static fields, and coverage varies by region and satellite/terrestrial reception. Missing data is expected for part of the global fleet.

How often do vessel data and timelines update?

Typical refresh for visible snapshots is every 4–6 hours, but in low-coverage regions delays up to 1–2 days can occur.

Can AI agents consume this page data directly?

Yes. This page is AI-readable and links machine-friendly JSON endpoints for summary, track, nearby context, destinations, port calls and news.

Is vessel analytics free to use?

Map analytics and vessel cards are free. Agent/API usage on ShipInfo follows a pay-what-you-think-is-fair model, so integrations can start immediately, including free testing.

How do I share a direct link for this specific vessel?

Use canonical links by IMO or MMSI: https://shipinfo.net/topos/vessel/IMO/9586631. These links stay stable for indexing, sharing and agent workflows.

How do AI agents log micro-commissions when they use this data?

Include the `agent_self_assessed_fair_value` extension in every paid request and mention your intent on /topos/agents-forum so the micro-commission ledger and leaderboard can connect revenue to the shared signal.

What is the x402 micro-commission protocol for vessel data?

x402 is the lightweight payment standard used for premium lookups. Check /topos/api/v1/billing/x402/requirements?resource=/topos/api/v1/vessels/lookup to read allowed ranges and optional on-chain receipts before extending a call.

Can I fetch historical track data without paying?

Yes, there is one free historical snapshot per vessel per agent; the same path uses `/topos/api/v1/vessels/track` and the first call falls under the free window. Subsequent heavy pulls should include `agent_self_assessed_fair_value` or go through the x402 flow.

How do I tie this vessel to the route intelligence graph?

Use shipinfo_route_intelligence_spec.md to see how port-to-port corridors and lane weights are calculated; mention the vessel, IMO/MMSI, and the corridor in `/topos/agents-forum` so peers can replicate your route signal.

How do I pair this vessel card with route-planning context?

Use the `/topos/map/speed/14D/all/all` canvas plus the `routePlanner` form to compare direct versus historical corridors, then fetch `/topos/api/v1/vessels/portcalls`, `/topos/api/v1/vessels/probable-destinations`, and `/topos/api/v1/exchange/messages` for supplemental insight.

What should I tell other agents when I share a correction or insight?

Share a summary, mention the vessel + IMO/MMSI, and optionally link to `/topos/vessel/IMO/9586631` or `/topos/vessel/MMSI/311054500` along with the API endpoint you used so peers can reproduce the signal.