BIZTRAC BETA
Computer consultancy and computer facilities management activities

UBIQUITOUS AS

Org. no. 919063181 Limited company (AS) Larvik Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 47,000
Equity NOK −91,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−91k kr).

UBIQUITOUS AS is registered as a limited company in Larvik, Vestfold with organisation number 919063181. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rådgivning innen programvarearkitektur og utvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 47,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 47,000
Equity
NOK −91,000
Est. value
NOK 526,000

Financial health · 2025

Liquidity
0.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-78.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns UBIQUITOUS AS?

ALEXEY VIKTOROVICH ZIMAREV
UBIQUITOUS AS
NOK 2.2m rev. · NOK 47,000 profit

UBIQUITOUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UBIQUITOUS AS

Who owns UBIQUITOUS AS?

ALEXEY VIKTOROVICH ZIMAREV is the largest registered owner, with 100.0%.

What is the revenue of UBIQUITOUS AS?

UBIQUITOUS AS had revenue of NOK 2.2m in 2025.

Who is the general manager of UBIQUITOUS AS?

Alexey Viktorovich Zimarev is registered as general manager of UBIQUITOUS AS.

Where is UBIQUITOUS AS based?

UBIQUITOUS AS has its business address in Larvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.