Summary

  • Kompeatelecom Ltd. is best read through the gap between two records: a compact Russian limited-liability company in public company registers and a much larger visible routing footprint around AS59815, AS25299 and legacy AS49908.
  • The strongest public evidence is operational rather than financial. RIPE, RIPEstat, BGP tools, IPinfo, IPregistry, PeeringDB-linked records and Cloudflare Radar all support a live IPv4 ISP footprint, while company-register sources do not show a public revenue base proportionate to that routing visibility.
  • The core economic question is whether recurring customer invoices can pay for more than pass-through bandwidth. The durable margin has to come from installation recovery, support response, local continuity, address management, abuse handling and renewal convenience.
  • The judgment remains conditional because public sources do not disclose customer contracts, churn, actual prices, payroll, field-service cost, equipment age, license scope, operating brand ownership or whether cash is booked in Kompeatelecom itself or in related service companies.

The invoice is the right starting point

The clean way to judge Kompeatelecom is not to begin with its ASN count. It is to begin with one recurring customer invoice and ask what part of the payment is defensible gross margin. A residential or small-business connectivity bill contains at least four pieces that behave differently. The first is bandwidth pass-through: upstream transit, peering, backhaul and any paid access path. The second is access recovery: the router, optical network terminal, drop cable, mast, modem, switch port or installation visit that had to be paid before the first monthly fee arrived.

The third is support labour: calls, ticket triage, abuse complaints, routing changes, CPE replacement, billing exceptions and renewal contact. The fourth is continuity value: the customer's reluctance to move because addresses, phone numbers, CCTV, payment terminals, DNS, mail reputation, office workflows or a known local technician have become embedded in the account.

Public evidence can illuminate only the edges of that invoice. It shows that Kompeatelecom is attached to an active network footprint and to reachable registry contacts. It does not show whether a retail customer pays Kompeatelecom directly, another Trinity-branded operator, a reseller, a building network, a related Donetsk-registered company, or an intermediary. It does not show the tariff, the support SLA, the install subsidy, the payback period or the customer mix. That absence is not a minor data gap. It is the margin question itself.

The most investable version of Kompeatelecom is a regional ISP or wholesale-access operator whose recurring accounts stay because the service is difficult to replace locally. In that version, AS59815 provides reach, AS25299 or related address space preserves legacy customer continuity, and support contacts turn technical familiarity into renewals. The less attractive version is a routing shell or resource holder whose visible address space does not translate into cash in the reported company. In that version, the network can be real and still fail the equity question because revenue, labour and risk sit somewhere else.

The public sources lean toward "real network footprint" but do not yet prove "recurring margin in the named company."

Identity and control boundary

RIPE identifies Kompeatelecom Ltd. as a Russian LIR-associated organisation with the ORG-KL262-RIPE handle, a Dolgoprudny address, phone contacts, an email contact and serviced areas listed as Russia and Ukraine [S01-S03]. RIPE database records tie that organisation to AS59815, AS25299 and AS49908 [S04-S07]. Public company-register aggregators identify the Russian legal entity as OOO Kompeatelekom, with OGRN 1185029019856, INN 5047215681, registration in September 2018, a Dolgoprudny address, a 10,000 ruble charter capital, and Puzin Evgeny Aleksandrovich as director and 100 percent entity in current records [S46-S50]. Several register aggregators also show the entity as active, while at least one flags a record of unreliable legal-address information in the Russian unified company register [S47, S50].

That boundary matters because the network resource record predates or exceeds the simple corporate story. AS25299 was originally registered in 2002, AS49908 in 2009, and AS59815 in 2014, while the current Russian limited-liability company registration visible in company aggregators is from 2018 [S21-S23, S46-S50]. This does not mean the public record is wrong. Network resources are frequently transferred, consolidated, renamed or held through successor companies. It does mean that a buyer or lender should not treat the company registry entry, the LIR record and the historical network footprint as automatically identical economic units.

The control boundary is also complicated by related-party signals. Klerk and Tochka records list Puzin Evgeny Aleksandrovich as associated with several other entities, including names that look operationally relevant to the Trinity, Telephant and local telecom ecosystem [S48, S52]. Those pages are useful because they show a business group context. They do not prove that those companies share cash, employees, physical network assets or customers with Kompeatelecom.

