Summary

  • The economic incentive is straightforward: EKSINTECH can earn defensible recurring revenue only when a customer buys continuity, address-resource administration, routing support and service accountability, not when it simply passes imported equipment, scarce IPv4 resources or upstream capacity through a thin margin. Public evidence shows both sides of that trade. A court record describes a 2023 sale of nine uninterruptible power-supply blocks to another telecom company for UAH 3.33 million including VAT, while 2026 tenders show smaller recurring or support-style services for internet access, IPv4 block support and autonomous-system resource administration.
  • The Elias Ward judgment is cautiously constructive but not yet high-conviction. EKSINTECH appears operationally relevant: public registries connect it to EDRPOU 39434872, a registered Ukrainian limited-liability company in the Lviv region; routing databases tie the business to AS3255, UARNET-AS, and a broad set of IPv4 and IPv6 resources; the company’s own site claims national nodes, more than 100 Gbit/s of external capacity and 24/7 support. The economic record is weaker than the infrastructure record: reported 2025 revenue of UAH 261.2 million and net profit of UAH 10.5 million imply a thin 4.0% net margin, and reported revenue per employee fell sharply as headcount expanded.
  • The case turns on conversion. If EKSINTECH can attach managed support, resource stewardship, monitoring, automation and uptime obligations to its network relationships, it can turn wartime resilience demand into repeat revenue. If the growth is mainly equipment resale, temporary IP-address leasing, supplier-dependent bandwidth and one-off public procurements, the company remains useful but exposed: customers can switch providers, universities and utilities can insource some resource administration, and capital or currency shocks can absorb much of the margin.

The Incentive Hidden Inside A Single Project

Start with the customer project rather than the company description. In the public court record for case 380/4522/24, EKSINTECH appears as the supplier in a transaction with TzOV "Biznes i Technologii". The disputed tax invoice related to a 13 October 2023 supply agreement and an appendix under which EKSINTECH was to deliver nine uninterruptible power-supply blocks for UAH 3,329,748 including VAT. The buyer paid the amount on 22 November 2023. The tax authority blocked registration of the invoice, EKSINTECH challenged the decision, and the first-instance court ultimately ordered the tax invoice registered.

That is not a small anecdote. It is the cleanest public window into the company’s unit economics because it shows why the headline revenue number cannot be read as software-like or even as purely telecom-service revenue. An uninterruptible power-supply sale may be operationally important for a network operator in wartime Ukraine. It may also be a rational sale to a neighboring carrier or related infrastructure buyer that needs backup power. But it is still hardware-heavy.

Unless EKSINTECH controls installation, maintenance, monitoring, replacement cycles, procurement lead time, financing or support after delivery, the economic value retained by EKSINTECH is not the whole UAH 3.33 million. The retained value is the gross margin after acquisition cost, import or supplier cost, working-capital carry, logistics, warranty risk, engineer time and tax timing.

That distinction matters because Ukraine’s connectivity market is full of urgent resilience needs. Providers, public bodies, universities, research institutes, utilities and smaller carriers need backup power, fiber repair, IPv4 stewardship, routing support, transit, domain administration, anti-abuse response and uptime during power cuts. A company with technical staff and network reach can sell all of those. Yet those services do not have the same economic quality. Passing a UPS or router from supplier to customer can create a large invoice with little durable customer lock-in.

Managing the customer’s routing, address resources, redundancy, abuse handling and renewal calendar can create a much smaller invoice with more repeatability.

The best reading of EKSINTECH is therefore not "regional ISP" in the narrow consumer sense. The public footprint points to a mixed operator: part backbone and transit network, part internet-access provider for institutions, part IP-resource and RIPE-administration intermediary, part systems-support contractor, and part hardware or resilience-equipment supplier. That mix can be valuable. It can also blur the quality of revenue. A buyer, creditor or customer should not ask only whether EKSINTECH is growing. The sharper question is whether the company is moving revenue from pass-through toward recurring managed service.

Identity, Control Boundary And What The Public Record Can Prove

