BIZTRAC BETA
Wholesale of information and communication equipment

O RØNNING KONTOR OG DATA AS

Org. no. 980651460 Limited company (AS) Alstahaug Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 7.9m
Operating profit NOK 203,000
Equity NOK 2.3m
Incorporated 1999
Share capital NOK 63,000

O RØNNING KONTOR OG DATA AS is registered as a limited company in Alstahaug, Nordland with organisation number 980651460. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 1999. Registered share capital is NOK 63,000, divided into 63 shares. The company's stated purpose is: “Salg og service butikk, kontor og datautstyr. Samt virksomhet i tilknyttning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.9m in revenue and NOK 203,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.9m
Operating profit
NOK 203,000
Equity
NOK 2.3m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns O RØNNING KONTOR OG DATA AS?

LIV RØNNING
O RØNNING KONTOR OG DATA AS
NOK 7.9m rev. · NOK 203,000 profit

O RØNNING KONTOR OG DATA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about O RØNNING KONTOR OG DATA AS

Who owns O RØNNING KONTOR OG DATA AS?

LIV RØNNING is the largest registered owner, with 100.0%.

What is the revenue of O RØNNING KONTOR OG DATA AS?

O RØNNING KONTOR OG DATA AS had revenue of NOK 7.9m in 2024.

Who is the general manager of O RØNNING KONTOR OG DATA AS?

Liv Rønning is registered as general manager of O RØNNING KONTOR OG DATA AS.

Where is O RØNNING KONTOR OG DATA AS based?

O RØNNING KONTOR OG DATA AS has its business address in Sandnessjøen.

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.