FCS MOBILE BV

FCS_MOBILE_BV
Data as of 2026-09-06
Registry
This organisation
Netblocks6
IPv6 6 prefixes (largest 2a12:f381:1900::/40)
Also registered under this name 246 netblocks across 241 separate records
Record ID236943665
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 6 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a12:f381:1900::/40 FCS_MOBILE_SE RIPE AGGREGATED-BY-LIR ● low
2a12:f381:1e00::/40 FCS_MOBILE_SA RIPE AGGREGATED-BY-LIR ● low
2a12:f381:8300::/40 FCS_MOBILE_AG RIPE AGGREGATED-BY-LIR ● low
2a12:f381:8a00::/40 FCS_MOBILE_AS RIPE AGGREGATED-BY-LIR ● low
2a12:f381:a000::/40 FCS_MOBILE_BV RIPE AGGREGATED-BY-LIR ● low
2a12:f381:ae00::/40 FCS_MOBILE_CO RIPE AGGREGATED-BY-LIR ● low

IPv6 ranges (6)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
RPKI-inferred operator Andreas Fink
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

AF15-MNT DUMY-RIPE DUMY-RIPE