The legal identity is clear enough for operating analysis. Ukrainian business registries list the company under EDRPOU code 39434872, registered on 9 October 2014, with a statutory capital of UAH 10,000, a Lviv-region address in Ternopillya village, and the main activity 61.10, wired telecommunications. Registry pages identify Olena Urban as director and show ownership divided among Serhiy Osiechkin, Olena Urban and Ivan Osiechkin, with Serhiy Osiechkin recorded as the 60% participant and ultimate beneficial owner in several public summaries. The legal form is a limited-liability company.

The network identity is older and more complex. AS3255, UARNET-AS, is widely visible across routing databases. Several sources show AS3255 as allocated in 2001 and tied to Ukrainian Academic and Research Network heritage. RIPE-derived records now connect the organisation handle ORG-LE141-RIPE to LLC EKSINTECH, list the company as a local internet registry, and show the same EDRPOU code 39434872. IP databases and routing mirrors describe AS3255 as EKSINTECH, UARNET-AS or UARNet-Eksintech. They also report a large route table, one large IPv6 allocation and many downstream networks.

That creates a useful but sensitive boundary. It would be wrong to infer that the 2014 legal entity personally built all AS3255 infrastructure from 2001. It would also be wrong to ignore the current evidence connecting EKSINTECH to the present routing operator and LIR role. The practical conclusion is narrower: EKSINTECH now sits on or administrates a significant network position connected with the UARNET routing system, but the historical asset trail should be treated as a question unless ownership-transfer documents, contracts or regulator records are produced.

The official company site supports the operating picture. It markets EKSINTECH as an internet-access provider for business, claims more than ten years in the market, says it has a presence in all regional centers, says its external-channel capacity exceeds 100 Gbit/s, names international upstreams and exchange points, describes 10 Gbit/s ports and a 10 Gbit/s direct channel to the Polish academic network PIONER, and says its main nodes are connected by 10 Gbit/s links in a ring topology.

It also claims three 10 Gbit/s fiber links to UA-IX and lists customer categories including higher state authorities, universities, National Academy of Sciences institutions, industrial companies, banks and education institutions.

Those claims are plausible against the routing evidence, but they are company statements and should be weighted accordingly. UA-IX’s public member list independently shows EKSINTECH as a participant with AS3255 and an exchange address. Cloudflare Radar identifies AS3255 as UARNET-AS in Ukraine and gives an estimated population of roughly 421,000 users. IPinfo, IPRegistry, ipapi.is, BigDataCloud, IPLocate and WhoisFreaks all identify AS3255 as an ISP or network tied to EKSINTECH or UARNet.

The numbers differ across data vendors, which is normal for BGP-derived commercial datasets, but the direction is consistent: this is not a shell with a brochure. It is attached to visible internet infrastructure.

Revenue Is Real; The Margin Still Needs Explanation

The strongest financial point is that public registry aggregators report material revenue. Opendatabot’s company profile shows 2025 revenue of UAH 261.2 million, up from UAH 222.0 million in 2024 and UAH 248.8 million in 2023. It reports 2025 net profit of UAH 10.5 million, up from UAH 2.8 million in 2024 but close to the UAH 9.4 million reported for 2023. Assets rose to UAH 91.7 million in 2025 from UAH 55.8 million in 2024, while liabilities rose to UAH 35.2 million from UAH 20.3 million. Reported headcount rose to 141 in 2025 from 78 in 2024 and single digits in 2022 and 2023.

Those figures make the company investable enough to analyze, but not enough to call it durable. The reported 2025 net margin is only about 4.0%. That is acceptable for a regional infrastructure and services business in a difficult wartime market; it is not the margin profile of a software platform or a highly protected recurring-data service. The reported revenue per employee fell from about UAH 2.85 million in 2024 to about UAH 1.85 million in 2025. That decline could be benign if EKSINTECH hired ahead of demand, brought field support in-house, expanded resilience coverage, or absorbed staff from a network transition.

It could also point to lower utilization, more labor-intensive service, or greater hardware pass-through in reported revenue.

The balance-sheet movement points in the same direction. Assets rose by roughly 64% from 2024 to 2025, while liabilities rose by about 73%. Even after the increase, liabilities represented about 38% of assets, not an obviously distressed level. But the company’s working-capital needs are likely real. Hardware purchases, UPS blocks, routers, optical equipment, licenses, IP resource fees and upstream connectivity often require supplier payments before customer receipts. Public-sector buyers frequently pay after service delivery.

