NO-BKKB-Tveit-Regnskap

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks9
IPv6 3 prefixes (largest 2a00:14d8:4277::/48)
Also registered under this name 8,116 netblocks across 2,748 separate records
Record ID245861919
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.196.12/30 NO-BKKB-Tveit-Regnskap RIPE ASSIGNED PA ● low
62.97.244.28/30 NO-BKKB-Tveit-Regnskap RIPE ASSIGNED PA ● low
62.97.248.44/30 NO-BKKB-Tveit-Regnskap RIPE ASSIGNED PA ● low
62.97.248.48/30 NO-BKKB-Tveit-Regnskap RIPE ASSIGNED PA ● low
85.200.213.28/30 NO-BKKB-Tveit-Regnskap RIPE ASSIGNED PA ● low
85.200.227.220/30 NO-BKKB-Tveit-Regnskap RIPE ASSIGNED PA ● low
2a00:14d8:1001:17a::/64 NO-BKKB-Tveit-Regnskap RIPE ASSIGNED ● low
2a00:14d8:4277::/48 NO-BKKB-Tveit-Regnskap RIPE ASSIGNED ● low
2a00:14d8:4305::/48 NO-BKKB-Tveit-Regnskap-AS RIPE ASSIGNED ● low

IPv6 ranges (3)

CIDR
2a00:14d8:4277::/48
2a00:14d8:4305::/48
2a00:14d8:1001:17a::/64

Footprint over time

15 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-10-04

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (2)

These blocks are registered to NO-BKKB-Tveit-Regnskap 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:4305::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4277::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

BKKB-MNT DUMY-RIPE DUMY-RIPE LYSE-MNT