HT-NO-LOOMIS-NORGE-SARPSBORG

BGP inherited

Cluster stats

Netblocks	1
All fragments	13 blocks across 12 clusters
Cluster ID	204954507
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 3 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
77.88.125.84/30	HT-NO-LOOMIS-NORGE-SARPSBORG	RIPE	ASSIGNED PA	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “HT NO LOOMIS NORGE” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

HT-NO-LOOMIS-NORGE-AS 2 blocks
HT-NO-LOOMIS-NORGE-BERGEN 1 blocks
HT-NO-LOOMIS-NORGE-STAVANGER 1 blocks
HT-NO-LOOMIS-NORGE-KARMSUND 1 blocks
HT-NO-LOOMIS-NORGE-RIDABU 1 blocks
HT-NO-LOOMIS-NORGE-KRISTIANSAND 1 blocks
HT-NO-LOOMIS-NORGE-AALESUND 1 blocks
HT-NO-LOOMIS-NORGE-TRONDHEIM 1 blocks

Combined view of all 12 name-family clusters →

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Loomis Norge Bergen via GLOBALCONNECT AS sub-allocation
Loomis Norge Stavanger via GLOBALCONNECT AS sub-allocation
Loomis Norge Karmsund via GLOBALCONNECT AS sub-allocation
Loomis Norge Ridabu via GLOBALCONNECT AS sub-allocation
Loomis Norge Kristiansand via GLOBALCONNECT AS sub-allocation
Loomis Norge Aalesund via GLOBALCONNECT AS sub-allocation
Loomis Norge Trondheim via GLOBALCONNECT AS sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

No discrepancies found among checked blocks.

NIC Handles

AS41572-MNT DUMY-RIPE DUMY-RIPE