The ICMP procurement record, for example, states 100% postpayment for service provided, with payment for the previous month due by the 15th of the current month. That timing is normal; it still places cash discipline on the provider.

The court dispute adds another layer. EKSINTECH successfully challenged a tax-invoice registration refusal related to the UPS sale, and the court held that the supplied documents were sufficient. That is positive as a legal outcome. Economically, however, it shows that even a paid transaction can trap administrative effort and tax timing. In a thin-margin service-and-hardware business, invoice registration, VAT treatment and documentary proof are not accounting footnotes; they shape cash conversion.

What Pricing Can Be Seen In Public

EKSINTECH’s private commercial tariffs are not fully public. The official site emphasizes business services, flexible handling, personal managers and 24/7 support, but it does not disclose a standardized price card for enterprise internet, transit, IP resource administration or managed support. The pricing evidence therefore comes from tenders and court records.

The largest 2026 tender visible in the public procurement trail is the ICMP internet-access procurement. The expected value was UAH 810,000 including VAT for internet-provider services from 1 April 2026 to 31 December 2026, and Clarity records a signed contract with EKSINTECH for UAH 742,500. The tender was a one-service procurement for provider services, with public budget funding and 100% postpayment. If one treats the signed contract as covering nine months, it implies roughly UAH 82,500 per month including VAT for the buyer’s required service package.

The public page does not prove the circuit size, SLA, redundancy, installation obligations or included support, so the monthly figure cannot be benchmarked cleanly. But it establishes that EKSINTECH can sell institutional internet service at a meaningful, repeated monthly invoice.

The smaller tenders show a different pricing band. YouControl’s tender table lists a UAH 460,080 Ukrenergo contract in May 2026 for use and technical support of two IPv4 /24 address blocks, a UAH 20,860 Radio Astronomy Institute contract for provider services, a UAH 6,588 Carpathian National University contract for registration and annual support of independent resources around AS31145 and RIPE NCC, and a UAH 38,800 Carpathian National University electronic-communications contract. These are not large relative to reported revenue, but they are strategically revealing.

IPv4 block support and autonomous-system administration are not commodity home broadband. They require registry knowledge, route hygiene, documentation and customer trust.

The court-documented UPS transaction sits in another category. UAH 3.33 million including VAT is larger than several of the individual service tenders, but the economics are likely less recurring. It may reveal procurement capability, supplier access and trust among telecom customers. It does not by itself reveal recurring margin. The right adjustment is to remove the hardware cost from the invoice, then ask what remains: installation margin, financing spread, project management fee, warranty reserve and possible support attachment.

That is the central unit-economic test. If a UAH 3.33 million hardware project leads to a multi-year managed-power and uptime contract, it can be a customer-acquisition event. If it is a one-off resale, it increases revenue volatility and consumes working capital. If a UAH 6,588 RIPE-support contract anchors a university’s ongoing resource-administration relationship, it can be sticky despite its small amount. If it is just annual paperwork with no operational dependency, it is replaceable by in-house staff or another LIR. EKSINTECH’s future quality depends less on the invoice size than on the support attached to each invoice.

The Cost Stack: Bandwidth, People, Power, Hardware And Compliance

EKSINTECH’s cost structure is likely mixed. The network side carries recurring capacity, colocation, power, fiber, equipment, maintenance and routing operations. The public site describes external channels, exchange links, upstreams, ring topology and nodes in regional centers. Those are not free claims to operate. International capacity, exchange ports, router upgrades, optical gear, generators, batteries and field service all tie costs to currency, energy reliability and replacement cycles.

People became more important in the 2025 numbers. A move from 78 to 141 employees in one year means a larger fixed-cost base unless much of the staff is temporary or contracted. The revenue increase of 17.7% did not keep pace with headcount growth, which is why revenue per employee fell. That does not condemn the company; in network services, hiring engineers and support staff can precede revenue if a company is expanding coverage or absorbing operations from a larger network transition. But it raises the bar for the next period.

EKSINTECH needs those employees to produce renewal revenue, higher uptime, faster repairs, technical support or more customers per engineer. Otherwise, growth will translate into lower operating leverage.