The right conclusion is narrower: public evidence supports a person-linked cluster around telecom and related local operations, but the named company must still be tested as its own contracting, billing and asset-holding entity.

For a recurring-support thesis, that distinction is decisive. If Kompeatelecom controls the customer contracts, support teams, route policy, address resources and brand relationship, then its public routing footprint can support a margin story. If it merely holds registry resources while retail billing and field teams sit elsewhere, then the asset being analysed is closer to an infrastructure-control node than a full ISP operating company. Both can be valuable. They have different risks, debt capacity and due-diligence questions.

Infrastructure evidence is stronger than the company accounts

BGP routing records are the strongest part of the file. The BGP Tools AS page describes AS59815 as an active RIPE-registered eyeball network, with 16 IPv4 originated prefixes, no IPv6 originated prefixes, three upstreams and one downstream, AS25299 [S21]. IPinfo classifies AS59815 as an ISP, reports 25,600 IPv4 addresses and zero IPv6 addresses, shows a consumer-ISP activity pattern, lists three upstreams and shows pingable IPs and router evidence in Russian locations [S28]. IPregistry reports AS59815 as an ISP with 14 IPv4 ranges and no IPv6 range, with upstreams AS52091, AS201776 and AS206810 and downstream AS25299 [S36].

IP2Location independently reports 25,600 IPv4 addresses and zero IPv6 addresses for AS59815 [S40].

The exact counts vary by source because some tools count overlapping aggregate and more-specific announcements differently. That inconsistency is not a reason to ignore the footprint. It is a reason to avoid a false precision claim. The robust point is that multiple independent routing data sets show AS59815 as live, IPv4-only in public route views, and materially larger than a token allocation. The BGP Tools page says it represents 100 /24-equivalent IPv4 units [S21]. IPinfo and IP2Location converge on 25,600 IPv4 addresses [S28, S40]. IPregistry's route-sum figure is higher because its list includes overlapping route objects [S36].

The economic reading is that Kompeatelecom appears to operate or control enough address space to support a real access network, but the public data cannot distinguish occupied subscribers from spare capacity, internal routing, reseller load or dormant historical blocks.

AS25299 adds legacy and continuity value. The BGP Tools page describes it as an active eyeball network, registered in 2002, with 10 IPv4 prefixes and upstream AS59815 [S22]. IPinfo and IPregistry describe AS25299 as Kompeatelecom-linked, show a smaller IPv4 footprint, and report no downstream networks [S29, S37]. Hurricane Electric's AS-set page for AS-TRKMETRO lists both AS59815 and AS25299 as members, reinforcing the idea that the two ASNs belong in one routing policy family [S24]. CIDR Report's AS25299 page also treats AS59815 as the adjacent upstream in its view [S27].

AS49908 is different. The BGP Tools page shows it as allocated under RIPE but not currently in the global routing table, while RIPE database records identify it as TELEPHANT-AS49908 under Kompeatelecom's RIPE organisation [S06, S23]. It may be a legacy or reserved routing identity, not an active revenue engine. That matters because a network with multiple ASNs can look bigger than the live earning surface if old resources remain registered but unused. The article's economic test therefore weights AS59815 and AS25299 much more heavily than AS49908.

Routing shape points to customer access, not pure hosting

The public network signals look more like an access network than a pure data-centre host. BGP Tools labels AS59815 and AS25299 as "eyeball" networks [S21, S22]. IPinfo calls AS59815 a consumer ISP and describes a day-night activity rhythm associated with end-user usage [S28]. Cloudflare Radar lists AS59815 as TRINITY-AS, also known as Kompeatelecom Ltd., and shows a large APNIC-derived estimated population, along with 100 percent IPv4 and zero percent IPv6 in its observed traffic view [S42]. Cloudflare Radar's Russia overview ranks AS59815 among the top Russian ASes by APNIC estimated population in the snapshot viewed [S45].

Those are market signals, not subscriber counts. APNIC-derived population estimates and CDN-observed traffic distributions can be influenced by geography, measurement panels, NAT, proxying, mobile/desktop mix, routing geography and Cloudflare's own customer base. They should not be converted into paying households. Still, the same direction appears across several unrelated sources: AS59815 is not presented as an anonymous tiny hoster. It appears as an eyeball or consumer-access network with meaningful user-side traffic.

