Back to Companies DeskLelystadAirport
Technology market and infrastructure profile visual with growth structure.
Reference visual: company and capital context snapshot.

Company Briefing / Network-related institution

LelystadAirport

LelystadAirport is tracked because its presence in the RIPE ASN registry creates a public signal of potential internet routing dependencies for an airport. Changes in AS210372 registration, prefix announcements, or the airport's connectivity disclosures could reveal operational shifts, security risks, or dependencies that matter to infrastructure analysts and aviation-sector risk mapping.

Evidence Pack

Primary-source references used for classification and impact scoring.

Context

LelystadAirport is a Dutch regional airport with a registry presence as AS210372. The airport is operated by Royal Schiphol Group and focuses on general aviation, business aviation, maintenance, and training. Public evidence includes RDAP and RIPEStat records, the airport's website, and Schiphol Group's portfolio page, but lacks active BGP announcements, technical contacts, or a confirmed legal holder of the ASN. The profile serves as a baseline for monitoring routing changes, registry updates, or new disclosures that could alter the subject's infrastructure relevance.

Core Entity Brief

Core Entity Brief

EntityLelystadAirport
Public roleLelystadAirport is tracked because its presence in the RIPE ASN registry creates a public signal of potential internet routing dependencies for an airport. Changes in AS210372 registration, prefix announcements, or the airport's connectivity disclosures could reveal operational shifts, security risks, or dependencies that matter to infrastructure analysts and aviation-sector risk mapping.
RegionNetherlands
CategoryNetwork-related institution
Primary domainInfrastructure
Signal focusInstitution Type
Time horizonQuarter (30-120d)
ImpactMedium
Confidence0.95
Evidence coverage5 public source references
Related coverageProfile anchor article
WebsitePublic evidence pending
Last updateJun 02, 2026

LelystadAirport is presented as a Network-related institution in the BTW company and institution directory. LelystadAirport is tracked because its presence in the RIPE ASN registry creates a public signal of potential internet routing dependencies for an airport. Changes in AS210372 registration, prefix announcements, or the airport's connectivity disclosures could reveal operational shifts, security risks, or dependencies that matter to infrastructure analysts and aviation-sector risk mapping.

The current public read is bounded by primary domain: Infrastructure; signal focus: Institution Type; time horizon: Quarter (30-120d); impact band: Medium. These fields give readers a stable baseline for comparing the profile with other institutions, operators, and market actors.

The evidence basis currently includes 5 public evidence references and the linked public profile. Claims should stay limited to role, context, operating surface, dependencies, and watchpoints that are visible in reviewed public material.

Signal Map

Signal Map

  • Why tracked: LelystadAirport is tracked because its presence in the RIPE ASN registry creates a public signal of potential internet routing dependencies for an airport. Changes in AS210372 registration, prefix announcements, or the airport's connectivity disclosures could reveal operational shifts, security risks, or dependencies that matter to infrastructure analysts and aviation-sector risk mapping.
  • Object role: Lelystad Airport operates as a regional airport in Lelystad, Flevoland, providing general aviation, business aviation, maintenance, and training services. The institution is part of the Schiphol Group portfolio. In internet infrastructure, the subject name is associated with AS210372 in RIPE registry data, indicating potential direct enterprise routing or connectivity management.
  • Impact note: The impact of signals about LelystadAirport lies in how they affect the airport's connectivity surface and, by extension, the digital services used by aviation tenants, flight schools, and maintenance operators. A confirmed active ASN or new prefixes would move the subject from a paper-registry entry to an operational network node with measurable dependency and risk consequences.
  • Control surface: public operating records, official service pages, source-backed relationship updates
  • Key dependencies: official company sources, public registries, operator-published records

Actions