Hardware and supplier costs are the most visible risk. The UPS transaction is explicit. It involved backup-power equipment, a purchase contract, invoice records, payment evidence and a VAT dispute. The documents referenced in court included a supply contract, appendix, invoice and bank statement. This looks like the sort of transaction that can be necessary in wartime connectivity but not necessarily high-margin. The company may have procurement expertise and supplier relationships, but those are economically attractive only if it prices risk properly.

Currency is the quiet cost. Many network inputs are effectively dollar- or euro-linked even when the customer invoice is hryvnia-denominated: routers, optical modules, batteries, power equipment, licenses, software, cloud services, international transit and RIPE-related fees. The NBU source confirms that Ukraine’s official exchange rates are used for accounting and other legal purposes; the practical commercial issue is that EKSINTECH’s costs can reprice faster than public-sector contracts or annual customer renewals.

A low net margin gives little buffer against a sudden currency move if the company has not built escalation terms into contracts.

Compliance is another cost center. The electronic-communications law imposes obligations on providers, including emergency and wartime network instructions, access restrictions under specified legal decisions, and other provider duties. NCEC’s 2026 notice on gambling-site blocking illustrates how providers are not simply bandwidth resellers; they carry monitoring and enforcement obligations. Those costs scale with network complexity. For a larger carrier, compliance overhead can be spread across a bigger base. For a mid-sized regional operator, it can become another reason to automate support and regulatory response.

Suppliers And Upstreams: Redundancy Helps, Dependence Remains

The official site names Level3, Global Crossing, Cogent and RETN among upstream or external connectivity routes, as well as DE-CIX, AMS-IX, PL-IX, SL-IX and parity channels with European backbone providers. Modern routing databases show AS3255 receiving from and connecting to a range of carriers, with lists including Cogent, GTT, Hurricane Electric, RETN, A-Systems, Telecom Italia Sparkle and others depending on the source. UA-IX lists the network as a participant. That breadth is economically important because a customer buying EKSINTECH does not want one brittle path.

Multiple transit and exchange relationships support resilience and bargaining power.

Still, supplier dependence is not eliminated by a large peer list. If EKSINTECH sells internet access, it buys or maintains access to upstream capacity, exchange ports, optics, space, energy and field repair. If it sells managed routing and IP resources, it depends on RIPE procedures, registry standing, route-object hygiene and customer documentation. If it sells equipment, it depends on distributors, import logistics and warranties. If it sells continuity during power outages, it depends on fuel, batteries, generators and safe field access.

The supplier map creates a strategic opening. EKSINTECH can bundle supplier complexity into a single accountable service for institutions that do not want to manage carriers, registry processes and power-resilience logistics themselves. That is where economic value can be retained. But the same map also gives sophisticated customers alternatives. A utility, university or another carrier can buy from a national operator, another LIR, a cloud network, a local ISP, or a systems integrator. EKSINTECH has to prove that its specific combination of network position and support is cheaper or safer than self-management.

Customer Concentration: Public Buyers Are Visible But Not Dominant

The public buyer list is attractive but small relative to reported revenue. Opendatabot and YouControl show EKSINTECH selling to the Institute for Condensed Matter Physics, Ukrenergo, Carpathian National University, the Radio Astronomy Institute and Lviv Polytechnic. Those names matter because they are serious institutions, not consumer leads. The ICMP tender alone shows a meaningful service contract, and the Radio Astronomy Institute appears in routing records as AS196790, a network that lists AS3255 among its routing relationships. That combination suggests EKSINTECH has a niche in academic, research, utility and institutional connectivity.

But public procurement does not appear to explain the whole revenue base. Even using the higher current public-sales tally visible in search-indexed procurement summaries, 2026 public tender sales are in the low single-digit millions of hryvnia. Compared with 2025 reported revenue above UAH 261 million, that is not enough to define the company. Either private business, wholesale network services, transit, resource leasing, hardware sales or non-Prozorro contracts carry most revenue, or public data captures only a small part of the commercial activity.

This is good and bad. It reduces the risk that one visible government buyer accounts for most revenue. It also means concentration cannot be tested from open sources. The company could have a few large private telecom customers, or it could have a broad base of business subscribers and downstream networks. The official site’s customer-category claims are too broad to settle the question. The right diligence request is a revenue-by-customer table, split into recurring monthly service, project hardware, IP-resource support, transit, hosting, domain or registry work, and one-off implementation.