The geolocation record is politically and commercially sensitive. RIPE membership lists service areas as Russia and Ukraine [S01]. IPinfo's AS59815 page reports geography led by Ukraine in its activity view, while abuse and IP detail pages associate individual my-trinity hostnames with Russian and contested-region locations [S28, S53-S55]. IPinfo prefix pages and BrowserScan-derived WHOIS displays repeatedly show a my-trinity domain and a geofeed URL in RIPE entities [S30-S35]. Those facts support a service footprint around Russian-registered resources and Ukrainian or Donetsk-linked geography. They do not establish the lawful customer location of any individual account, nor do they resolve control of physical infrastructure in contested territory.

For unit economics, the access-network reading has a clear implication. Consumer and small-business ISPs do not usually win on raw transit resale. They win when local installation knowledge, account memory, reachable repair and migration inconvenience create renewal value. If the network's visible traffic is mostly end-user access, then support labour is not overhead to be minimized blindly. It is part of the product. The danger is that support can also eat the margin if accounts are low-ARPU, bespoke, geographically dispersed, or burdened by old CPE and unstable access paths.

The business model needs standardization

Kompeatelecom's public records support three possible revenue models. The first is retail access under a Trinity or my-trinity service identity, with Kompeatelecom or a related company billing households and SMEs. The second is wholesale or backhaul access, where Kompeatelecom sells connectivity or route reach to other local operators, including AS25299 as a downstream or legacy policy component. The third is resource and operations support: maintaining ASNs, prefixes, abuse contacts, geofeed, routing and technical administration while another entity owns the customer relationship.

The evidence does not let an outside reader choose one model confidently.

Each model has a different margin structure. Retail access depends on monthly recurring charges, installation recovery, router replacement, customer care, bad-debt management and churn. Wholesale access depends on committed information rate, burst pricing, backhaul availability, route quality, dispute resolution and whether the customer can multi-home or switch upstreams. Resource administration depends on scarcity value, LIR competence, abuse handling, documentation and the ability to keep records current. A blended operator can earn from all three, but only if it avoids bespoke work that consumes labour without repeatable fees.

The recurring invoice therefore needs a service map. For each customer class, management should know which cost is variable, which cost is capital recovery, which cost is support, and which cost is strategic retention. A small SME connection with static addresses and working CCTV may be profitable at a higher monthly fee because the customer values continuity. A residential plan with frequent truck rolls and low price competition may be unprofitable even if it adds subscribers. A wholesale relationship may look efficient until a route leak, abuse complaint or payment dispute consumes senior engineering time.

The visible network suggests Kompeatelecom has something to sell other than a commodity connection. It has registered resources, a route policy family, contacts, a recognisable my-trinity naming pattern, and evidence of live usage. The missing proof is whether those assets are packaged into standardized products. A support-heavy ISP can scale if installations, CPE, billing, monitoring and escalation rules are repeatable. It struggles when every account depends on one technician remembering how a custom link was built years earlier.

Pricing must pay back installation before churn

No reliable public tariff sheet was available in the reviewed public record. That absence forces the economics to be framed as a test rather than a reported price conclusion. A recurring plan must first recover any access installation. If a connection requires a technician visit, a new router, roof or building work, a fibre drop, splicing, mast alignment or local permissions, the monthly gross margin must pay that back before the customer churns. If installation is paid upfront, the operator has less payback risk but may face lower conversion. If installation is subsidized, churn and nonpayment become central risk variables.

For a regional ISP, the bandwidth component can be deceptively small or deceptively volatile. If upstream capacity is committed and underused, the next customer may look high margin. If peak-hour congestion forces an upgrade, the same customer may create a step cost. Transit suppliers and adjacent networks are visible in routing data: AS59815's upstreams include Level-MSK, Miranda-Media and GUP DNR UGLETELECOM in multiple sources [S21, S28, S36]. AS25299 appears to depend on AS59815, with some tools also observing MegaFon in peer or upstream context [S29, S37]. These supplier relationships are not cost contracts.

They show where the network reaches the global Internet. The cost of that reach remains private.

