BIZTRAC BETA
Uoppgitt

ØREN HOLDING AS

Org. no. 924910410 Limited company (AS) Vestby Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −94,000
Equity NOK 5.0m
Incorporated 2020
Share capital NOK 330,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−94k kr).

ØREN HOLDING AS is registered as a limited company in Vestby, Akershus with organisation number 924910410. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 330,000, divided into 3000 shares. The company's stated purpose is: “Investeringer i aksjer og andre formuesgoder samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −94,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −94,000
Equity
NOK 5.0m
Est. value
NOK 15.4m

Financial health · 2024

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
74.2%
Very good
Equity as a share of total capital

Who owns ØREN HOLDING AS?

KIRSTEN GUNDERSEN
ØREN HOLDING AS
NOK 0 rev. · NOK −94,000 profit

ØREN HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ØREN HOLDING AS own?

ØREN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØREN HOLDING AS

Who owns ØREN HOLDING AS?

KIRSTEN GUNDERSEN is the largest registered owner, with 40.0%.

What is the revenue of ØREN HOLDING AS?

ØREN HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of ØREN HOLDING AS?

Hanne Gundersen Tjelland is registered as general manager of ØREN HOLDING AS.

Where is ØREN HOLDING AS based?

ØREN HOLDING AS has its business address in Son.

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.