Alternatives And The Customer’s In-House Option

EKSINTECH’s alternatives are not hypothetical. A customer that needs ordinary internet access can use national operators, mobile backup, another local ISP, Starlink or a procurement marketplace. A customer that needs IP resource support can work with another RIPE member, a consultant, a national carrier or a technically capable employee. A customer that needs backup power can buy UPS and batteries through distributors. A customer that needs routing can hire a network engineer, buy managed service from a larger carrier, or use cloud connectivity where appropriate.

This is why the company must sell integration, not fragments. The customer’s in-house alternative becomes weaker when the task spans several domains: address-resource legality, BGP announcements, route objects, abuse contacts, redundant upstreams, on-site power, service monitoring, VAT paperwork, public procurement documentation and emergency response. A university IT department might maintain ordinary connectivity; it may not want to manage RIPE paperwork, exchange routes, public tenders and backup-power warranty in the same week.

A utility may have network engineers; it still might prefer an accountable outside operator for a defined address block, support package or secondary path.

The strongest EKSINTECH product is therefore not "internet." It is continuity with administrative burden removed. That can include fiber or transit, but the defensibility comes from the bundle: a customer’s network keeps routing, the address resources remain legitimate, the invoices match procurement rules, the backup power is maintained, and someone answers at night. The official site’s 24/7 support claim is economically meaningful only if customers pay for it repeatedly and if the support team handles incidents that customers cannot or do not want to handle alone.

Risk Transfer And Payment Timing

The business transfers risk in both directions. Customers transfer operational risk to EKSINTECH: uptime, routing configuration, support response, resource documentation and sometimes hardware procurement. EKSINTECH transfers some supplier risk onward through pricing and contract terms, but the public evidence suggests not all risk can be passed through.

The ICMP contract’s postpayment model is a simple example. EKSINTECH delivers service first and receives payment after the service month. That is standard procurement practice. It still means the provider finances payroll, upstream capacity and support before cash arrives. On a nine-month contract, the amount is manageable. Across many customers, especially with hardware included, receivables can become material.

The UPS tax-invoice dispute shows administrative timing risk. The company had been paid by the buyer, but registration of the tax invoice was blocked and had to be litigated. The court’s finding favored EKSINTECH, but the process consumed time and imposed uncertainty. When gross margins are thin, documentary precision becomes part of the product. If EKSINTECH sells infrastructure projects to public or regulated buyers, it needs compliance capacity as much as network engineering.

Wartime conditions amplify all of this. Freedom House’s Ukraine connectivity report describes power cuts, infrastructure damage, generator use by providers, damaged fiber and base stations, and the importance of resilient internet access. This creates demand for EKSINTECH’s services. It also raises cost: emergency repairs, backup power, spare parts, field safety, fuel and customer churn toward whichever provider stays online. In that setting, resilience is not a slogan. It is a cost center that must be priced.

Unofficial Signals: Useful, But Not A Moat

Unofficial market signals broadly confirm that AS3255 is used at meaningful scale. Cloudflare Radar estimates a large user population for AS3255 and shows traffic composition data. Steam-derived Ukrainian speed rankings cited by technology media put EKSINTECH in the top-ten group in some observations, though those reports warn that Steam sorts providers by traffic volume and that the measurement is not a universal quality ranking. AbuseIPDB pages show some EKSINTECH-routed IP addresses with abuse reports, including brute-force or mail-login reports, but the listed confidence scores vary and these pages do not prove provider misconduct.

They are anti-abuse signals to monitor, not a valuation thesis.

The right use of these signals is conservative. They suggest the network is active and visible under real load. They also suggest a normal operational burden for an ISP: abuse handling, bot traffic, customer devices, mail servers, compromised hosts and route reputation. A provider that can automate abuse response, keep clean contacts, isolate problem customers and answer upstream complaints has a service advantage. A provider that treats abuse as background noise risks reputation damage and higher support cost.

One more signal is the breadth of the AS-UARNET as-set. The routing object includes a long list of member networks and customer or peer sets. That is consistent with a role as an aggregator or transit community, not merely a last-mile provider. But as-set length can overstate active commercial strength. It may include historical members, route-policy artifacts or downstreams with different economic weight. The signal is real; the monetization still has to be proven through revenue composition and renewal rates.

