Mobile operator · Ukraine

Kyivstar ASN, MCC/MNC and IP prefixes

Kyivstar is a mobile network operator in Ukraine, part of VEON. It routes traffic through 3 autonomous systems (AS15895, AS12421, AS12530), which announced 47 prefixes at our last probe, and its SIMs carry MCC/MNC 255-03.

ASNs
3
Prefixes
47
Reviewed
September 2026
Country
Ukraine (UA)
Parent group
VEON
ASNs
AS15895, AS12421, AS12530
MCC / MNC
255-03
Network generations
4G LTE, 5G (testing)
ASNs confirmed
3 of 3
Announced prefixes
47 at probe on 2026-09-06
Official site
kyivstar.ua

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.
Kyivstar autonomous systems
ASNHolder (RIPEstat)RoleAnnouncedIPv4 prefixesIPv6 prefixesEvidence
AS15895KSNET-AS "Kyivstar" PJSCPeeringDB: Kyivstar · NSPMobile networkconfirmedyes452source · RIPEstat · PeeringDB
AS12421GT-Fiber "Kyivstar" PJSCFixed-lineconfirmedno00source · RIPEstat
AS12530GoldenTelecom-Ukraine "Kyivstar" PJSCFixed-lineconfirmedno00source · RIPEstat

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.
Kyivstar MCC and MNC
MCC-MNCMCCMNCSource
255-0325503en.wikipedia.org/wiki/Mobile_network_codes_in_IT

About Kyivstar

Kyivstar is a mobile operator in Ukraine and a subsidiary of VEON. The registry records AS15895, held by Kyivstar PJSC under the name KSNET-AS, as the ASN carrying its mobile network, alongside two fixed-role ASNs of the same holder, AS12421 and AS12530. Its MCC/MNC is 255-03.

The registry lists three ASNs for Kyivstar. AS15895 holds the documented mobile role and is the only one announcing routes, with 45 IPv4 prefixes against 2 IPv6 prefixes at the last probe. PeeringDB records that number under the name Kyivstar with the network type NSP. AS12421, registered as GT-Fiber, and AS12530, registered as GoldenTelecom-Ukraine, sit with the same holder organisation, carry a fixed role, and announced no prefixes at all. The registry holds no PeeringDB entry for either of those two.

An address whose origin ASN is AS15895 is routed by Kyivstar, and the registry documents that number as the mobile network, so it is the one to look for when attributing the operator's mobile traffic. The IPv6 count is small next to the IPv4 count, so nearly all of what this ASN originates is IPv4. AS12421 and AS12530 are recorded as fixed rather than mobile and announce nothing, so an address is unlikely to trace back to them. An origin ASN identifies the operator, not the service a subscriber is on.

Research note. AS15895 is the announced Kyivstar network (PeeringDB name Kyivstar, website kyivstar.ua, NSP, as-set AS-KYIVSTAR). AS12421 (RIPE descr: Golden-Fiber Project FTTB) and AS12530 (ex Golden Telecom Ukraine / SvitOnline) are held by the same org ORG-KG8-RIPE but RIPEstat reports them as not announced. Wikipedia MCC 255 table: MNC 03 operational (GSM/UMTS/LTE/5G 3500); MNC 02 listed as not operational (former Beeline/URS, absorbed by Kyivstar) so dropped; MNC 05 withdrawn; MNC 707 status unknown; candidate MNC 67 and 68 do not appear in the table and were dropped. Kyivstar is a VEON subsidiary (veon.com); kyivstar.ua/about also names Kyivstar Group Ltd (Nasdaq: KYIV) as the direct parent. 5G page says it is still testing in Lviv, Kharkiv, Borodianka, Kyiv.

Check whether an IP belongs to Kyivstar

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.
Origin ASN of an address
curl -s "https://stat.ripe.net/data/prefix-overview/data.json?resource=203.0.113.9" | jq '.data.asns'
Routes registered under AS15895
whois -h whois.radb.net -- '-i origin AS15895' | grep ^route

Questions

What is Kyivstar's ASN?
The registry records three. AS15895, under the holder name KSNET-AS Kyivstar PJSC, is the announced mobile network. AS12421 and AS12530 belong to the same holder with a fixed role, and neither announced any prefixes at the last probe.
What is the MCC/MNC of Kyivstar?
Kyivstar is recorded under MCC 255, the country code for Ukraine, with MNC 03. That is the only MCC/MNC pair the registry holds for the operator; other network codes once associated with the company are not carried here as operational.
Is an IP from AS15895 a mobile IP?
AS15895 is recorded with a mobile role, so an address originating there is routed by Kyivstar's mobile network. The registry cannot confirm the access type of any single address, because one operator ASN can carry more than one kind of service.

Where Kyivstar meets other networks

PeeringDB records Kyivstar as a participant at internet exchanges in 4 cities. Each city page lists the exchanges there and the other networks present.

Network cities in Ukraine: Kyiv, Kiev, Lviv, Kharkiv, Odessa.

Sources

Operator and registry pages used for this entry, followed by the RIPEstat Data API (holder, announced prefixes) and the PeeringDB API (network records).

  1. [1]https://kyivstar.ua/en
  2. [2]https://kyivstar.ua/about
  3. [3]https://kyivstar.ua/4g
  4. [4]https://kyivstar.ua/5g
  5. [5]https://www.veon.com/
  6. [6]https://www.veon.com/kyivstar
  7. [7]https://www.peeringdb.com/api/net?asn=15895
  8. [8]https://stat.ripe.net/data/as-overview/data.json?resource=AS15895
  9. [9]https://stat.ripe.net/data/as-overview/data.json?resource=AS12421
  10. [10]https://stat.ripe.net/data/as-overview/data.json?resource=AS12530
  11. [11]https://rest.db.ripe.net/ripe/aut-num/AS12421.json
  12. [12]https://rest.db.ripe.net/ripe/aut-num/AS12530.json
  13. [13]https://en.wikipedia.org/wiki/Mobile_network_codes_in_ITU_region_2xx_(Europe)
  14. [14]https://stat.ripe.net/docs/02.data-api/
  15. [15]https://www.peeringdb.com/apidocs/

ASN and prefix data describe how the operator's networks are registered and announced. They do not identify an individual subscriber or where a device is, since carriers route traffic from many areas through shared gateways.