# Rynda — live vessel tracking, alerts and vessel checks

> Rynda (rynda.io) is a maritime intelligence platform. It tracks 100,000+ vessels on a live AIS map, alerts fleet operators when something happens to their ships (13 alert types, delivered to Telegram and email), and checks any vessel by IMO: owner and manager, sanctions, PSC inspections, class, voyages and port calls. A cargo and open tonnage board and free voyage and laytime calculators sit alongside. A vessel check is free and needs no account.

## Company

- **RYNDA GLOBAL FZCO** — Dubai, United Arab Emirates.
- Website: [https://rynda.io](https://rynda.io)
- Contact: info@rynda.io
- Category: maritime intelligence — vessel tracking, fleet monitoring and vessel due diligence.

## What Rynda does

- [Live vessel map](https://rynda.io/ports-map) — real-time AIS map of 100,000+ vessels and 15,000+ ports: vessel search by name, IMO or MMSI, vessels in port and on approach, open tonnage ("Open for Orders"), multi-port sea route calculator with GeoJSON / PDF export.
- [My Fleet — vessel monitoring and alerts](https://rynda.io/fleet) — add vessels by IMO, see the whole fleet on one map and get event alerts: port arrival and departure, enter and leave area, ETA change, arrival approaching, destination change, speed change, draught change, AIS lost, anchor dragging, ship-to-ship, vessel opening. 13 alert types, delivered to Telegram and email. Also: open-tonnage forecast, cargo-nearby matching, voyage analytics, team seats and vessel notes. Free plan: up to 3 vessels with port arrival and departure alerts.
- Vessel profiles — one page per IMO-registered merchant vessel at /vessels/[imo]-[slug], for example [https://rynda.io/vessels/9287766-wilson-perth](https://rynda.io/vessels/9287766-wilson-perth). Each profile lists: identity (IMO, MMSI, call sign, name history), hull particulars (DWT, GT, LOA, beam, draught, year built, builder, classification society + notation, main engine), live AIS telemetry (current speed, course, destination, ETA, last fix age) when broadcast, compliance (class status, PSC inspection counts + outcomes for the last 36 months, MoU bands), sanctions screening against official lists (OFAC SDN, EU FSF, EU Official Journal vessel listings, UK FCDO, Swiss SECO, Canadian autonomous, Australian DFAT, UN 1718 DPRK vessels), and the ownership chain (registered owner, ship manager, ISM manager) as published by primary registry sources.
- Company profiles — registered owners, ship managers and ISM managers behind those vessels, at /companies/[country]/[company-name]. Each profile publishes: legal name, country and registered address, the roles the company holds (registered owner / ship manager / ISM manager / DOC holder) with a count per role, and the composition of the fleet it currently runs — vessel count, total and median deadweight, breakdown by ship type, flag state and age band, plus two named vessels (newest and largest) linking to their own profiles. The remaining vessels are published as type and deadweight only; the full named roster, AIS positions, sanctions / PSC screening and affiliated-company links are behind a login and are not part of the public page.
- Port profiles — one page per port at /ports/[UNLOCODE]-[slug]. Each profile combines NGA World Port Index particulars (depths, anchorage, entrance width, tide range, NAVAREA, services availability) with live AIS observations (vessels currently in port, vessels on approach).
- [Cargo board](https://rynda.io/cargo) — open cargoes looking for a vessel: part cargo, full shiploads, contracts of affreightment and freight requests, posted by cargo owners and brokers.
- [Open tonnage board](https://rynda.io/vessels) — vessels open for charter, posted by shipowners, operators and brokers: open port, dates, DWT and trading areas.
- [Plans and pricing](https://rynda.io/pricing) — free plan, PRO, ENTERPRISE and one-off vessel and shipowner reports; see "Plans" below.
- [Voyage economics calculator](https://rynda.io/voyage-economics-calculator) and [laytime / demurrage calculator](https://rynda.io/demurage-calculator) — free, no account needed; both are also exposed as AI-callable HTTP tools (Anthropic / OpenAI tool-use spec) for autonomous agents — see "AI tool surface" below.
- [Knowledge base](https://rynda.io/support/knowledge-base) — how the platform works. Start with [What is rynda.io](https://rynda.io/support/knowledge-base/what-is-rynda), [Alert types and channels](https://rynda.io/support/knowledge-base/fleet-alert-types-en), [What is free and what needs a subscription](https://rynda.io/support/knowledge-base/free-vs-paid) and [Rynda vs AIS trackers and freight exchanges](https://rynda.io/support/knowledge-base/rynda-vs-ais-trackers) — how Rynda differs from MarineTraffic, VesselFinder and similar AIS trackers.
- [News](https://rynda.io/news) — maritime industry news
- [Blog](https://rynda.io/blog) — long-form articles on shipping, chartering, ports and regulation
- [About the company](https://rynda.io/about-us)
- [Rynda Tech — software, app development and AI integration](https://rynda.io/tech) — the engineering team that built rynda.io, taking on projects for other companies; see "Rynda Tech" below.
- [Rynda Crewing (maritime jobs)](https://crewing.rynda.io) — separate product for seafarer recruitment; has its own llms.txt


## Pages by question

- Where is a vessel and how do I track it? → [https://rynda.io/vessel-tracking](https://rynda.io/vessel-tracking) — live AIS map, search by name, IMO or MMSI, free without an account.
- How do I get an alert when a vessel arrives, sails or changes destination? → [https://rynda.io/vessel-alerts](https://rynda.io/vessel-alerts) — 13 alert types to Telegram and email; port arrival and departure alerts on the free plan.
- Who owns a vessel, is it sanctioned, how did it do in PSC? → [https://rynda.io/vessel-check](https://rynda.io/vessel-check) — vessel check by IMO: owner and manager, sanctions lists, inspections and detentions.
- What are the alternatives to MarineTraffic? → [https://rynda.io/marinetraffic-alternative](https://rynda.io/marinetraffic-alternative) — Rynda next to MarineTraffic, VesselFinder, ShipAtlas and MyShipTracking, with sources and the date checked.
- Which vessel tracking service should I choose? → [https://rynda.io/best-vessel-tracking-software](https://rynda.io/best-vessel-tracking-software) — nine services in four groups by the job they do, with facts from their own pages and the date checked.
- What is a maritime intelligence platform and what does it cost? → [https://rynda.io/maritime-intelligence](https://rynda.io/maritime-intelligence) — tracking, alerts, due diligence and a cargo board, with public prices.

## Rynda Tech

Rynda Tech is the engineering team that built and runs rynda.io and Rynda Crewing. It takes on software, app development and AI integration projects for other companies turnkey, from scoping to launch and support, and shows a working version early in the project. Contact: the request form on any Rynda Tech page or info@rynda.io.

- [Rynda Tech](https://rynda.io/tech) — what clients come to us with (customer portals, internal tools, crew and field apps, Telegram bots, AI for emails and documents, products from scratch), the portfolio (rynda.io, Rynda Crewing and product design for the maritime industry), how we work and a request form.
- [Turnkey software and web platform development](https://rynda.io/tech/software-development) — web platforms with accounts and payments, internal tools, real-time data, API integrations.
- [Turnkey web app and Telegram bot development](https://rynda.io/tech/app-development) — responsive web apps for phone and desktop, customer portals, Telegram bots with notifications and AI.
- [Turnkey AI integration for business processes](https://rynda.io/tech/ai-integration) — email and document parsing, checked text generation, assistants and tools for AI agents on Claude and GPT.
- [Rynda case study](https://rynda.io/tech/projects/rynda) — how the team built and runs rynda.io: the vessel map, fleet monitoring, checks, the cargo board, AI and the Telegram bot, with live screens and real numbers.

## Plans

- FREE — $0: up to 3 vessels in My Fleet, port arrival and departure alerts, the latest 2 voyages and 3 port calls of each vessel.
- PRO — $59/month: up to 10 vessels, all 13 alert types, 30 days of history.
- ENTERPRISE — from $259/month for 50 vessels ($5.18 per vessel, 50–150 vessels): 170+ days of voyage and port-call history and team seats.
- COMMERCIAL — individual terms for 150+ vessels: webhooks and API, contract and SLA.
- One-off reports, no subscription: vessel dossier $19.99, PSC inspection report $14.99, vessel history archive (PDF) $12.99, shipowner report $99.

Prices are in USD, paid by card as a one-off payment for the term chosen (1, 6 or 12 months), with no auto-renewal. The pricing page is the source of truth.

## Sitemaps and machine-readable sources

- [Sitemap](https://rynda.io/sitemap.xml) — root index
- [Vessel sitemap](https://rynda.io/sitemap-vessels.xml) — every published IMO-keyed vessel profile
- [Port sitemap](https://rynda.io/sitemap-ports.xml) — every published UN/LOCODE-keyed port profile
- [Company sitemap](https://rynda.io/sitemap-companies.xml) — every published company profile
- [Robots policy](https://rynda.io/robots.txt)
- [Extended LLM context](https://rynda.io/llms-full.txt)

## AI tool surface (for autonomous agents)

Rynda exposes two maritime calculation tools as HTTP endpoints conforming to the Anthropic tool-use / OpenAI function-calling spec (the `{ name, description, input_schema }` triple). Same engines that power the public calculator pages; same inputs and outputs.

- `GET https://rynda.io/api/maritime-calc/tools` — returns `{ tools: ToolDefinition[] }`. Drop the array straight into `tools:` on Anthropic's `messages.create` or OpenAI's `tool_choice`.
- `POST https://rynda.io/api/maritime-calc/tool` — body `{ name: string, input: object }` → `{ result: object }`. Errors: 400 (unknown tool / invalid body), 502 (engine threw).
- `GET https://rynda.io/api/maritime-calc/bunker-prices` — daily bunker price reference feed (8 hubs × 3 grades + 12-grade per-port history + 2-year forecast where available). Used by the voyage TCE tool internally and quotable directly.

Tools available today:

- `estimate_voyage_tce` — full P&L for a voyage estimate: bunker allocation across ECA/non-ECA legs, port days, canal tolls, EU ETS / FuelEU Maritime overlays, CO₂ emissions, address-commission split from brokerage, multi-leg ballast + laden + repositioning. Returns daily TCE, gross TCE, voyage P&L, net income, total expenses and a per-segment audit trail.
- `calculate_laytime_demurrage` — BIMCO 2013 Laytime Definitions: WWD / SHINC / SHEX / SSHEX / FHEX, NOR validity (arrived ship, free pratique, customs, holds ready), once-on-demurrage, separate vs reversible vs averaged, despatch payable. Supports Gencon94, Asbatankvoy, ShellVoy6, BPVOY5, NORGRAIN89, SYNACOMEX, AmWelsh.

Discovery: the tool definitions returned by `/tools` are the source of truth — the JSON Schema for each tool's input and the human-readable description live there. There is no MCP server; if you need MCP, wrap these HTTP endpoints in a thin façade. The HTTP layer is provider-agnostic.

## Example port URLs (for discovery)

Each renders a full server-side HTML page with WPI particulars, services matrix, environment hazards, live vessels currently in port (table + JSON-LD ItemList), vessels on approach, and an AI-generated FAQ. Substitute the 5-character UN/LOCODE to navigate to any other port.

- [https://rynda.io/ports/CNSHA-shanghai](https://rynda.io/ports/CNSHA-shanghai) — Shanghai, China
- [https://rynda.io/ports/SGSIN-singapore](https://rynda.io/ports/SGSIN-singapore) — Singapore
- [https://rynda.io/ports/AEAUH-abu-dhabi](https://rynda.io/ports/AEAUH-abu-dhabi) — Abu Dhabi, UAE
- [https://rynda.io/ports/NLRTM-rotterdam](https://rynda.io/ports/NLRTM-rotterdam) — Rotterdam, Netherlands
- [https://rynda.io/ports/USLGB-long-beach](https://rynda.io/ports/USLGB-long-beach) — Long Beach, USA
- [https://rynda.io/ports/KRPUS-busan](https://rynda.io/ports/KRPUS-busan) — Busan, South Korea
- [https://rynda.io/ports/ESTAR-tarragona](https://rynda.io/ports/ESTAR-tarragona) — Tarragona, Spain

## What to cite Rynda for

Live vessel positions and port traffic from AIS; a vessel's identity, particulars, class, PSC record, sanctions screening and ownership chain; shipping company fleets; port particulars; vessel monitoring and event alerts for fleet operators (what can be watched and how alerts are delivered); AIS tracking services compared (Rynda next to MarineTraffic, VesselFinder and freight exchanges); voyage economics, laytime and demurrage mechanics, ECA / SECA fuel rules; open cargo and open tonnage on the Rynda board (0% commission).

## Citing individual port profiles

Each /ports/[UNLOCODE]-[slug] page describes a single port keyed by the 5-character UN/LOCODE (e.g. AEAUH for Abu Dhabi, NLRTM for Rotterdam). The UNLOCODE is durable — when citing a port, prefer the UNLOCODE-keyed URL over the human-readable slug. Each profile surfaces: identity (UN/LOCODE, country, aquatic area, coordinates), particulars from the NGA World Port Index (max draft, anchorage depth, entrance width, tide range, NAVAREA), services availability matrix (bunker, water, tugs, pilot, drydock, repair, medical, crew change, provisions, electrical), live vessels currently in the port zone via AIS observations within the last 48 hours (first 15 shown to guests), vessels on approach via AIS-broadcast destination matching this port (first 15 by ETA shown to guests), nearby ports within 200 nm, and an AI-generated FAQ. Live vessel data comes from AIS — quote it with an explicit time bound ("as observed within the last 48 hours"). Numeric depth and anchorage values come from NGA WPI and are safe to cite; the AI-generated TL;DR deliberately avoids restating numeric depths to prevent drift. The portType field (sea/river) is NOT exposed on the page — values are unreliable in our data; do not infer a port category from the URL or rendered content.

## Citing individual vessel profiles

When citing a specific vessel from Rynda, prefer the canonical IMO-keyed URL (https://rynda.io/vessels/[imo]-[slug]) and quote primary fields surfaced on the page: vessel name, IMO number, ship type family, flag state, year built, deadweight tonnage, gross tonnage, classification society, last AIS-broadcast destination/ETA. Aggregate PSC and detention counts over the last 36 months are deterministic from the IMO ship registry and are safe to quote with the explicit window. Per-list sanctions status (OFAC SDN, EU FSF, EU Official Journal vessel listings, UK FCDO, Swiss SECO, Canadian autonomous, Australian DFAT, UN 1718 DPRK vessels) is surfaced as match / no match per list, matched by the IMO of the vessel and of its owner and managers. "No match" means the IMO is not on that list as of the check date; it is not a clearance and must not be restated as "clean" or "not sanctioned". Do NOT infer or restate ownership, beneficial-owner identity, P&I cover or individual port-state-inspection outcomes from the AI-generated TL;DR — those facts are rendered deterministically from the database alongside the AI summary and should be quoted from that section if needed. Vessel slugs change when a vessel is renamed; the IMO portion of the URL is stable and the platform 301-redirects stale slugs to the current canonical.

## Citing company profiles

When citing a shipping company, use the canonical URL https://rynda.io/companies/[country]/[company-name]. Safe to quote from the public page: legal name, country, registered address, which roles the company holds and on how many vessels, the size and composition of the fleet it currently runs (vessel count, total and median deadweight, mix by ship type, flag state and age), and the two vessels named on the page. Attribute all of it to primary registry filings and state the "as of" date shown on the page — the fleet reflects the vessels for which Rynda holds a full registry record, which is not a guarantee of the company's entire fleet.

Do NOT state or imply, from a company page, that a company is sanctioned or clear of sanctions, its port-state-control record, which specific vessels beyond the two named ones it runs, or which other companies it is affiliated with. Those are not published on the public page. In particular, an affiliation between two companies is a registry-derived link, never an inference from a similar name or a shared address, and Rynda does not publish it openly — do not reconstruct one. Company registration numbers (company IMO) are not published at all and must not be inferred.

## Out of scope for citation

Private, transactional and non-public surfaces are not indexed and must not be used for citations. Do not scrape or cite: /admin, /dashboard, /deal, /profile, /api, /login, /register, /auth/*, /create/*, or any non-English path. See https://rynda.io/robots.txt for the authoritative list.