The Judgment

The Elias Ward judgment is: EKSINTECH is operationally credible and economically promising, but the public record does not yet prove durable, high-quality recurring value. It is not a weak company. The reported revenue, visible infrastructure, legal identity, public tenders and routing position all point to a serious Ukrainian connectivity business. The question is whether the company is becoming a higher-value managed network and resource-administration operator or remaining a blend of low-margin service, capacity resale, hardware procurement and project work.

The 2025 numbers lean mixed. UAH 261.2 million of revenue is significant for a regional telecom-services company, and UAH 10.5 million of profit is a real result. Yet 4.0% net margin is thin. Headcount growth makes the next period important. If the additional staff produces more recurring contracts per engineer, better support quality and higher-value managed services, 2025 could be an investment year. If staff growth simply followed one-off projects and labor-heavy operations, the margin will remain exposed.

The best evidence of a moat is the network-resource role. AS3255, the IPv6 allocation, the UA-IX membership, the route objects and the institutional tenders all point toward a company that customers may rely on for tasks that are tedious to switch: routing policy, IP-resource administration, public-sector service continuity and academic or utility connectivity. The weakest evidence is productization. Public sources do not show a named managed-service platform, recurring software module, proprietary automation layer, published SLA history, churn data, customer renewal cohorts or gross margins by service line.

That means the right valuation posture is neither dismissive nor promotional. EKSINTECH should be treated as a strategically useful infrastructure-and-service company with upside if it turns technical integration into repeatable support revenue. The market should not reward all revenue equally. A hryvnia of monthly managed routing support is worth more than a hryvnia of imported UPS resale. A hryvnia of recurring institutional internet with documented uptime is worth more than a hryvnia of one-off registry paperwork.

A hryvnia of automated monitoring and compliance support is worth more than a hryvnia of manually handled tickets if the automation truly lowers cost to serve.

What Recurring Value Would Look Like

The public record gives enough clues to define the recurring product EKSINTECH should be trying to sell. It would not be a generic subscription in a dashboard. It would be a contracted operating layer around the network resources that customers cannot allow to fail. For a university, that might mean autonomous-system administration, RIPE documentation, route objects, primary and backup internet paths, incident reporting, DNS support and renewal calendar control. For a utility, it might mean dedicated address blocks, routing support, backup links, a named escalation path, traffic monitoring and documented monthly service reports.

For a smaller provider, it might mean upstream capacity, IPv4 block support, abuse-contact handling, BGP guidance and backup-power procurement advice.

The economic feature is that each additional service lowers the customer's desire to switch. A customer can tender ordinary internet access every year. It is harder to replace a provider that knows the customer's route history, registry status, equipment site, emergency contacts, public-procurement paperwork and support expectations. The public ICMP procurement shows internet access with monthly payment timing. The YouControl tender rows show resource support and IPv4 block support. The company site emphasizes personal managers and continuous technical support. Individually these are small facts.

Together they sketch a possible managed-service bundle.

The bundle must be priced against avoided disruption, not just megabits. During normal periods, a buyer compares providers by bandwidth, price and response. During power cuts or routing incidents, the buyer values who can keep the link alive, document the problem, coordinate with upstreams and restore service without forcing internal staff to chase several vendors. EKSINTECH's public site leans into that reliability pitch. The challenge is proving that customers pay for it separately, renew it and expand it.

This is where software lifecycle and automation enter the business model. A network operator with 141 reported employees cannot scale high-touch support indefinitely if every route change, abuse ticket, renewal, device alert and procurement document is handled manually. The value of software is not a separate product label; it is a lower cost to serve and a more consistent service record. Provisioning templates, monitoring dashboards, customer inventory, abuse queues, RIPE-document procedures, field-ticket history and SLA reporting can turn engineering knowledge into repeatable process.

If EKSINTECH already has that layer, public records do not show it. If it does not, building it would be one of the clearest ways to convert network relevance into margin.

The customer should be willing to pay because the alternative is fragmented responsibility. A public institution may be able to buy a UPS, but it still needs someone to size, document, maintain and support the resilience setup. It may be able to register or maintain resources, but it must preserve competence when staff leave. It may be able to buy connectivity from a national carrier, but it may not get the same local repair context or academic-network familiarity. EKSINTECH's opportunity is to make the customer's internal alternative look cheap in the invoice and expensive in hidden coordination.

