BIZTRAC BETA
Development of building projects

MALERHAUGEN PARK AS

Org. no. 911812207 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK −82,000
Operating profit NOK −64,000
Equity NOK 973,000
Incorporated 2013
Share capital NOK 31,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−64k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MALERHAUGEN PARK AS is registered as a limited company in Oslo, Oslo with organisation number 911812207. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 31,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 2025 financial year, show NOK −82,000 in revenue and NOK −64,000 in operating profit.

Key figures · 2025

Revenue
NOK −82,000
Operating profit
NOK −64,000
Equity
NOK 973,000
Est. value
NOK 888,000

Financial health · 2025

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

Who owns MALERHAUGEN PARK AS?

GJELSTEN BOLIG AS
MALERHAUGEN PARK AS
NOK −82,000 rev. · NOK −64,000 profit

MALERHAUGEN PARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MALERHAUGEN PARK AS

Who owns MALERHAUGEN PARK AS?

GJELSTEN BOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of MALERHAUGEN PARK AS?

MALERHAUGEN PARK AS had revenue of NOK −82,000 in 2025.

Where is MALERHAUGEN PARK AS based?

MALERHAUGEN PARK 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.