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 monitoring baseline routing changes, registry updates, or new disclosures that could alter the subject's infrastructure relevance.
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.
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.
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.
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.
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.
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 monitoring baseline routing changes, registry updates, or new disclosures that could alter the subject's infrastructure relevance.
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.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
LelystadAirport
Lelystad Airport is a Dutch regional airport operated by Royal Schiphol Group, focused on general and business aviation. The name LelystadAirport appears in internet registry records for AS210372, though active BGP announcements remain absent. This profile assembles the public evidence linking the airport to the autonomous system and outlines the operating surface, evidence gaps, and watchpoints for infrastructure monitoring.
Why It Matters
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.
What Public Sources Show
Lelystad Airport is a regional airport in the Netherlands, operated by Royal Schiphol Group, that focuses on general and business aviation alongside maintenance and training. The name LelystadAirport also appears in the internet’s routing registry under autonomous system number AS210372.
Although active BGP announcements are absent from the current public record, the ASN entry signals that the airport may operate its own internet connectivity, making it a node worth monitoring for dependency mapping and infrastructure risk assessment.
Public evidence includes an official RDAP record for AS210372 listing LelystadAirport as the holder, a RIPEStat overview page confirming the ASN’s existence, and the airport’s own website at lelystadairport.nl. Royal Schiphol Group’s site explicitly names Lelystad Airport among the airports it operates, while Britannica places the facility in the municipality of Lelystad, Flevoland.
These sources together establish a clear real-world identity and a verifiable registry link, but they stop short of documenting any active network prefixes or the personnel who manage the ASN.
The airport’s control surface starts with its website, the public portal for passenger and tenant information. In the internet context, the key observable is the AS210372 registration. Anyone able to influence that record or announce IP prefixes under the ASN could affect network visibility and the digital services used by aviation tenants.
Royal Schiphol Group provides an additional governance layer that could drive changes in how the airport’s connectivity is sourced and managed.
Several signals would sharpen the assessment. First, new IP prefixes originated by AS210372 in public BGP feeds would confirm active routing and convert the ASN from a paper registration into an operational asset. Second, a change in the registration holder or a move to another registry would force a re‑examination of who controls the numbering resource.
Third, additions to lelystadairport.nl—a technical contact page, a network statement, or a PeeringDB entry—would add operational detail currently missing. Fourth, any public procurement or tender about the airport’s IT or connectivity contracts would reveal its dependency on providers and could shift monitoring priority.
The limits of the evidence are important. The AS210372 registration uses a name matching the airport, but no corporate registration number confirms that the same organisation holds the ASN. No public BGP data show that AS210372 has ever announced a prefix, so the airport may not be using it.
Without named technical contacts or a published network policy, the link is plausible but not proven, and readers should treat it as a lead.
Operating Surface
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.
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.
Watchpoints
The appearance of LelystadAirport in RIPE ASN data suggests a potential directly managed internet presence for a regional airport, which is uncommon and therefore worth monitoring. The evidence is thin, so the strategic takeaway is to treat this as a watchlist item rather than an active risk node until routing activity confirms operational use.
Any BGP announcement by AS210372, changes in the RIPE registration record, or updates to the airport's website that mention network operations would change the assessment. New PeeringDB entries or procurement documents about airport IT would also be significant.
No PeeringDB entry, no active BGP data, no technical contacts, no legal confirmation that the airport controls AS210372. Additional registry or routing sources are needed to strengthen the link between the institution and the numbering resource.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for LelystadAirport.
- RIPE registry record - RIPEstat provides a public ASN page for AS210372, supporting existence of a public routing/registry object for the subject-linked ASN.
- Operator website - The official website identifies Lelystad Airport as an airport in the Netherlands and provides operator-published context on the airport.
- schiphol.nl - Royal Schiphol Group states that it operates Amsterdam Airport Schiphol, Rotterdam The Hague Airport and Lelystad Airport.
- britannica.com - Britannica describes Lelystad as a municipality in Flevoland, supporting the geographic context of the airport’s location.
Domain of operation
Lelystad Airport is a Dutch regional airport operated by Royal Schiphol Group, focused on general and business aviation. The name LelystadAirport appears in internet registry records for AS210372, though active BGP announcements remain absent. This profile assembles the public evidence linking the airport to the autonomous system and outlines the operating surface, evidence gaps, and watchpoints for infrastructure monitoring.
- Registry RDAP / WHOIS record: public-source identity and registry context for LelystadAirport. Evidence basis: source-462ff845adf7
Timeline
- LelystadAirport public evidence observed
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.
At A Glance
- Name: LelystadAirport
- Type: Network-related institution
- Base: Netherlands
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- source-backed relationship updates
Why It Matters
- 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.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
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.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic Sources and Linked Organizations
| Organization | Link | Related organization | Confidence | Why it matters | Source | Caveat |
|---|---|---|---|---|---|---|
| Royal Schiphol Group | operates | LelystadAirport | High | Public source supports this object-to-object relationship. | Royal Schiphol Group states that it operates Amsterdam Airport Schiphol, Rotterdam The Hague Airport and Lelystad Airport. | Low risk |
Public View
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.
Watchpoints
- The appearance of LelystadAirport in RIPE ASN data suggests a potential directly managed internet presence for a regional airport, which is uncommon and therefore worth monitoring.
- The evidence is thin, so the strategic takeaway is to treat this as a watchlist item rather than an active risk node until routing activity confirms operational use.
- Any BGP announcement by AS210372, changes in the RIPE registration record, or updates to the airport's website that mention network operations would change the assessment.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track 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.
What evidence supports the profile?
public-source identity and registry context for LelystadAirport.
What should readers watch next?
The appearance of LelystadAirport in RIPE ASN data suggests a potential directly managed internet presence for a regional airport, which is uncommon and therefore worth monitoring.
