Summary

  • AS51035 (UFA-AS), the network behind the Ufa-branch NOC name, is single-homed to AS9049 — its own parent's transit system — with zero downstreams and zero peerings across four independent BGP views.
  • Its registry paperwork is frozen: the aut-num was last modified 2018-09-04, the as-set AS-UFA on 2019-12-17 still describes a pre-2011 "CJSC" legal form, and the NOC role object was last modified 2019-10-24 with a Perm postal address.
  • The only datable routing-footprint change in the retained history is a two-prefix step around July 2025; peer count, upstream count and address totals stayed flat into 2026.
  • A September 17, 2026 traceroute shows the Ufa access routers reachable, confirming live operation — but no retained source states a Ufa or Bashkortostan market-share figure or any branch-level financials.
  • Group-level Q1 2026 results (net profit up roughly 286x to ~2.58bn RUB on 27.65bn RUB revenue) cannot be attributed to the branch; the evidence distinguishes operating state from attribution and financial performance without merging them.

The State Difference Worth Measuring

Every company has paperwork that lags reality. The interesting question about the network registered as AS51035 is the reverse: the paperwork has been frozen for years while the operating evidence shows a network that is alive, small, and entirely dependent on a single connection to its own corporate family. That combination is more informative than either fact alone.

The subject itself needs disambiguation before any conclusion. "Network Operation Center JSC ER-Telecom Holding Ufa branch" is not a separately identifiable Ufa legal entity in any retained source. It is a RIPE role object — an administrative label in a registry database — that administers the autonomous system AS51035, historically named UFA-AS. The role object carries a Perm postal address (shosse Kosmonavtov, 111, 614099), a Ufa-branded NOC mailbox and a Dom.ru abuse mailbox (the mailbox addresses themselves are withheld at the public tier), and it was created on 2011-01-25 and last modified on 2019-10-24. That record is reproduced in third-party mirrors of the RIPE database (https://whois.ipip.net/AS51035). BTW examined this attribution gap in a prior briefing and found the same divergence between the Ufa administrative naming and the Perm corporate reality (https://btw.media/en/ufa-branch-ripe-registry-as51035-attribution). This report goes beyond that prior attribution question to the operating layer: what the network's routing shape and its few observable changes say about the branch's economic position.

One evidence limitation must be stated up front. The authoritative RIPE database query interface did not return the AS51035 object content on retrieval — the supplied URL resolved only to generic documentation text (https://apps.db.ripe.net/db-web-ui/query?searchtext=AS51035). Every registry-derived fact in this report therefore rests on third-party mirrors of the same upstream registry. Mirror consistency establishes internal agreement, not independent verification, and caps how firmly the report can speak about the authoritative record.

The Routing Shape: One Upstream, Zero Peers, Zero Downstream

The single most consequential fact about AS51035 is its topology, because topology is the cheapest observable proxy for network independence.

Four independent BGP views agree. Hurricane Electric's ASN page shows exactly one BGP peer in both IPv4 and IPv6 — AS9049, JSC "ER-Telecom Holding", the group's transit system — and 57 originated prefixes (52 IPv4, 5 IPv6) (https://bgp.he.net/AS51035). CIDR Report, computing from the routing table rather than Hurricane Electric's collector, shows the same adjacency structure: one upstream (AS9049), zero downstreams, and roughly 73,216 originated IPv4 addresses (about /15.84) with zero transit address space (https://www.cidr-report.org/cgi-bin/as-report?as=AS51035&view=2.0). Qrator Labs classifies the network with one provider, zero customers and zero peerings in both address families, and records 52 IPv4 prefixes totalling about 73,200 addresses (https://radar.qrator.net/as/51035). A fourth view, IPinfo, likewise counts one peer, one upstream and zero downstreams, and classifies AS51035 as a consumer ISP (https://ipinfo.io/AS51035).

What does that shape mean economically? A network with one upstream and no peers buys all of its transit from a single seller — and here the seller is the network's own parent. AS9049 is the ER-Telecom group backbone, registered in PeeringDB under the Dom.ru brand with traffic levels of 5–10 Tbps, a selective peering policy, and presence at multiple Russian exchange points including MSK-IX in Moscow, Ekaterinburg, Saint-Petersburg and Samara, plus W-IX and GNM-IX; the record was last updated on 2026-03-25 (https://www.peeringdb.com/net/17746). PeeringDB carries no network record for AS51035 itself. Absence of a PeeringDB entry is evidence of non-registration, not proof of non-peering, but combined with the four BGP views showing zero peering adjacencies, the reasonable reading is that the Ufa branch has no independent interconnection strategy at all. It is an access network hanging off the group backbone — the group does the peering, the branch does the last mile.

The declared routing policy confirms this is a design, not an accident. The aut-num object declares one import for "ANY" from AS9049 and one export of AS-UFA to AS9049, plus a single documented customer relationship: AS13105, LUKOIL Technology Services GmbH, whose routes AS51035 accepts and to which it announces ANY. That object has not been modified since 2018-09-04 (https://whois.ipinsight.io/AS51035). The as-set AS-UFA — the announcement set behind the network — lists six members: AS51035 itself, AS13105, AS-BRTC, AS204925, AS208352 and AS197725, and its description still reads "CJSC "ER-Telecom Holding" Ufa branch", a legal form the holding abandoned years before 2019. The object was last modified on 2019-12-17 and shows no update since (https://ipv4.bgp.he.net/irr/as-set/AS-UFA). A legacy description in an IRR object is not evidence of anything on its own; frozen member lists plus a frozen import/export policy plus a frozen role object, taken together, describe an operating model that nobody has needed to restate in the registry for seven years.

The origin footprint is small and consumer-shaped. In the GIBIRNet view, updated 25 August 2026, the network's prefixes are labelled overwhelmingly as "PPPoE individual customer" allocations, with one prefix (188.187.230.0/24) labelled as a VoIP network; the view shows one peer and around 50 networks (https://bgp.gibir.net.tr/as/51035). PPPoE labels in a prefix registry are operator-facing descriptions of how address space is used at the edge — individual broadband subscribers, dialled in session by session. That is the fingerprint of a residential access network, not of an enterprise platform or a wholesale carrier.

Prefix counts differ modestly across sources — 50 in the GIBIRNet view, 52 IPv4 plus 5 IPv6 in Hurricane Electric's, 52 in Qrator's, 57 total in Hurricane Electric's headline figures — because collectors observe different subsets of the global table. The differences are collector artefacts, not contradictions; the material point, stable across every view, is the order of magnitude: a network originating roughly 40,000 to 73,000 IPv4 addresses is a city-scale access footprint, several orders below the group backbone that carries it.

The One Datable Change

Against that frozen backdrop, the retained history contains exactly one datable movement. The iamroot.tech ASN history, last updated 2026-07-19, records that before 2025-07-04 AS51035 originated 55 prefixes with 38 subprefixes; after that date it originated 57 prefixes with 40 subprefixes — a step of +2 and +2. Across the same window, peer count (1), IPv4 address total (40,192) and IPv6 totals stayed flat, and no change in peers or exchange-point presence was recorded (https://iamroot.tech/asndatabase/?search=AS51035).

That is the entire observable change surface for the operating network in the retained record: two additional announced prefixes around July 2025, everything else flat. Two readings are possible, and the data does not fully separate them. The change could be the footprint of modest subscriber growth — new PPPoE allocations announced at the edge of an unchanged access model. It could equally be housekeeping — deaggregation for traffic engineering or filtering hygiene, with no commercial meaning at all.

The iamroot dataset is an aggregator history with at least one internal inconsistency (a peers row that conflicts with the peer count shown elsewhere on the same page), so this single source carries medium-high uncertainty. What can be said firmly is the negative finding: nothing in the retained evidence shows a second upstream, a peering session, a downstream customer relationship beyond the legacy LUKOIL entry, or any growth in address holdings, at any point through 2026.

The Network Is Alive — And That Matters

A frozen registry record could describe a decommissioned network. It does not here. On September 17, 2026, IPinfo's ProbeNet measurement platform ran a traceroute from Moscow that entered AS51035 through routers geolocated in Ufa in the 109.195.152.x range — routers 109.195.152.18, .21, .25, .26 and .50 — and the network is classified in that dataset as a consumer ISP holding roughly 40,192 IPv4 addresses with around 144 hosted domains (https://ipinfo.io/AS51035). Whatever the paperwork says, the Ufa access routers were forwarding traffic into the group's backbone eight days before this report's research window.

So the operating state is: live, consumer-facing, single-homed, un-peered, small. The attribution state is: frozen at three registry layers for six to eight years. These are different facts about different layers, and the report keeps them separate deliberately. Registry freeze tells you that no administrative change was declared. Routing freeze tells you that no structural change was observed. Neither tells you whether subscribers are being gained or lost — and that is the economic question the remaining evidence circles without resolving.

The Group Layer: Profits Without a Branch Breakdown

The financial signal that makes this question worth asking sits one organisational level up. Comnews reported on 2026-05-18 that JSC "ER-Telecom Holding" multiplied its net profit roughly 286 times year-on-year in the first quarter of 2026, to approximately 2.58bn RUB, on revenue of 27.65bn RUB (+9% YoY), with consumer (B2C) segment revenue up 18% and business (B2B) revenue up 2% (https://www.comnews.ru/content/245314/2026-05-18/2026-w21/1008/er-telekom-kholding-sotni-raz-priumnozhil-chistuyu-pribyl).

It is tempting to connect a consumer segment growing 18% to a consumer-labelled access network in Ufa. The evidence does not license that connection. The disclosure is group-level: no retained source states a Ufa- or Bashkortostan-specific market position, subscriber count, ARPU, capex allocation or margin for the branch. The 286x profit expansion is a group-wide figure that could reflect debt structure, one-off items, or mix effects anywhere in the portfolio; attributing it to Ufa would be inventing a mechanism the sources do not describe.

What the group result does establish is context: the parent's consumer business is expanding aggressively while its Ufa branch network's observable footprint is flat. Those two facts are compatible with several stories — the branch participating in growth invisibly, the branch being flat while other regions grow, or the branch being managed for cash rather than share — and the retained evidence cannot choose between them.

What the Market Evidence Does and Does Not Say

The retained market-context sources are regional and indirect. A TMT Consulting ranking of Russian fixed broadband providers, published for the first quarter of 2024, provides an industry-wide benchmark of provider scale and market structure in the period before the group's 2025–2026 financial results (https://tmt-consulting.ru/wp-content/uploads/2024/06/%D0%A2%D0%9C%D0%A2-%D1%80%D0%B5%D0%B9%D1%82%D0%B8%D0%BD%D0%B3-%D0%A8%D0%9F%D0%94-1q2024-1.pdf). It does not, in the retained excerpts, state a Ufa- or Bashkortostan-specific market-share figure for ER-Telecom. Two Ufa local-news items — one from April 2026 on network coverage in populated localities of the region (https://ufa-news.net/society/2026/04/20/525395.html) and another regional item on connectivity in populated places (https://ufa.bezformata.com/listnews/naselyonnih-punktah/163811903/) — establish that broadband coverage in Bashkortostan's smaller settlements remains a live local topic in 2026, and that networks including the ER-Telecom footprint are part of that public conversation. Neither item quantifies the branch's position.

The honest summary is therefore negative in a precise way: the branch's market position in Bashkortostan is not stated in any retained source, and no source permits even a directional inference. A single-homed consumer access network with frozen paperwork is consistent both with a strong incumbent running on an unchanged architecture and with a secondary player being carried by a parent's backbone. The routing table cannot tell those stories apart; only commercial disclosure can.

Evidence Boundaries

Three boundaries cap this report's conclusions. First, the authoritative registry record was not directly retrievable; all registry facts rest on mirrors. Second, topological "peer" and "provider" labels in BGP data describe adjacency, not commercial contracts — the single upstream could carry commercial terms that no public source documents. Third, the group financials are group-level and the market-context sources are dated or non-quantitative; nothing bridges them to branch-level economics.

Within those bounds, the findings are: operating state live and unchanged in structure; registry state frozen; one two-prefix movement in mid-2025; no independent interconnection; no branch-level financial or market-share evidence in any retained source.