BIZTRAC BETA
Computing infrastructure, data processing, hosting and related activities

DATACITY AS

Org. no. 979441320 Limited company (AS) Ringerike Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 561,000
Operating profit NOK 22,000
Equity NOK 150,000
Incorporated 1997
Share capital NOK 150,000

DATACITY AS is registered as a limited company in Ringerike, Buskerud with organisation number 979441320. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 1997. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Salg av internettjenester og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 561,000 in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 561,000
Operating profit
NOK 22,000
Equity
NOK 150,000
Est. value
NOK 226,000

Financial health · 2025

Liquidity
6.36
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
84.3%
Very good
Equity as a share of total capital

Who owns DATACITY AS?

DIGITALIA AS
DATACITY AS
NOK 561,000 rev. · NOK 22,000 profit

DATACITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DATACITY AS

Who owns DATACITY AS?

DIGITALIA AS is the largest registered owner, with 100.0%.

What is the revenue of DATACITY AS?

DATACITY AS had revenue of NOK 561,000 in 2025.

Who is the general manager of DATACITY AS?

Ingolf Løken is registered as general manager of DATACITY AS.

Where is DATACITY AS based?

DATACITY AS has its business address in Hønefoss.

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.