The support component is harder to hide. A company can oversell bandwidth for a time; it cannot fake field response indefinitely in a local market. Registry records show reachable phone and email contacts [S01-S03]. That supports the idea of an operator with public operational contactability, but it does not measure repair quality. If customers pay because someone answers and fixes local faults, support is revenue protection. If calls are too frequent because the network is fragile, support is leakage.

The most important pricing question is not the advertised monthly fee. It is contribution after avoidable work. A customer paying a modest recurring fee can be profitable if they install once, renew quietly and require only remote monitoring. A customer paying a higher fee can be destructive if they need repeated site visits, custom routing, manual billing and senior engineer attention. Kompeatelecom's thesis depends on sorting those accounts, not merely adding route announcements or user estimates.

Cost and capital risk sit in old infrastructure and address management

The address footprint has value in an IPv4-constrained market, but address value is not the same as free cash flow. IPv4 resources must be routed, documented, secured, geofed, justified in customer service, and protected from abuse reputation damage. The reviewed public records show extensive IPv4 reliance and little public IPv6 usage. BGP Tools, IPinfo, IPregistry and Cloudflare Radar all point to zero visible IPv6 for AS59815 in their respective views [S21, S28, S36, S42]. IP2Location reports IPv6 blocks for AS25299 while other current routing sources emphasize no IPv6 in active route views [S37, S41].

The conservative reading is that IPv4 remains central to the public operating surface.

That matters because IPv4 scarcity can improve retention and support pricing for customers that need stable addresses. It can also trap the operator in old architectures. NAT, address reassignment, blacklist remediation, reverse DNS, mail reputation and geolocation corrections become operational work. The geofeed references visible in multiple WHOIS and IP pages suggest active geolocation management [S30-S35, S38-S39]. That is a positive sign of resource administration, but it also creates a recurring maintenance obligation.

Capital risk is invisible in the public documents. There is no public plant map, tower list, fibre lease schedule, router inventory, CPE age table, support payroll or colocation contract in the reviewed records. BGP and IP intelligence can show reachability; they cannot show whether equipment is new, redundant, financed, borrowed, locally serviceable or exposed to power and physical-access risk. For a regional ISP, those facts are not footnotes. They define whether a low headline price is sustainable.

The company-register record deepens the uncertainty. Public aggregators show a small charter capital, microbusiness status and, in one source, zero 2024 revenue, expenses and net profit for the registered entity [S47-S51]. Those facts do not prove that the network is uneconomic. Revenue could sit in another related operator, public filings may lag, or a resource-holding entity may not be the retail billing company. But from an investor's perspective the mismatch between routing scale and company-account scale is a red flag that demands reconciliation. The named company cannot be valued from route tables alone.

Suppliers and substitutes are visible enough to frame the negotiation

Kompeatelecom's upstream evidence defines the supplier-pressure side of the model. BGP Tools and IPinfo list AS201776 Miranda-Media, AS206810 GUP DNR UGLETELECOM and AS52091 Level-MSK as upstreams for AS59815 [S21, S28]. IPregistry gives the same broad supplier set [S36]. BGP Tools also shows a larger peer table, including international and regional networks, but the presence of peers is not the same as paid settlement-free peering or usable local capacity for every customer [S21]. The economic issue is whether Kompeatelecom has enough upstream diversity to avoid outages and enough purchasing power to defend gross margin.

AS25299 appears more dependent. BGP Tools lists AS59815 as its upstream, and IPinfo shows AS59815 as the only upstream in its page [S22, S29]. IPregistry lists AS31133 and AS59815 in an upstream context for AS25299, creating a discrepancy that should be checked with live route data before any hard conclusion [S37]. The practical inference is that AS25299 is not the independent profit centre; it is a policy or legacy access component tied to Kompeatelecom's broader route family.

Customers have substitutes. A small business can move to a national mobile operator, a fibre incumbent, a larger regional carrier, satellite backup, a managed cloud service, or a different local WISP or fibre provider. Larger wholesale customers can multi-home, lease alternative transport or move traffic to a stronger upstream if they control their own ASN. The substitute threat is strongest where Kompeatelecom sells only undifferentiated bandwidth. It is weaker where the customer depends on local repair, stable addresses, site-specific installation, existing wiring, or a trusted support relationship.

