BIZTRAC BETA
Uoppgitt

WÅLENGEN HOLDING AS

Org. no. 934034899 Limited company (AS) Nittedal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −25,000
Equity NOK 72,000
Incorporated 2024
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

WÅLENGEN HOLDING AS is registered as a limited company in Nittedal, Akershus with organisation number 934034899. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Å eie og forvalte aksjer, investere og delta i andre selskaper samt annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK 72,000
Est. value
NOK 85,000

Financial health · 2025

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

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

Who owns WÅLENGEN HOLDING AS?

INGER MERETE WÅLENGEN
WÅLENGEN HOLDING AS
NOK 0 rev. · NOK −25,000 profit

WÅLENGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WÅLENGEN HOLDING AS own?

WÅLENGEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WÅLENGEN HOLDING AS

Who owns WÅLENGEN HOLDING AS?

INGER MERETE WÅLENGEN is the largest registered owner, with 100.0%.

What is the revenue of WÅLENGEN HOLDING AS?

WÅLENGEN HOLDING AS had revenue of NOK 0 in 2025.

Where is WÅLENGEN HOLDING AS based?

WÅLENGEN HOLDING AS has its business address in Hakadal.

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.