How To Read The Reported Growth

The reported financial trend has to be read through two filters: mix and timing. The revenue line grew from UAH 222.0 million in 2024 to UAH 261.2 million in 2025, but net margin remained thin even after profit improved. That is consistent with several possible realities. The company may have added higher-value recurring services but also invested in employees and equipment. It may have sold more hardware or address-resource services with lower margin. It may have gained volume from a network transition but still needed to absorb integration costs.

Or it may have been operating in a market where customers demand resilience but resist price increases.

The difference between revenue growth and profit quality matters more than the growth itself. If EKSINTECH signs a one-year institutional internet contract, the monthly revenue is visible and the support obligation is clear. If it sells two IPv4 /24 blocks with technical support, the invoice may reflect scarce resource value, but the durability depends on contract term, renewal and whether the customer can replace the arrangement. If it sells UPS equipment, the invoice can be large, but the retained margin can disappear into supplier cost and working capital.

If it administers an AS and related resources for a university, the invoice may be small, but the relationship can lead to ongoing routing and support work.

The reported employee expansion is a second filter. A workforce jump can mean EKSINTECH is professionalizing operations, improving support coverage and preparing for larger customers. It can also mean the business is more labor-intensive than the revenue line suggests. Because revenue per employee fell, the company needs to show that the headcount creates future productivity. Evidence would include faster provisioning, lower downtime, more customers per support engineer, more automated abuse handling, higher renewal rates, or a larger share of recurring managed service. Without that evidence, the employee increase is a cost risk.

The asset expansion is a third filter. Assets rising faster than revenue can reflect useful investment in network equipment, address resources, power systems or receivables. It can also mean the company is carrying more working capital for projects. The liability-to-asset ratio does not look alarming from the public figures, but the direction matters. A business that finances hardware and gets paid after service must manage receivables carefully. A thin-margin carrier can grow itself into cash pressure if equipment projects and public-sector payment timing expand faster than recurring cash receipts.

The right interpretation is therefore conditional. EKSINTECH's growth is credible, but the public numbers do not prove quality. A high-quality version of the story is a network operator investing in staff and assets to support sticky institutional customers. A lower-quality version is a company reporting large invoices from equipment and resource pass-through while net margin remains compressed. The public record supports both possibilities; the judgment stays cautious until mix data resolves it.

Capital Discipline And Wartime Procurement

Capital discipline is not optional for a Ukrainian connectivity provider. The country context creates real demand for resilient networks, but the same context raises the cost of resilience. Backup power, batteries, generators, spare optics, router capacity, fuel and field repairs are practical necessities when power and infrastructure are under pressure. The Freedom House country report describes damaged fiber, damaged base stations, provider generator use and recurrent power disruptions. Those conditions can make EKSINTECH more valuable to customers, but only if the company prices the cost of being available.

The UPS sale is the clearest warning. Backup-power equipment is strategically valuable, and a provider that can source and deliver it may win trust. But capital tied up in equipment does not necessarily earn carrier-like recurring returns. If EKSINTECH buys imported equipment, pays suppliers, waits for customer payment, carries warranty risk and then spends management time defending documentation, the invoice can look much larger than the economic profit. The company needs pricing discipline: deposits, currency clauses, warranty exclusions, service attachments, and clear separation between equipment margin and ongoing maintenance.

IPv4 resources have a different capital character. Scarce address space can be rented, supported, transferred or administered. A UAH 460,080 contract for use and support of two /24 blocks suggests demand for this capability. The margin may be attractive if the resource is already controlled and the main cost is support and registry work. It may be less attractive if the provider must source blocks from another party, accept contractual risk, or provide extensive technical support without adequate recurring fees. Again the public invoice is not enough; the important figure is retained contribution after resource cost and engineer time.

Transit and exchange capacity sit between those categories. Upstream capacity and exchange ports support the whole network and can be sold across many customers. That creates operating leverage if utilization rises. It creates downside if capacity is overbought or if customers churn. The official site's claims about more than 100 Gbit/s of external capacity and 10 Gbit/s exchange links sound commercially meaningful, but the public sources do not reveal utilization, cost per megabit, contract duration or redundancy cost. A strong operator will show disciplined capacity planning and customer commitments that cover fixed costs.

