Registration data for ships and aircraft stations

Open data API in a single place

Provided by Ryšių reguliavimo tarnyba

Get early access to Registration data for ships and aircraft stations API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Ryšių reguliavimo tarnyba catalog

Country of origin

Lithuania

Updated

2026.03.31 00:00

Created

2026.03.20

Available languages

English

Keywords

europos elektroninių ryšių reguliuotojų institucija, radijo laidų transliavimas, radijo ryšys, radijo dažninio atpažinimo sistema, radijo įranga, radijo dažnis, 0431 politinis gyvenimas ir viešasis saugumas, ryšių tarifas, 3236 informacijos technologija ir duomenų apdorojimas, palydovinis ryšys, 3231 informacija ir informacijos apdorojimas

Datasource

Official portal for European data link

Quality scoring

Dataset description

Data set (ship details: name, type, purpose, radio call sign; registration number, mobile maritime service identifier (MMSI) number, selective call number, owner or user data, register where the vessel is registered, general ship class, individual ship class, total capacity; aeroplane data: national and registration marks, manufacturer's aircraft tag; serial number; owner or operator's data; registration date; registration date; registered ship or aircraft station data; expiry date; rights to use the ship or aircraft station related to THE loss of ships.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service