BIZTRAC BETA
Computer consultancy and computer facilities management activities

UPTIME CONSULTING AS

Org. no. 987321288 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 30.6m
Operating profit NOK 4.7m
Equity NOK 326,000
Incorporated 2004
Employees 15
Share capital NOK 200,000

UPTIME CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 987321288. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2004 and has 15 registered employees. Registered share capital is NOK 200,000, divided into 100000 shares. The company's stated purpose is: “Å yte konsulent- og rådgivningstjenester innen IT-sektoren, samt all hertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 30.6m in revenue and NOK 4.7m in operating profit.

Key figures · 2025

Revenue
NOK 30.6m
Operating profit
NOK 4.7m
Equity
NOK 326,000
Est. value
NOK 27.4m

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.5%
Not satisfactory
Equity as a share of total capital

Who owns UPTIME CONSULTING AS?

UPTIME O
UPTIME CONSULTING AS
NOK 30.6m rev. · NOK 4.7m profit

UPTIME CONSULTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about UPTIME CONSULTING AS

Who owns UPTIME CONSULTING AS?

UPTIME O is the largest registered owner, with 80.0%.

What is the revenue of UPTIME CONSULTING AS?

UPTIME CONSULTING AS had revenue of NOK 30.6m in 2025.

Who is the general manager of UPTIME CONSULTING AS?

Ole-Kristian Villabø is registered as general manager of UPTIME CONSULTING AS.

Where is UPTIME CONSULTING AS based?

UPTIME CONSULTING AS has its business address in Oslo.

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.