biztrac. BETA
COMPANY REGISTER PROFILE
926725394 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Compulsory dissolution UPDATED 03.10.2026
⚠HAUGÅKER PROSJEKT AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Development of building projects

HAUGÅKER PROSJEKT AS

Org. no. 926725394 Limited company (AS) Oslo Incorporated 2021 Compulsory dissolution
Operating profit NOK −41,000
Equity NOK −138,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.

HAUGÅKER PROSJEKT AS is registered as a limited company in Oslo, Oslo with organisation number 926725394. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp og salg av eiendom og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Former names: BONUM PROSJEKT 44 AS

Key figures · 2025

Operating profit
NOK −41,000
▼ −12 %
Equity
NOK −138,000
▼ −42 %

Financial health · 2025

Liquidity
55.15
Very good
Current assets ÷ current liabilities
Profitability
-0.1%
Not satisfactory
Return on total assets
Solidity
-0.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HAUGÅKER PROSJEKT AS?

HAUGÅKER PROSJEKT AS
· NOK −41,000 profit

HAUGÅKER PROSJEKT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAUGÅKER PROSJEKT AS

Who owns HAUGÅKER PROSJEKT AS?

MIDDELBORG AS is the largest registered owner, with 60.0%.

Where is HAUGÅKER PROSJEKT AS based?

HAUGÅKER PROSJEKT 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.