This is where support becomes strategic. A larger carrier may offer broader backbone resilience but worse local accountability for a small site. A cloud provider may offer better application infrastructure but cannot replace a physical local access line. A national mobile operator can be a cheap backup but not always a stable primary for fixed business workflows. Kompeatelecom's margin can survive if customers are buying continuity, not just megabits. It is exposed if customers can replicate the service with a SIM card or a standard fibre package.

Customer concentration is unknowable from public routes

The public record does not disclose customer count, ARPU, churn, bad debt or contract concentration. Routing scale cannot solve that. A /20 can serve many households behind NAT, a handful of business customers, a reseller, internal infrastructure, or a mix. Cloudflare Radar's APNIC-derived population estimates for AS59815 are large enough to be notable [S42, S45], while AS25299's estimate is much smaller [S43]. Those figures are useful as attention signals. They are not a customer ledger.

Concentration risk can hide behind stable routes. A provider might have thousands of low-paying household accounts and low enterprise dependence. It might have one or two wholesale relationships that generate most traffic. It might carry related-party traffic from linked entities. It might have inherited address resources that make the network look broad even though billed customers are elsewhere. The public evidence supports none of those alternatives conclusively.

The company-register mismatch makes this issue sharper. If public register aggregators are right that the Russian OOO had zero 2024 revenue, then either Kompeatelecom's visible routing footprint is not monetized inside that legal entity, public data is incomplete or stale, or the economically meaningful customers are attached to a related company [S48-S51]. A potential buyer should demand bank statements, invoices, customer ageing, contract lists and tax-account reconciliation before assigning recurring-revenue value to the named entity.

The best concentration test starts with the top twenty recurring invoices. For each, ask who is the contracting entity, what service is sold, what infrastructure is used, how long the customer has been active, what the gross margin is after upstream and support, and what would happen if the customer moved. If the top accounts are diverse, standardized and sticky, the public routing footprint becomes economically meaningful. If the top accounts are related-party, bespoke or loss-making, the public routing footprint is more a technical asset than a scalable company.

Renewal mechanics decide whether support is margin or leakage

Recurring access revenue looks stable from a distance because the bill repeats. The inside economics are less forgiving. A customer renews because the line works, because the provider is reachable, because switching is annoying, because the service is bundled with addresses or local knowledge, or because there is no better local substitute. Those reasons are not equal. A customer who renews because the provider solved a difficult installation can be attractive if the account now runs quietly. A customer who renews only because the provider repeatedly performs unpaid emergency work can look sticky while destroying labour margin.

Kompeatelecom's public evidence makes this distinction especially important. The route footprint supports a real network thesis, and the RIPE contact record supports public operational reachability [S01-S03, S21, S28]. But the company-register evidence does not show enough public revenue to assume that support labour is being monetized inside the named entity [S48-S51]. If a recurring invoice exists, it should be decomposed into support contribution. That means recording how many tickets, calls, abuse notices, billing exceptions, replacement devices and field visits were attached to the invoice during the last twelve months.

A monthly fee that survives this support ledger is real margin. A monthly fee that depends on unpriced interventions is deferred loss.

The renewal process should also distinguish avoidable and unavoidable support. Unavoidable support includes network-wide incidents, upstream failures, planned maintenance communication, abuse contact compliance and occasional equipment replacement. Avoidable support includes poor installation notes, undocumented customer premises equipment, manual billing, weak router templates, bad reverse-DNS hygiene, stale geolocation data, and custom promises made by one technician. The first category is part of running an ISP. The second category is a process problem.

A small regional operator can compete with larger substitutes through faster local response, but only if the response is repeatable and priced.

The public IPv4 dependence increases the value of good support. Customers using stable addresses for cameras, payment terminals, remote access, small servers or whitelisted business systems often underestimate migration friction until something breaks. Kompeatelecom's visible IPv4 footprint and my-trinity naming pattern indicate that address management is part of the operating surface [S28-S35, S56]. That can create renewal power. It can also create expensive exceptions if customers require bespoke reverse DNS, reputation cleanup or manual geolocation corrections.

The operator's job is to make those services explicit, charge for the premium cases, and avoid turning every technical exception into a free favour.