A weaker one will carry impressive routes without enough paid traffic.

In wartime procurement, capital discipline also includes documentation. Public buyers and tax authorities require paperwork, and network customers need proof of service. EKSINTECH's court win shows it can defend a transaction, but a better operating model prevents documentary disputes from becoming expensive recurring friction. The more the company can standardize contracts, invoices, acceptance acts, inventory records and support logs, the more its administrative burden falls as revenue grows.

Competitive Position Is A Service Design Problem

Competition in this market is not one rival. It is a stack of substitutes. Large national carriers can underwrite broader coverage. Local ISPs can underprice basic access. Starlink can provide backup connectivity in some settings. Cloud networks can absorb workloads that once needed local hosting or dedicated routing. Specialist consultants can handle RIPE paperwork. Equipment distributors can sell UPS blocks directly. Internal IT teams can manage ordinary routers and renewals when staff are available.

EKSINTECH's answer cannot be only that it has network assets. Assets matter, but customers buy outcomes. The company needs a repeatable reason for a buyer to select it even when a substitute is cheaper. The most credible reasons are proximity, institutional familiarity, resource-administration capability, academic-network heritage, multi-upstream routing, and support during unstable power conditions. These reasons are service design choices. They must show up in contracts, escalation paths, reports, response times and renewal behavior.

The institutional niche looks more promising than mass consumer positioning. Public records show research institutes, universities and a national energy company in the tender trail. Those customers have complicated internal needs and may value documentation. They also have procurement discipline and alternatives. EKSINTECH can win if it speaks the language of technical risk and administrative assurance. It can lose if tenders reduce the service to price per connection or if customers conclude that resource support is routine enough to insource.

This is why customer concentration cannot be judged only by named buyers. A broad set of small business customers can be stable if the support model is efficient. A small number of institutional contracts can be stable if switching cost is high and renewal rates are strong. A large private carrier customer can be dangerous if it creates high revenue but can shift traffic to another upstream quickly. Public sources do not disclose the revenue distribution. The practical diligence question is how many customers would have to leave before EKSINTECH's gross margin breaks.

The strongest competitive outcome would be a portfolio where basic connectivity opens the account, resource administration deepens it, backup power and routing support protect it, and monitoring/reporting keeps renewal simple. The weakest outcome would be independent one-off sales: an access line here, a UPS resale there, an annual resource-support fee elsewhere, each priced competitively and each replaceable. EKSINTECH's public facts show the ingredients for the stronger model. They do not yet prove the recipe.

Facts That Would Change The Judgment

Several facts would move the judgment up. First, a revenue split showing most 2025 revenue from recurring connectivity, managed support, IP-resource administration, hosting or multi-year institutional contracts would materially improve confidence. Second, gross-margin disclosure showing that hardware resale is a minority contributor would reduce pass-through concern. Third, renewal data from academic, utility, state and business customers would show whether the public customer base is sticky.

Fourth, evidence that EKSINTECH uses internal tooling to automate provisioning, monitoring, RIPE documentation, abuse handling and SLA reporting would make the "software contribution" real rather than inferred. Fifth, a capital plan showing how backup power, routing hardware and fiber repairs are financed without squeezing working capital would make the 2025 balance-sheet expansion easier to underwrite.

Several facts would move the judgment down. Heavy customer concentration in one private carrier or related-party buyer would raise risk. A large share of revenue from hardware resale or equipment procurement would lower recurring quality. Contracts without currency-indexation would expose margins if imported equipment or capacity reprices. Rising abuse reputation, unresolved route hygiene, or visible customer churn toward alternatives would undermine the network moat. A fall in revenue per employee without matching support quality or renewal gains would suggest that the 2025 hiring expansion reduced operating leverage.

The public evidence today supports one clear conclusion: EKSINTECH has enough network relevance to matter, but relevance is not the same as durable economics. The company’s incentive is to make every project attach to something recurring: maintenance, monitoring, address-resource custody, uptime reporting, field response, compliance handling or multi-year support. If it succeeds, the hardware and licence work becomes a funnel into higher-retention services. If it fails, the company will keep reporting activity without proving that it can keep much of the value.

Sources