Core Entity Brief
| Entity | DK_IBF IKAST BETONVAREFABRIK A/S |
|---|---|
| Public role | Dormant ASNs can be activated without warning and used for prefix hijacking, route leaks, or other BGP abuse. Tracking this holder provides an early-warning reference for resource governance watchers and helps detect any transition from a latent entry to an active routing entity. |
| Region | Denmark |
| Category | Digital infrastructure institution |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.70 |
| Evidence coverage | 3 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 02, 2026 |
DK_IBF IKAST BETONVAREFABRIK A/S is a dormant ASN registrant with no public revenue model or active network services. Its name hints at a concrete manufacturing business, but that remains unconfirmed.
What It Does
- Visible operating role: The company does not offer any internet connectivity services, IP transit, or hosting. Its only infrastructure footprint is the passive holding of AS211676.
- Revenue model: No public evidence identifies a customer base, revenue streams, or contract position. The registry record does not disclose commercial activities.
Operating Snapshot
- Identity baseline: DK_IBF IKAST BETONVAREFABRIK A/S is the registered holder of AS211676 in the RIPE NCC region. The name suggests a concrete products factory in Ikast, Denmark.
- Routing context: AS211676 has no announced prefixes and no visible BGP peers. The ASN is dormant, with no historical routing data available.
Control Surface
- Registry records: The RIPE NCC entry for AS211676 is the sole verifiable control point. Modifications to this record—or the addition of route objects—could enable future network operations.
- Potential route objects: If the entity creates route objects in the RIPE database, it could authorize BGP announcements, expanding its control surface.
Watchpoints
- Record freshness: Stale or changed registry records can create uncertainty about the entity's current network role.
- Footprint change: Any new ASN, prefix, website, or PeeringDB entry would significantly alter the entity's infrastructure relevance and should trigger reassessment.

