BIZTRAC BETA
Retail sale of other food

OLIVENLUNDEN AS

Org. no. 984058799 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 78.2m
Operating profit NOK −5.6m
Equity NOK 6.9m
Incorporated 2001
Employees 141
Share capital NOK 22.3m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5,6 mill kr).
  • Nylig endring 2026-05-04 Adresseendring registrert 2026-05-04.

OLIVENLUNDEN AS is registered as a limited company in Oslo, Oslo with organisation number 984058799. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2001 and has 141 registered employees. Registered share capital is NOK 22.3m, divided into 2754 shares. The company's stated purpose is: “Drive butikk og forretningsdrift samt tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 78.2m in revenue and NOK −5.6m in operating profit.

Key figures · 2024

Revenue
NOK 78.2m
Operating profit
NOK −5.6m
Equity
NOK 6.9m
Est. value
NOK 27.9m

Financial health · 2024

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

Who owns OLIVENLUNDEN AS?

S.A.S MAISON BREMOND 1830
OLIVENLUNDEN AS
NOK 78.2m rev. · NOK −5.6m profit

OLIVENLUNDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLIVENLUNDEN AS

Who owns OLIVENLUNDEN AS?

S.A.S MAISON BREMOND 1830 is the largest registered owner, with 100.0%.

What is the revenue of OLIVENLUNDEN AS?

OLIVENLUNDEN AS had revenue of NOK 78.2m in 2024.

Who is the general manager of OLIVENLUNDEN AS?

Nils Johan Gunnar Nilsson is registered as general manager of OLIVENLUNDEN AS.

Where is OLIVENLUNDEN AS based?

OLIVENLUNDEN 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.