BIZTRAC BETA
Development of building projects

ÆLVEBRUKET HOLDING AS

Org. no. 827997862 Limited company (AS) Modum Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK −771,000
Incorporated 2021
Share capital NOK 150,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−771k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).

ÆLVEBRUKET HOLDING AS is registered as a limited company in Modum, Buskerud with organisation number 827997862. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Investere og eie aksjer i selskaper med tilknytning til eiendomsutvikling samt annet som står naturlig i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −46,000
Equity
NOK −771,000

Financial health · 2024

Liquidity
91.77
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4.4%
Weak
Equity as a share of total capital

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

Who owns ÆLVEBRUKET HOLDING AS?

VARP EIENDOM AS
ÆLVEBRUKET HOLDING AS
· NOK −46,000 profit

ÆLVEBRUKET HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ÆLVEBRUKET HOLDING AS own?

ÆLVEBRUKET HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ÆLVEBRUKET HOLDING AS

Who owns ÆLVEBRUKET HOLDING AS?

VARP EIENDOM AS is the largest registered owner, with 33.3%.

Who is the general manager of ÆLVEBRUKET HOLDING AS?

Petter Tangen is registered as general manager of ÆLVEBRUKET HOLDING AS.

Where is ÆLVEBRUKET HOLDING AS based?

ÆLVEBRUKET HOLDING AS has its business address in Vikersund.

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.