BIZTRAC BETA
Web search portal activities

MEDIEARKIVET NO AS

Org. no. 981957059 Limited company (AS) Oslo Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 51.8m
Operating profit NOK 4.5m
Equity NOK 10.6m
Incorporated 2000
Share capital NOK 300,000

MEDIEARKIVET NO AS is registered as a limited company in Oslo, Oslo with organisation number 981957059. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2000. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Utvikling, drift og distribusjon av informasjonsdatabaser uansett lagringsmedium og distribusjonsform, og alt som står i naturlig forbindelse med dette. Selskapet kan også investere eller delta i andres virksomheter i Norge og utlandet.”. The most recent filed accounts, for the 2024 financial year, show NOK 51.8m in revenue and NOK 4.5m in operating profit.

Key figures · 2024

Revenue
NOK 51.8m
Operating profit
NOK 4.5m
Equity
NOK 10.6m
Est. value
NOK 31.0m

Financial health · 2024

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.9%
Good
Equity as a share of total capital

Who owns MEDIEARKIVET NO AS?

RETRIEVER NORGE AS
MEDIEARKIVET NO AS
NOK 51.8m rev. · NOK 4.5m profit

MEDIEARKIVET NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEDIEARKIVET NO AS

Who owns MEDIEARKIVET NO AS?

RETRIEVER NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of MEDIEARKIVET NO AS?

MEDIEARKIVET NO AS had revenue of NOK 51.8m in 2024.

Who is the general manager of MEDIEARKIVET NO AS?

Robert Carl Sture Söderling is registered as general manager of MEDIEARKIVET NO AS.

Where is MEDIEARKIVET NO AS based?

MEDIEARKIVET NO 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.