BIZTRAC BETA
Dental practice care activities

VICTORIA ØEN AS

Org. no. 821196132 Limited company (AS) Lier Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 842,000
Operating profit NOK −175,000
Equity NOK 303,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

VICTORIA ØEN AS is registered as a limited company in Lier, Buskerud with organisation number 821196132. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å drive med tannlegetjenester og konsulentvirksomhet som naturlig tilknytning til dette, samt annen konsulentvirksomhet innen handel, produksjon, eksport, import, og investering i andre selskaper og kursvirksomhet, og annen drift som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 842,000 in revenue and NOK −175,000 in operating profit.

Key figures · 2024

Revenue
NOK 842,000
Operating profit
NOK −175,000
Equity
NOK 303,000
Est. value
NOK 870,000

Financial health · 2024

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

Who owns VICTORIA ØEN AS?

VICTORIA ØEN-VEISANEN
VICTORIA ØEN AS
NOK 842,000 rev. · NOK −175,000 profit

VICTORIA ØEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VICTORIA ØEN AS

Who owns VICTORIA ØEN AS?

VICTORIA ØEN-VEISANEN is the largest registered owner, with 100.0%.

What is the revenue of VICTORIA ØEN AS?

VICTORIA ØEN AS had revenue of NOK 842,000 in 2024.

Where is VICTORIA ØEN AS based?

VICTORIA ØEN AS has its business address in Lierstranda.

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.