The most useful internal metric would be gross margin after ticket cost, not gross margin after transit cost. Transit is only one input. A low-support household account can subsidize network fixed costs. A high-support SME with static addresses can still be profitable if priced as a managed service. A wholesale account can be efficient if route policy is standardized and abuse escalation is clear. A related-party or bespoke account can be dangerous if it consumes engineering time without invoice discipline.

That is why the article's conclusion is conditional: Kompeatelecom's reachability is valuable only when it is converted into priced continuity.

Wholesale access needs its own proof of contribution

The public routing evidence also leaves open a wholesale-access interpretation. AS59815 has upstreams and peers visible in third-party routing views, and AS25299 appears as a downstream or closely related route-family member [S21, S22, S28, S36]. That structure could support retail access, wholesale backhaul, related-network transit, or a mixture. The economics of wholesale access differ from retail. Fewer customers can produce more traffic, but one customer dispute, one unpaid bill or one bad route policy can remove a large part of contribution.

A wholesale contract should be tested on committed revenue, burst terms, route filtering responsibility, abuse escalation, payment discipline and termination rights. If Kompeatelecom sells a downstream operator full routes or transport reach, the invoice must cover both upstream cost and the senior engineering time required to keep the relationship clean. If the downstream is related-party, the same discipline is still required; otherwise group traffic can occupy scarce capacity while reported company revenue remains weak.

If AS25299 is primarily a legacy policy component rather than an external customer, management should not count it as independent market demand.

The supplier side creates another contribution test. AS59815's listed upstream mix suggests some redundancy, but redundancy is valuable only if contracts, physical paths and operational responsibility are actually distinct [S21, S28, S36]. Two logical upstreams that share a vulnerable facility, power source or political risk are less useful than the route table implies. A wholesale customer paying for continuity will care about those hidden dependencies. A recurring wholesale invoice should therefore be accompanied by private evidence of path diversity, maintenance windows, incident communication and route-security practice.

Wholesale can be attractive because support is concentrated. It can also be fragile because negotiation power moves to the customer. A downstream network can demand discounts, move traffic to another upstream, or threaten multi-homing if Kompeatelecom cannot prove reliability. The investable case is not "Kompeatelecom has address space." The investable case is "Kompeatelecom uses its address space, local reach and upstream relationships to sell repeatable wholesale or retail continuity at a contribution margin that survives support and supplier costs."

Regulatory and geopolitical risk is not background noise

The RIPE member page lists Russia and Ukraine as serviced areas [S01]. IPinfo and Cloudflare-derived signals associate traffic and geography with Russia, Ukraine and the wider contested-region network environment [S28, S42-S45]. This creates regulatory and geopolitical exposure that ordinary regional-ISP analysis cannot ignore. Licensing, sanctions, payment rails, equipment supply, fibre access, power reliability, law-enforcement demands, data-retention rules, address registration and international interconnection can all change faster than customer demand.

The company-register address flag is also material. DaMIA and E-Ecolog report a Russian unified-register entry concerning unreliable information for the legal entity's address [S47, S50]. That does not by itself prove operating failure, but it is a control and compliance signal. If the legal address is disputed or considered unreliable, counterparties may face extra know-your-customer questions, bank friction, procurement hesitation or regulatory correspondence risk. For a support-driven ISP, administrative reachability is part of reliability.

RIPE and abuse contacts remain reachable in public records [S01-S03]. That is positive. Abuse handling is not optional for an ISP with visible IPv4 space. IPinfo flags VPN and BitTorrent observations on AS pages [S28, S29], and AbuseIPDB pages show specific Kompeatelecom-linked IPs with individual abuse reports, including low-confidence old reports and one higher-confidence FTP-bruteforce cluster on an AS25299 address [S53-S55]. These signals should not be exaggerated into a network-wide security verdict. They do show why abuse response, customer identification and address hygiene belong in the margin model.

Equipment and upstream supply are another geopolitical risk. If routers, optics, spares or vendor support become hard to obtain, a network can keep routing while service quality deteriorates. Public sources do not identify Kompeatelecom's vendors, stock levels or maintenance contracts. The private due-diligence question is whether the operator can repair faults quickly under local constraints. A recurring invoice is durable only if the customer believes the operator can keep the service alive when outside conditions worsen.

Unofficial signals should be used but not overread

