Summary
- Information & Computing Center is a real Nizhny Novgorod connectivity business with long operating history, licensed telecom activity, AS24658, IPv4 resources, hosting, colocation, telephony, private-sector access, web-support services and operator-facing offers. The public evidence supports its local utility value.
- The investment judgment is cautious. A 2024 company record showing about 39.1 million rubles of revenue and only 177,000 rubles of profit leaves almost no visible self-funded renewal capacity, while another registry view reports a loss. Price indexation, a 2025 contract-party transfer to NITS SVT, compliance litigation, mixed customer reviews and a material 2024 service instability all point to pressure on the legacy asset base.
- The company can keep earning where it solves local reach, support and continuity problems that larger or more standardized alternatives do not solve. It is not evidenced as a scalable infrastructure compounder unless post-transfer economics, capital backing, upstream resilience, compliance closure and customer retention improve.
The renewal bill is the strategy
Information & Computing Center's economic incentive is simple: make an old local network earn enough recurring money before that same network becomes the liability. The company was registered in 1998. Its public telecom surface presents it as one of the older regional operators around Nizhny Novgorod, with internet access, telephony, private-sector coverage, operator traffic services, colocation, hosting, domain services and website support sitting under related IVC, Internet2 and NNOV.ru brands. That mix can be defensible. It can also hide a thin-margin asset-renewal problem.
The renewal bill is not just routers. It is radio access equipment, switching, backhaul, subscriber devices, tower or rooftop work, colocation power and cooling, monitoring, spares, lawful-interception compliance, support staff and the people who know how the legacy network was built. It is also supplier risk. A local operator that says it works with equipment manufacturers and importers still has to buy, support and replace equipment in rubles while much of the relevant technology supply chain is priced, directly or indirectly, against foreign-currency hardware markets.
That mismatch does not have to destroy the business, but it sets the hurdle. Small monthly access fees and low-priced hosting only work if utilization is high, faults are contained and enough customers stay because the operator has reach that substitutes cannot match.
The explicit judgment is that IVC is credible as a narrow continuity utility, not yet credible as a broad self-funded renewal story. It has actual operating evidence: telecom licenses, a RIPE organisation record, AS24658, active IPv4 announcements, colocation terms, support channels, phone and internet services, and a long public service history. But its visible financial scale is modest. RBC Companies reports 2024 revenue of 39.097 million rubles, cost of sales above revenue, and profit of only 177,000 rubles. That is less a return on infrastructure than a rounding error after operating friction.
A second registry view reports broadly similar income but a 2024 net loss, which is not proof that RBC is wrong; it is a warning that public company-level economics are not robust enough to carry a confident renewal thesis.
The right question is not whether the company has customers. It plainly has had customers. The question is whether the paying base is large, loyal and price-tolerant enough to finance asset replacement, support labor, compliance cost and supplier dependence before outages and alternatives force the issue. On the current record, the answer is only partly yes. IVC likely has pockets of durable demand. It does not yet show a clean margin engine.
What sits inside the boundary
The first analytical problem is the control boundary. The legal entity is Information & Computing Center, Ltd., a Russian limited liability company in Nizhny Novgorod with OGRN 1025203758580 and INN 5262067308. Public registry sources identify Alexander Terentyev as executive director and 100% founder, with Marina Terentyeva listed in management. The public operator surface uses IVC and Internet2 language. NNOV.ru presents a web-studio, hosting and digital-support surface. Internet2 presents the telecom access, telephony, colocation and operator-services surface.
These may be commercially connected, but the public reader should not collapse every brand claim into one clean financial statement.
That caution matters because the company-level numbers are small. RBC's 2024 employee count is eight. Another database reports eleven employees. NNOV.ru marketing copy refers to a much larger team and a large hosted-site base, but that reads like brand-surface language rather than a verified legal-entity employment number. It may include contractors, group resources, legacy claims, or a wider service organization. For economics, the conservative move is to treat the legal entity's public financial record as the hard floor and the brand claims as commercial context.
The boundary became more important in 2025. A public notice on the Internet2 site says that, from 2025-07-01, rights, obligations, debts and claims under communication-service contracts were transferred from IVC to ООО "НИЦ СВТ". The notice describes NITS SVT as an IVC partner continuing to work under the IVC brand, with familiar payments and contacts largely remaining in place. This is not a cosmetic detail. It means that some customer-contract economics may have moved away from the original legal entity while the public customer experience still looks continuous.
That can be good or bad. It could mean a cleaner operating vehicle, better licensing structure, more capital support, or a practical reallocation of obligations. It could also mean that the legacy entity's financials are no longer the best measure of the current branded service. The point is not to speculate beyond the notice. The point is to treat the company as a visible local operating platform whose exact economics after July 2025 are less transparent than its public service pages suggest.
In a small infrastructure business, opacity is not automatically fatal. Many local networks survive because their owners, technicians, suppliers and customers understand arrangements that are not obvious from a registry page. But opacity raises the discount rate. When the central question is whether the business can fund renewal, a contract-party transfer is a demand for evidence, not a footnote.
Revenue exists; renewal cash is the problem
IVC's revenue base is not imaginary. The public service surface points to recurring charges from internet access, telephony, static IPs, colocation, traffic services, hosting, domains and website support. It also points to project revenue from site creation, promotion, contextual advertising and other digital services. The combination is rational for a local operator. Connectivity creates a customer relationship. Hosting and domain registration monetize the same small-business customer. Website support creates recurring service revenue. Telephony and operator services add technical depth.
Colocation and traffic sales turn network and facility assets into additional yield.
But the scale of those revenues must be compared with the scale of the obligations. A company doing roughly 39 million rubles of annual revenue is not insignificant, but it is small in infrastructure terms. If profit is only 177,000 rubles, the margin is under half a percent. Spread across a year, that is less than many small businesses would spend on one meaningful equipment replacement, one complex outage response, or a few months of specialist technical labor. If the alternative database's loss figure is closer to the economic truth, the renewal gap is wider.
Cost of sales above revenue is the most direct warning in the RBC record. A company can show accounting profit despite gross pressure because of other income, timing or classification. But a telecom operator with high direct costs has little room to absorb power increases, equipment imports, support overtime, credit cost, license-compliance spending or customer credits after outages. The August 2024 public instability notice promised recalculations for affected subscribers. Even if the immediate cash amount was manageable, it shows how service interruptions turn technical problems into revenue leakage.
The 2025 price-indexation notice is therefore economically predictable. When a local operator announces higher prices for legal entities and later for individuals, it is not only seeking more revenue. It is testing customer captivity. Customers with fiber, mobile broadband, cloud PBX and national hosting alternatives can resist or leave. Customers in private-sector areas where large fiber operators do not build may accept more. The price increase is useful evidence precisely because it asks who truly values the local network.
For IVC, recurring revenue quality is more important than headline revenue. A hosting customer paying 300 to 500 rubles per month is valuable only if support cost is low and churn is controlled. A colocation customer paying from 1,900 rubles per month for 1U space is useful if the cabinet, power and network are already there and if the customer does not consume disproportionate engineering time. A private-sector access customer can be attractive if the radio or fixed access plant is already amortized, but can be costly if every fault requires field work.
A legal-entity connection can be profitable if installation is priced properly and if the customer buys telephony, support or static IP services. The economics depend less on the existence of tariffs than on utilization, fault rate and customer concentration, none of which is disclosed.
The business therefore sits in a familiar regional-operator bind. The services are real. The customer need is real. The reported company-level margin does not yet prove that the asset base can renew itself.
Business model: local access first, digital services second
The strongest part of the model is local access. Internet2 says IVC serves Nizhny Novgorod and the region, including places such as Bor, Bogorodsk, Gorodets, Zavolzhye and Chkalovsk. It emphasizes private-sector homes and organizations where larger operators may not build. That is the right terrain for a small regional ISP. The large carrier's advantage is standardized scale. The local operator's advantage is awkward coverage, practical installation and a shorter decision path.
The radio-access claim is especially important. Internet2 says IVC was among the first in the city to use wireless access and that it can reach areas beyond competitor coverage. Court material from another context mentions historical contracts for wireless coverage calculation in the 2-7 GHz range and modeling of distributed broadband networks. Those records do not prove current quality, but they do show that wireless access and radio planning were part of the engineering history, not just marketing.
Radio access is a double-edged asset. It avoids the capital intensity of trenching fiber into every low-density location. It can also become a support-heavy system if equipment ages, interference changes, rooftop access is difficult, or backhaul becomes congested. A radio last mile that solved the coverage problem ten years ago may still produce cash today, but it eventually asks for replacement, better spectrum planning, better customer equipment, higher-capacity backhaul and more disciplined fault handling.
The second layer is telephony. Internet2 offers ordinary telephone service and IP telephony for individuals and legal entities, including one number or a whole office. Voice can be sticky because customers build business habits around numbers and call flows. But voice also brings compliance obligations, equipment, number management, customer support and a shrinking tolerance for outages. When a 2024 notice says both internet and telephone availability were affected for many subscribers, it shows why telephony stickiness can turn into service pressure.
The third layer is operator and wholesale services. IVC advertises IP transit, VoIP transit, remote configuration and support for smaller providers. It names technical systems such as Cisco, Asterisk, Freeswitch, MERA and MVTS. This is not a mass-market story. It is a services-for-operators story, where the buyer pays for practical experience and local engineering availability. The upside is that one capable technical team can monetize knowledge across several small networks. The downside is labor dependence. If a few specialists carry too much of the operational memory, the business is hard to scale and hard to transfer.
The fourth layer is hosting, domains, website builds, promotion and support through NNOV.ru. This layer broadens revenue and makes sense for small-business customers. NNOV.ru lists turnkey site creation, landing pages, promo sites, corporate sites, online stores, hosting, SEO, media advertising, social-network work, contextual advertising and website-support packages. It also claims an own hosting-server park and long history in hosting. The logic is straightforward: the local business that needs connectivity may also need a domain, site, e-mail, hosting and maintenance. Bundling reduces selling cost.
This layer is also the most exposed to alternatives. Website builds and hosting are commoditized. A customer can use national hosting, cloud infrastructure, site builders, marketplaces, freelancers or agencies. IVC's advantage is not product uniqueness. It is relationship, proximity, Russian-language support, bundled service and continuity for customers that already know the operator. That can be profitable, but it is not enough to carry network renewal if the access layer is weak.
The model works only if the layers support one another. Access brings customers. Telephony increases stickiness. Hosting and web support add margin. Colocation and traffic services monetize technical assets. Operator support keeps engineers productive. If the layers fragment across legal entities, brands or contract transfers, the economic question becomes who keeps the cash and who pays the replacement bill.
Infrastructure evidence: real network, limited slack
The network evidence is concrete enough to establish that IVC is not merely a reseller brand. RIPE records link Information & Computing Center, Ltd. to ORG-ICCL1-RIPE, show LIR status, and identify AS24658 as IVC-AS. The aut-num was created in 2002, and the IPv4 inetnum 81.19.128.0-81.19.143.255 dates to 2002 as well. Public ASN databases report 1,280 IPv4 addresses. That is a meaningful but small address base. It supports a local operator thesis, not a national platform thesis.
Observed routing also matters. RIPEstat announced-prefix data showed active more-specific IPv4 prefixes, including 81.19.128.0/23, 81.19.130.0/24 and 81.19.142.0/23 during the query interval. RIPEstat RPKI validation for an active AS24658-originated prefix returned a valid result. bgp.tools similarly presents the observed active prefixes as having valid RPKI certificates. Valid route authorization does not prove commercial health, but it does show that the operator has maintained at least part of its routing hygiene.
The caution is that the registered routing policy looks older than the observed network. The RIPE aut-num still lists import and export policy around AS31133, AS3216, AS8744 and AS8359, and route objects include larger historical blocks. RIPEstat routing-consistency data showed the older 81.19.128.0/20 route object as not visible in BGP, while more-specific prefixes were visible. It also showed active BGP adjacency around AS51685 that was not reflected in the older WHOIS policy. Public BGP summaries from bgp.tools and BigDataCloud also point to AS51685 Mikron-Media LLC as the current important upstream or adjacent network.
This is not a scandal. Small networks often carry stale registry policy. But stale policy is a sign of limited operating headroom. A well-resourced network usually keeps route objects, public routing policy, RPKI and current peering reality aligned because counterparties, customers and incident responders use those records. When the public record drifts, it suggests a small technical team focused on keeping service running rather than polishing every registry detail.
IPv6 evidence is also mixed. RIPE shows an IPv6 allocation, 2a10:ad80::/29, created in 2020. Yet public ASN summaries used here did not show active IPv6 prefixes for AS24658. That does not mean IVC has no IPv6 anywhere, and it should not be overread. It does mean there is no strong public evidence of active IPv6 deployment at the ASN level. For a legacy regional provider, that is another sign that renewal priorities may be defensive: keep existing customers connected, keep IPv4 service stable, and defer investments that do not immediately protect revenue.
The network resource picture therefore supports both sides of the case. IVC has address space, ASN history, LIR identity and live routes. It also has small scale, limited observed upstream diversity, route-policy staleness and no visible active IPv6 footprint in the public ASN summaries reviewed. The network is real. The slack is not.
Pricing says continuity, not capital abundance
The published tariff clues are useful because they show what the company can ask customers to pay. NNOV.ru lists hosting tiers at 300, 425 and 500 rubles per month, depending on disk space and site count. It lists website-support packages from 7,000 rubles per month for up to five hours to 60,000 rubles per month for up to fifty hours, with one-off work at 2,000 rubles per hour. It lists turnkey site creation at 35,900 rubles, landing pages at 27,900, corporate sites at 32,900 and online stores at 72,000. These are accessible small-business prices. They are not enterprise-software economics.
Colocation pricing tells the same story. Internet2 lists 1U from 1,900 rubles per month, with included 100/1000 Mbps connection language, add-on traffic at 1,000 rubles for 10 Mbps and 10,000 rubles for 100 Mbps, extra IPs at 100 rubles, extra ports and sockets at low monthly prices, and individual terms for more than 350W per server. Those prices may fit a local facility with already-built space and low acquisition costs. They do not indicate a business throwing off large amounts of free cash.
The important question is not whether these prices are cheap or expensive in isolation. It is whether they create enough gross contribution after support, power, hardware, network transit, facility, payment, compliance and administration costs. A 300-ruble hosting account with minimal support can be profitable on a shared platform. A 300-ruble hosting account that requires handholding is not. A 1,900-ruble colocation unit can work if power usage is controlled and the rack would otherwise sit underused.
It becomes less attractive if power prices rise, cooling is constrained, equipment fails or the customer expects enterprise-grade remote-hands support.
The access side is harder to price because the public service pages direct potential legal-entity and residential customers to call or request survey-based terms. That makes sense operationally. A private-sector radio connection, a business line and a telephony bundle have different installation costs. But it also means public outsiders cannot verify whether IVC has enough pricing power to fund replacement. The 2025 indexation notice shows that prices had to move. It does not show that customers accepted them at low churn.
This is where local monopoly pockets matter. In an apartment block with multiple fiber providers, IVC's pricing power is limited. In a private-sector area with poor alternatives, a stable radio or fixed service can command more loyalty even if customers complain. The review page contains exactly that kind of signal: customers who value service where alternatives are absent, and customers who complain when speed, support or price disappoint. The business earns money in the gap between those two facts.
A renewal thesis would be stronger if the company disclosed average revenue per access customer, active subscriber counts, churn, installation payback, support tickets per line, colocation utilization, hosting account count by paid plan, and contract length for legal entities. It does not. The published prices show monetization tools. They do not show renewal capacity.
Supplier and upstream dependence narrow the margin of error
IVC says publicly that it has direct supplies from manufacturers and importers, its own warehouse, and the ability to solve local network problems quickly. That is exactly what a small operator should emphasize. Local spares and supplier relationships reduce downtime. A short decision arm helps when a customer needs a survey, replacement device, voice configuration or site visit. The economic risk is that those advantages cost money before they become revenue.
The supplier problem is partly visible in the network. Current public BGP summaries point to AS51685 Mikron-Media LLC as the important observed upstream or adjacent network. The older RIPE policy names larger and older counterparties, including AS31133, AS3216, AS8744 and AS8359. The difference may reflect normal evolution. It may also reflect a narrower present-day upstream posture. For a local provider, one observed current upstream is not automatically fatal; many small networks buy from one stronger regional or national carrier. But it reduces bargaining power and raises outage exposure.
The economic effect is straightforward. If transit, backhaul or upstream terms worsen, a small provider cannot offset them with procurement scale. If equipment becomes harder to source, the provider has to stretch equipment life, raise prices, narrow service commitments or accept lower margins. If a key upstream has problems, the downstream operator absorbs customer anger even when the fault is partly outside its own network.
Legal and compliance dependencies add another supplier-like burden. The court records around lawful-interception obligations show that telecom operation is not just a matter of selling bandwidth. Operators must maintain arrangements with authorities and technical systems. The cases describe failures to provide required implementation acts or approvals and uphold regulatory pressure. The fine reported in one case was small, but the operational obligation was not. Compliance consumes management attention, capital planning and technical work.
It also creates a binary risk: an operator can be mostly functional for customers and still be deficient under license obligations.
The same point applies to voice. IP telephony and operator VoIP transit can be sticky, but they require reliable routing, configuration skill, numbering and compliance. A small operator may earn good service revenue from that complexity. It may also carry concentrated person-risk if only a few engineers know the old voice systems well enough to fix them under pressure.
The supplier picture therefore reinforces the margin concern. IVC appears to have practical technical resources and a network history. It does not have the public scale that would make supplier and upstream shocks easy to absorb.
Customers pay for locality until locality fails
The strongest customer case for IVC is not that it is cheaper than every alternative. It is that it can serve specific local needs that alternatives may ignore. Internet2 emphasizes private-sector areas, legal entities, regional settlements, installation surveys, equipment maintenance and a local support relationship. That is a defensible niche. A national operator may not want to build to a low-density location. A cloud PBX provider may not solve the local access line. A national hosting provider may not send someone who knows the customer's building, network cabinet or radio link.
This is why small regional providers survive long after the market looks consolidated on paper. They own awkward relationships. They know which rooftops work, which villages have demand, which business customers need a number to keep working, and which legacy setups cannot be migrated cleanly without downtime. Customers often do not buy the most modern network. They buy the least risky path to continuity.
But locality is a promise that has to be renewed every day. The review signals are mixed. Some users describe long relationships and useful service, including a 14-year customer and private-sector customers who say the service works where they need it. Other reviews complain about speed, support tone, limited support hours, weekend responsiveness, price and outages. A review page is not a statistically reliable customer survey.
It is still useful because the complaints are the natural failure modes of a small local ISP: slow speed under load, field-service bottlenecks, support availability, acquired network segments that are difficult to maintain, and customer frustration when there is no easy alternative.
The August 2024 service-instability notice adds weight because it is not merely a review. The public notice says many subscribers had difficulty with internet and telephone availability and that recalculations would be made. The next day's update provided timing around recovery work. No operator can avoid every outage. The question is whether outages are isolated and well-handled or symptoms of underinvestment. With the public data available, the answer is uncertain. But the incident fits the broader risk profile: a useful local network with limited visible renewal cash.
Customer concentration remains one of the largest unknowns. Public materials point to residential private-sector users, legal entities, operators, telephony accounts, hosting customers, web-support customers and lead-generation communication services. Court and procurement references show some public-sector or contract history, but not enough to infer a large diversified enterprise base. If a handful of business, operator or public customers carry a large share of revenue, IVC's renewal economics could change quickly after one churn event or contract transfer.
If the revenue base is fragmented across many sticky local users, it may be more resilient than the financial margin suggests.
The contract transfer to NITS SVT makes customer analysis harder. If communication-service contracts moved while the brand remained, then customers may still experience continuity, but the economic beneficiary and obligation holder may differ. That is exactly why the judgment must be cautious. A local brand can keep customer trust while the legal economics move elsewhere.
Regulation turns paperwork into capital cost
Telecom regulation is often described as paperwork until a small operator has to fund it. The Roskomnadzor and court materials around IVC show why that framing is wrong. Licensed telecom operators have obligations around lawful-interception capabilities and coordination with authorities. The cases describe inspections, authority communications, plans, deadlines, modernization references and findings that required documentation or implementation acts were absent. One case produced a fine; another upheld a prescription to correct deficiencies.
The monetary fine alone is not the investment issue. The issue is that compliance competes with renewal capital. A provider that needs to replace access equipment, upgrade switching, improve support, maintain voice services and keep colocation power stable also has to satisfy legal requirements that may require equipment, integration, records, staff time and coordination. For a large carrier, that is a department. For a small regional operator, it can be a management distraction and a cash drain.
The court material also undercuts a common excuse in small-network analysis: that local operators can run cheaply because they are informal and close to customers. Telecom does not allow that indefinitely. Licenses create obligations. Voice services create obligations. Data services with voice-related functions create obligations. Telematics services create obligations. Once those obligations attach, the operator's real cost base is higher than the cost of bandwidth and access equipment.
Geopolitics makes the renewal question harsher, even when the company itself is purely local. IVC sells to local customers in rubles while its own public materials describe supply relationships with manufacturers and importers. That does not prove a supply failure. It does show why replacement cost may not move neatly with local tariffs. The operator can raise access, telephony, hosting or support prices only as fast as local customers will tolerate, while equipment, spares and technical support may follow a different cost path.
This is why the 2025 price indexation cannot be dismissed as routine. If supplier, compliance and labor costs rise faster than local customers' willingness to pay, the operator has only a few choices: accept lower margin, reduce service scope, delay renewal, transfer contracts, consolidate with a partner, or push prices and risk churn. The public record already shows several of those mechanisms: thin margin, price increases, a contract-party transfer and service instability.
The digital-services layer helps but cannot carry everything
NNOV.ru gives IVC a broader commercial surface than a plain ISP would have. The site presents web development, domain registration, hosting, promotion, contextual advertising, social-network services and website maintenance. It claims hundreds of completed sites, many hosted sites and an own hosting-server park. This has strategic logic. A small business that buys internet access may also buy a website. A company that uses local hosting may also need support. A domain or hosting account keeps the relationship alive even when project work is episodic.
The pricing shows a practical small-business shop. A business-card site, corporate site or online store at the published prices can produce useful cash without requiring the same capital intensity as last-mile network buildout. Monthly support packages create recurring revenue that may carry better margin than access if work is managed well. Hosting and domains can scale if the platform is stable and support is standardized.
The constraint is competition. Digital services have abundant alternatives. A customer can move to a cloud provider, a national hosting company, a website builder, a freelancer or another agency. The local relationship helps, but it does not create the same physical lock-in as a hard-to-replace access line. The digital layer therefore improves customer monetization; it does not by itself solve the renewal bill for telecom assets.
There is also a credibility gap between digital marketing claims and legal-entity scale. NNOV.ru's public claims about hosted sites, active projects and staffing should be treated as commercial brand signals, not verified company-level operating metrics. They may be true within a broader brand or over a long history. They do not reconcile cleanly with the small employee counts in registry sources. That does not make them useless. It means they cannot carry the financial conclusion.
The best interpretation is that NNOV.ru gives the IVC ecosystem a useful cross-sell channel. It can produce recurring support revenue, deepen small-business relationships and monetize hosting infrastructure. But when the article's central question is whether connectivity and computing demand can fund equipment replacement and support labor, the digital-services layer is a supplement, not the proof.
Alternatives define the ceiling
Every local infrastructure business is priced against alternatives, even when the alternatives are imperfect. For IVC, the alternatives split by product.
For access, the alternatives are large fixed operators, other regional ISPs, mobile broadband and, in some cases, doing nothing until a better line arrives. Large operators can beat a small provider on procurement, national backbone, call-center scale and bundled offers. They can also ignore marginal pockets where buildout is unattractive. IVC's opening is the private-sector or business customer that needs a practical connection now and values local installation more than a national brand.
For telephony, alternatives include mobile substitution, cloud PBX providers, national SIP providers and bundled carrier voice. IVC's advantage is local bundling and technical support. Its disadvantage is that voice customers are intolerant of interruption and increasingly aware that numbers and PBX functions can be hosted elsewhere.
For hosting and domains, alternatives are even more plentiful. National hosting providers, cloud platforms and managed website tools can undercut or out-feature a local host. IVC's edge is service continuity for local businesses that prefer one provider. That edge is real, but it is soft. It depends on support quality.
For colocation, the alternatives depend on customer sophistication. A small local company or operator may value nearby access to equipment and a known technical team. A larger enterprise may prefer a bigger data center, stronger certifications, richer connectivity and more visible redundancy. Internet2's colocation page claims Tier III reliability, monitoring, UPS, cooling and network availability. Those claims are helpful, but the public evidence does not establish the full facility standard, independent certification or depth of redundancy.
The conservative view is that colocation is a local facility offer, not proof of a high-scale data-center business.
For operator services, IVC's alternative set includes upstream carriers, regional technical contractors and internal staff at small providers. Here the company may have a practical niche. A small operator may not want to hire a full voice or routing specialist. IVC's 25-year technical-service claim and remote configuration offer could monetize experience. Yet that also reinforces person-dependence: expert services are valuable because the expertise is scarce.
Alternatives set the price ceiling. IVC's local reach sets the price floor. The renewal thesis depends on whether the gap between those two prices is large enough after costs. The public record does not yet show that it is.
What would reverse the judgment
The cautious judgment can be reversed, but not by more marketing claims. It would require hard evidence that the renewal bill is funded.
The first reversal fact would be post-transfer financial clarity. If NITS SVT now holds communication-service contracts, then the current economics of the branded service may sit partly outside IVC. A consolidated view, contract allocation, or separate NITS SVT financial evidence would matter. If the transfer placed customer obligations into a better-capitalized operator while IVC retained valuable services or assets, the risk could fall. If the transfer simply moved thin-margin contracts without adding capital, the risk remains.
The second reversal fact would be margin improvement. A 2025 or 2026 record showing higher revenue, positive gross contribution and materially stronger net profit would change the analysis. The current 177,000-ruble profit figure is too thin for comfort. A small operator does not need national-carrier margins, but it needs enough cash to replace equipment before faults force emergency spending.
The third reversal fact would be visible network renewal. Updated route policy aligned with observed BGP, multiple active upstreams, more complete RPKI coverage across live prefixes, active IPv6 announcements, published modernization work, lower outage frequency and clearer service-level reporting would all support the case that the technical base is being maintained rather than harvested.
The fourth reversal fact would be compliance closure. Court records show that regulatory obligations have been a real burden. Evidence that the relevant lawful-interception requirements are fully implemented, accepted and maintained would remove a material uncertainty. It would not create profit by itself, but it would reduce the risk of sudden spending, enforcement pressure or management distraction.
The fifth reversal fact would be customer retention after price increases. The 2025 indexation is the market test. If legal entities and individuals accept higher tariffs without meaningful churn, that would prove local pricing power. If customers leave for fiber, mobile, cloud voice or other providers, IVC's renewal equation worsens.
The sixth reversal fact would be proof of customer diversification. A wide base of small sticky access, voice, hosting and support accounts is safer than dependence on a few large contracts. Public material does not disclose the concentration. Until it does, the risk remains.
Final judgment
Information & Computing Center has earned a place in the local infrastructure map. It has a long operating history, a real ASN, RIPE records, telecom licenses, public service pages, colocation and operator offers, hosting and digital services, and evidence of customers who value local reach. That is not trivial. Many companies with weaker public evidence call themselves telecom operators. IVC's evidence is better than that.
The hard part is renewal. The company appears to be monetizing a legacy local position at small scale while facing the normal cost stack of a telecom operator: equipment, support labor, upstream service, compliance, power, cooling, spares and customer-service failures. Public financial data does not show enough profit to make that comfortable. The 2025 price indexation suggests pressure. The 2025 contract transfer complicates who owns the current customer economics. The 2024 instability notice and mixed reviews show the customer consequences when a local network disappoints.
The company should therefore be read as a viable but constrained local service platform. It can keep earning where alternatives are worse, where private-sector access remains hard, where businesses value local telephony and support, and where hosting or website support stays bundled with customer relationships. It should not be valued as if legacy infrastructure automatically compounds. In this case, infrastructure value depends on disciplined price increases, low churn, capital support, route and compliance hygiene, and the ability to replace aging assets before they turn customer captivity into customer resentment.
The judgment is explicit: IVC's local reach is useful, but the visible economics are too thin to prove that the company can self-fund a full renewal cycle. Treat the business as a narrow regional continuity provider unless harder post-transfer evidence shows that recurring demand is now producing real replacement cash.
Sources
- https://companies.rbc.ru/id/1025203758580-ooo-informatsionnyij-vyichislitelnyij-tsentr/
- https://zachestnyibiznes.ru/company/ul/1025203758580_5262067308_OOO-IVC
- https://check.tochka.com/company/1025203758580/
- https://vsem-podryad.ru/company/54f0b715-c1cf-4f32-9e3c-3cd25f6cec70/
- https://base.garant.ru/63490451/
- https://sudact.ru/arbitral/doc/KxTI4B1ytNNK/
- https://base.garant.ru/66095284/
- https://sudact.ru/arbitral/doc/bmurdHFKvNUp/
- https://sudact.ru/arbitral/doc/dilX6vt9KW5l/
- https://internet2.ru/%d0%b8%d0%b2%d1%86/
- https://internet2.ru/%d1%83%d1%81%d0%bb%d1%83%d0%b3%d0%b8/
- https://internet2.ru/%d1%8e%d1%80%d0%b8%d0%b4%d0%b8%d1%87%d0%b5%d1%81%d0%ba%d0%b8%d0%bc-%d0%bb%d0%b8%d1%86%d0%b0%d0%bc/
- https://internet2.ru/%d0%bf%d0%be%d0%b4%d0%ba%d0%bb%d1%8e%d1%87%d0%b5%d0%bd%d0%b8%d0%b5-%d0%b8%d0%bd%d1%82%d0%b5%d1%80%d0%bd%d0%b5%d1%82%d0%b0-%d0%b2-%d0%bd%d0%b8%d0%b6%d0%b5%d0%b3%d0%be%d1%80%d0%be%d0%b4%d1%81%d0%ba/
- https://internet2.ru/colocation-%d1%80%d0%b0%d0%b7%d0%bc%d0%b5%d1%89%d0%b5%d0%bd%d0%b8%d0%b5-%d0%be%d0%b1%d0%be%d1%80%d1%83%d0%b4%d0%be%d0%b2%d0%b0%d0%bd%d0%b8%d1%8f/
- https://internet2.ru/b2o/
- https://internet2.ru/%d1%82%d0%b5%d1%85%d0%bd%d0%b8%d1%87%d0%b5%d1%81%d0%ba%d0%b0%d1%8f-%d0%bf%d0%be%d0%b4%d0%b4%d0%b5%d1%80%d0%b6%d0%ba%d0%b0/
- https://internet2.ru/%d0%be%d1%82%d0%b7%d1%8b%d0%b2%d1%8b/
- https://internet2.ru/%d0%ba%d0%be%d0%bd%d1%82%d0%b0%d0%ba%d1%82%d1%8b/
- https://internet2.ru/2025/07/31/%d1%83%d0%b2%d0%b5%d0%b4%d0%be%d0%bc%d0%bb%d0%b5%d0%bd%d0%b8%d0%b5-%d0%be-%d0%b7%d0%b0%d0%bc%d0%b5%d0%bd%d0%b5-%d1%81%d1%82%d0%be%d1%80%d0%be%d0%bd%d1%8b-%d0%bf%d0%be-%d0%b4%d0%be%d0%b3%d0%be%d0%b2/
- https://internet2.ru/2025/10/01/%d0%b8%d0%bd%d0%b4%d0%b5%d0%ba%d1%81%d0%b0%d1%86%d0%b8%d1%8f-%d1%81%d1%82%d0%be%d0%b8%d0%bc%d0%be%d1%81%d1%82%d0%b8-%d1%83%d1%81%d0%bb%d1%83%d0%b3/
- https://internet2.ru/2024/08/13/%d0%bd%d0%b5%d1%81%d1%82%d0%b0%d0%b1%d0%b8%d0%bb%d1%8c%d0%bd%d0%be%d1%81%d1%82%d1%8c-%d1%80%d0%b0%d0%b1%d0%be%d1%82%d1%8b-%d1%83%d1%81%d0%bb%d1%83%d0%b3/
- https://internet2.ru/2024/08/14/%d0%be%d0%b1%d0%bd%d0%be%d0%b2%d0%bb%d0%b5%d0%bd%d0%b8%d0%b5/
- https://nnov.ru/
- https://nnov.ru/about/
- https://nnov.ru/domen-i-hosting/
- https://nnov.ru/price/
- https://nnov.ru/contacts/
- https://nnov.ru/services/
- https://nnov.ru/podderzhka-saytov/
- https://rest.db.ripe.net/ripe/aut-num/AS24658.json
- https://rest.db.ripe.net/ripe/organisation/ORG-ICCL1-RIPE.json
- https://rest.db.ripe.net/search.json?query-string=81.19.128.0%2F20&source=ripe
- https://rest.db.ripe.net/search.json?query-string=2a10%3Aad80%3A%3A%2F29&source=ripe
- https://stat.ripe.net/data/as-overview/data.json?resource=AS24658
- https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS24658
- https://stat.ripe.net/data/as-routing-consistency/data.json?resource=AS24658
- https://stat.ripe.net/data/rpki-validation/data.json?resource=AS24658&prefix=81.19.128.0/23
- https://bgp.tools/as/24658
- https://ipinfo.io/AS24658
- https://www.bigdatacloud.com/asn-lookup/AS24658

