Play · Poland
Play is the consumer brand of P4 Sp. z o.o., a mobile network operator in Poland owned by the iliad Group. The registry records two confirmed ASNs for the company, AS39603 and AS201019, and documents both as carrying mobile traffic. Play uses the mobile country and network code pair 260-06.
Autonomous systems
Holder names and prefix counts come from the RIPE NCC's RIPEstat Data API, fetched on 2026-09-06. Role and confidence come from the evidence linked in each row; "confirmed" means a PeeringDB or RIPEstat record, or the operator's own site, names the operator.
Mobile network codes
The MCC identifies the country and the MNC identifies the operator inside it. Together they appear in the IMSI of every SIM on the network and in device diagnostics; they are how a handset knows which network it is on.
About Play
Play has two ASNs in the registry, both announcing address space and both documented with a mobile role. AS39603 (P4NET P4 Sp. z o.o.) announces 19 IPv4 prefixes against a single IPv6 prefix at the last probe, and PeeringDB records it under the name "PLAY" with an info type of Cable/DSL/ISP. AS201019 (P4NET_POZ P4 Sp. z o.o.) announces 8 IPv4 prefixes against one IPv6 prefix, and PeeringDB records it as "P4", also typed Cable/DSL/ISP. No third ASN is recorded for the operator.
An address whose origin ASN is AS39603 or AS201019 is routed by P4, the company behind the Play brand. Both ASNs carry the mobile role in the registry, so an address originating in either one sits on the network that carries Play's mobile service rather than on a separate fixed or enterprise network. That still describes the routing, not the individual subscriber line, and the registry records nothing about how any single address inside those prefixes is assigned.
Research note. Legal entity P4 Sp. z o.o. Parent: ir.play.pl/history states iliad S.A. gained control of 100% of Play Communications S.A. (owner of P4) in 2020 via tender offer. The input gave no ASN candidates (RIPE asn.txt lists the company as 'P4', not 'Play'); RIPEstat searchcomplete for 'P4' returns AS39603 'P4NET P4 Sp. z o.o.' and AS201019 'P4NET_POZ P4 Sp. z o.o.'. AS39603: RIPE DB descr 'P4 Play network operator', PeeringDB name 'PLAY', website https://www.play.pl/, type Cable/DSL/ISP, 20 prefixes; bgp.he.net prefix descriptions 'PLAY MBB' (5.173.0.0/17, 46.112.0.0/16, 46.113.0.0/16, 109.243.192.0/18) and 'Mobile Services and Mobile Terminals' (89.108.200.0/21, 89.108.208.0/21) - consumer mobile network. AS201019 (Poznań): 9 prefixes, 'PLAY MBB' descriptions on 5.173.224.0/19 etc.; PeeringDB not retrieved (throttled), confirmed via RIPEstat/RIPE DB. MCC/MNC: 260-06 operational (GSM 1800/UMTS 900/LTE 800-2600/5G 2100/5G 3500). Candidate 260-98 is P4 but a 'Test network, Not operational' per Wikipedia - dropped. Wikipedia also lists 260-45 (Virgin Mobile MVNO, P4) and 260-77/78/79 (P4, status Unknown). Generations: play.pl/kampania/5g-w-play states 800/1800/2100/2600 MHz for 4G/LTE and 5G for selected offers; ir.play.pl/history: 4G launched 2011, 5G launched 2020, C-band 3500-3600 MHz obtained Oct 2023.
Checking whether an IP belongs to Play
Look up the origin ASN of the address and compare it with the table above. RIPEstat answers for any address, and the RADB whois mirror lists the routes registered under an ASN.
curl -s "https://stat.ripe.net/data/prefix-overview/data.json?resource=203.0.113.9" | jq '.data.asns'whois -h whois.radb.net -- '-i origin AS39603' | grep ^routeQuestions
What is Play's ASN?
The registry records two confirmed ASNs for Play, which operates as P4 Sp. z o.o.: AS39603, registered as P4NET, and AS201019, registered as P4NET_POZ. Both are documented as carrying mobile traffic, and PeeringDB lists them as "PLAY" and "P4" respectively.
What is the MCC/MNC of Play?
Play has one confirmed code pair in the registry: MCC 260, MNC 06, written together as 260-06. No second MNC is recorded as confirmed, so a device reporting 260-06 in Poland is registered on the Play network operated by P4.
Is an IP from AS39603 a mobile IP?
AS39603 is documented in the registry as a mobile-role ASN belonging to P4, the operator of Play, so an address originating there is routed by Play's mobile network. The registry does not record how individual addresses within those prefixes are handed out.
Sources
- https://www.play.pl
- https://www.play.pl/kampania/5g-w-play
- https://ir.play.pl/history
- https://en.wikipedia.org/wiki/Mobile_Network_Codes_in_ITU_region_2xx_(Europe)
- https://www.peeringdb.com/api/net?asn=39603
- https://stat.ripe.net/data/as-overview/data.json?resource=AS39603
- https://stat.ripe.net/data/searchcomplete/data.json?resource=P4
- https://rest.db.ripe.net/ripe/aut-num/AS39603.json
- https://rest.db.ripe.net/ripe/aut-num/AS201019.json
- https://bgp.he.net/AS39603
- https://bgp.he.net/AS201019
- RIPEstat Data API (holder, announced prefixes)
- PeeringDB API (network records)