Unofficial market signals around Kompeatelecom are useful because official financial disclosure is thin. IPinfo's activity view suggests a consumer-ISP rhythm for AS59815 [S28]. Cloudflare Radar's AS page and Russia overview suggest that AS59815 is visible in end-user population estimates and HTTP traffic observations [S42, S45]. Reverse-DNS and hostname pages show a repeated my-trinity naming pattern across individual addresses [S53-S56]. AbuseIPDB reports show real-world third-party observations of traffic from specific IPs [S53-S55]. These are the kinds of signals a local ISP leaves when it is actually carrying users.

The limits are equally important. Crowd-sourced abuse reports can be stale, biased or about compromised customer machines rather than operator conduct. CDN traffic estimates may be shaped by measurement methodology. Hostnames may reflect old naming conventions. Search visibility can be low for a perfectly functional local provider. A lack of reviews is not proof of satisfaction, and a handful of abuse entries is not proof of poor service.

The most useful unofficial signal is the consistency of the pattern: multiple sources independently connect Kompeatelecom to TRINITY-AS, my-trinity hostnames, active IPv4 prefixes, consumer or eyeball network classification, and upstream relationships [S21, S28, S36, S42]. That consistency supports a live-service thesis. It does not settle the commercial thesis.

For management, unofficial signals can become operating metrics. Abuse reports per thousand active customers, reverse-DNS accuracy, geofeed freshness, pingable-router health, ticket resolution time, repeated support contacts per account and churn after outages are all measurable. Public sources give only fragments. A disciplined operator would turn those fragments into a monitoring dashboard and price the service accordingly.

What would change the judgment

Several facts would change the view quickly. The first is revenue reconciliation. If Kompeatelecom can show recurring customer invoices, bank receipts and tax filings matching the visible network, the public routing footprint becomes a credible earning base. If the cash sits in related companies, the analysis must move to the actual contracting entities. If revenue is immaterial, then the company is primarily a resource and network-control vehicle.

The second is gross-margin evidence by product. A table showing monthly recurring revenue, upstream cost, access lease, power, field visit cost, support hours, install subsidy and churn by customer class would answer the core economic question. A profitable local ISP does not need hyperscale margins. It needs a predictable spread after the costs that actually move with customers.

The third is support quality. Public contactability is not enough. Evidence that would matter includes ticket data, outage logs, response times, first-time fix rates, spare inventory, escalation rules, abuse closure times and customer renewal reasons. If customers stay because support is fast and knowledgeable, Kompeatelecom can defend price. If support is ad hoc and person-dependent, churn and labour risk rise.

The fourth is asset control. A buyer needs to know who owns or leases fibre, radio sites, routers, switches, CPE, address resources, domains, billing systems and customer databases. RIPE entities show administrative control over network resources [S02-S07]. They do not show ownership of physical plant or software systems.

The fifth is legal and regulatory clarity. The address-reliability flag, Russia-Ukraine service-area record, related-party company cluster and contested-region signals all require plain documentation [S01, S47-S52]. That does not make the business uninvestable. It means the discount rate should stay high until contracts, licenses, bank access and governance are understood.

The conditional conclusion

Kompeatelecom has enough public network evidence to matter. AS59815 is repeatedly visible as an active, IPv4-heavy eyeball or consumer-access network. AS25299 adds a legacy route family. The my-trinity naming pattern, RIPE contact records, geofeed references, upstream list and third-party traffic observations all point to real operations rather than a paper-only company. A pure commodity reading misses the likely customer value: local continuity, stable access, address management and reachable support.

But the public company evidence prevents an easy positive conclusion. The named Russian legal entity looks small in company-register sources, and at least one source reports zero 2024 revenue, expenses and profit [S48-S51]. Other sources flag legal-address reliability concerns [S47, S50]. Related-party signals suggest the economic activity may be spread across a group, not neatly inside Kompeatelecom [S48, S52]. Those facts do not negate the network. They make the boundary of the investment asset uncertain.

The operating mandate is therefore precise. Kompeatelecom must turn reachability into recurring margin. It should separate bandwidth pass-through from support contribution, price installations to recover before churn, standardize customer classes, document route and address management, and prove that support labour lowers churn rather than consuming the gross margin. The public route footprint is the opening evidence. The investable value depends on whether each recurring invoice survives that cost test.

Sources