BIZTRAC BETA
Other real estate activities on a fee or contract basis

MARIDALSVEIEN 85-87 AS

Org. no. 990337292 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 20.5m
Operating profit NOK 8.7m
Equity NOK 18.1m
Incorporated 2006
Share capital NOK 200,000

Signals

1 flags
  • Nylig endring 2026-07-17 Adresseendring registrert 2026-07-17.

MARIDALSVEIEN 85-87 AS is registered as a limited company in Oslo, Oslo with organisation number 990337292. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.5m in revenue and NOK 8.7m in operating profit.

Key figures · 2024

Revenue
NOK 20.5m
Operating profit
NOK 8.7m
Equity
NOK 18.1m
Est. value
NOK 30.3m

Financial health · 2024

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.0%
Good
Equity as a share of total capital

Who owns MARIDALSVEIEN 85-87 AS?

BERTEL O. STEEN NÆRINGSEIENDOM AS
MARIDALSVEIEN 85-87 AS
NOK 20.5m rev. · NOK 8.7m profit

MARIDALSVEIEN 85-87 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MARIDALSVEIEN 85-87 AS er morselskap for 54 datterselskaper:

Frequently asked questions about MARIDALSVEIEN 85-87 AS

Who owns MARIDALSVEIEN 85-87 AS?

BERTEL O. STEEN NÆRINGSEIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of MARIDALSVEIEN 85-87 AS?

MARIDALSVEIEN 85-87 AS had revenue of NOK 20.5m in 2024.

Where is MARIDALSVEIEN 85-87 AS based?

MARIDALSVEIEN 85-87 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.