BIZTRAC BETA
Joinery installation

WOLDENGEN AS

Org. no. 925700657 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −11,000
Equity NOK 130,000
Incorporated 2020
Share capital NOK 45,000

Signals

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

WOLDENGEN AS is registered as a limited company in Oslo, Oslo with organisation number 925700657. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2020. Registered share capital is NOK 45,000, divided into 45000 shares. The company's stated purpose is: “Bygg og anleggsvirksomhet 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.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK −11,000
Equity
NOK 130,000
Est. value
NOK 880,000

Financial health · 2024

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.6%
Good
Equity as a share of total capital

Who owns WOLDENGEN AS?

JAN MICHAELSEN WOLDENGEN
WOLDENGEN AS
NOK 2.4m rev. · NOK −11,000 profit

WOLDENGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WOLDENGEN AS

Who owns WOLDENGEN AS?

JAN MICHAELSEN WOLDENGEN is the largest registered owner, with 100.0%.

What is the revenue of WOLDENGEN AS?

WOLDENGEN AS had revenue of NOK 2.4m in 2025.

Who is the general manager of WOLDENGEN AS?

Jan Michaelsen Woldengen is registered as general manager of WOLDENGEN AS.

Where is WOLDENGEN AS based?

WOLDENGEN 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.