biztrac. BETA
COMPANY REGISTER PROFILE
818672772 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

WANGEN HOLDING AS

Org. no. 818672772 Limited company (AS) Rælingen Incorporated 2017 Active
Revenue 2025 NOK 0
Operating profit NOK −55,000
Equity NOK 17.7m
Incorporated 2017
Share capital NOK 30,000

Signals

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

WANGEN HOLDING AS is registered as a limited company in Rælingen, Akershus with organisation number 818672772. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i verdipapirer og eiendom samt deltakelse i annen næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −55,000
▼ −68 %
Equity
NOK 17.7m
▲ +58 %
Est. value
NOK 42.2m

Financial health · 2025

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

Who owns WANGEN HOLDING AS?

WANGEN HOLDING AS
NOK 0 rev. · NOK −55,000 profit

WANGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WANGEN HOLDING AS

Who owns WANGEN HOLDING AS?

Kim Andre Wangen is the largest registered owner, with 100.0%.

What is the revenue of WANGEN HOLDING AS?

WANGEN HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of WANGEN HOLDING AS?

Kim Andre Wangen is registered as general manager of WANGEN HOLDING AS.

Where is WANGEN HOLDING AS based?

WANGEN HOLDING AS has its business address in Blystadlia.

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.