BIZTRAC BETA
Uoppgitt

VOKSENLIA INVEST AS

Org. no. 930099783 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 302,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

VOKSENLIA INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 930099783. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap. Investeringer i aksjer og øvrige verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 302,000
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
79.34
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.1%
Good
Equity as a share of total capital

Who owns VOKSENLIA INVEST AS?

ERIK THORESEN HAUG
VOKSENLIA INVEST AS
NOK 0 rev. · NOK −5,000 profit

VOKSENLIA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VOKSENLIA INVEST AS own?

VOKSENLIA INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VOKSENLIA INVEST AS

Who owns VOKSENLIA INVEST AS?

ERIK THORESEN HAUG is the largest registered owner, with 100.0%.

What is the revenue of VOKSENLIA INVEST AS?

VOKSENLIA INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of VOKSENLIA INVEST AS?

Erik Thoresen Haug is registered as general manager of VOKSENLIA INVEST AS.

Where is VOKSENLIA INVEST AS based?

VOKSENLIA INVEST 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.