BIZTRAC BETA
Development of building projects

VESTAKSEN MJØNDALEN STADION AS

Org. no. 897876132 Limited company (AS) Drammen Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −873,000
Equity NOK 17.0m
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−873k kr).

VESTAKSEN MJØNDALEN STADION AS is registered as a limited company in Drammen, Buskerud with organisation number 897876132. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, herunder utvikling og utleie, investering i andre selskap samt alt hva derved er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −873,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −873,000
Equity
NOK 17.0m
Est. value
NOK 11.9m

Financial health · 2024

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

Who owns VESTAKSEN MJØNDALEN STADION AS?

VESTAKSEN EIENDOM AS
VESTAKSEN MJØNDALEN STADION AS
NOK 1.4m rev. · NOK −873,000 profit

VESTAKSEN MJØNDALEN STADION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTAKSEN MJØNDALEN STADION AS

Who owns VESTAKSEN MJØNDALEN STADION AS?

VESTAKSEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of VESTAKSEN MJØNDALEN STADION AS?

VESTAKSEN MJØNDALEN STADION AS had revenue of NOK 1.4m in 2024.

Where is VESTAKSEN MJØNDALEN STADION AS based?

VESTAKSEN MJØNDALEN STADION AS has its business address in Drammen.

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.