NO BKKB Telenor Ucom AS
NO-BKKB-Telenor-Ucom-AS
Data as of 2026-07-26
Registry
Cluster stats
| Netblocks | 4 |
| IPv6 | 2 prefixes (largest 2a00:14d8:4235::/48) |
| All fragments | 5 blocks across 2 clusters |
| Cluster ID | 213476032 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.97.203.96/30 | NO-BKKB-Telenor-Ucom-AS | RIPE | ASSIGNED PA | ● low |
| 82.134.92.48/28 | NO-BKKB-Telenor-Ucom-AS | RIPE | ASSIGNED PA | ● low |
| 2a00:14d8:1001:138::/64 | NO-BKKB-Telenor-Ucom-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4235::/48 | NO-BKKB-Telenor-Ucom-AS | RIPE | ASSIGNED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to NO BKKB Telenor Ucom AS but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a00:14d8:4235::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
NIC Handles
BKKB-MNT
DUMY-RIPE
DUMY-RIPE
LYSE-MNT