NO BKKB Bergen Vitensenter AS
NO-BKKB-Bergen-Vitensenter-AS
Data as of 2026-09-06
Registry
This organisation
| Netblocks | 4 |
| IPv6 | 1 prefix (largest 2a00:14d8:4514::/48) |
| Also registered under this name | 5 netblocks across 2 separate records |
| Record ID | 236368545 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names 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.213.136/30 | NO-BKKB-Bergen-Vitensenter-AS | RIPE | ASSIGNED PA | ● low |
| 85.200.204.32/30 | NO-BKKB-Bergen-Vitensenter-AS | RIPE | ASSIGNED PA | ● low |
| 85.200.239.248/30 | NO-BKKB-Bergen-Vitensenter-AS | RIPE | ASSIGNED PA | ● low |
| 2a00:14d8:4514::/48 | NO-BKKB-BERGEN-VITENSENTER-AS | RIPE | ASSIGNED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a00:14d8:4514::/48 |
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 Bergen Vitensenter 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:4514::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
NIC Handles
BKKB-MNT
DUMY-RIPE
DUMY-RIPE
LYSE-MNT