BIZTRAC BETA
Uoppgitt

VI ØNSKER STYREPLASS AS

Org. no. 926085425 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK −8.4m
Operating profit NOK −8.6m
Equity NOK 34.5m
Incorporated 2020
Share capital NOK 63,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8,6 mill kr).

VI ØNSKER STYREPLASS AS is registered as a limited company in Oslo, Oslo with organisation number 926085425. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 63,000, divided into 600 shares. The company's stated purpose is: “Å investere i aksjer og verdipapirer, eiendom og dertil naturlig tilhørende virksomhet, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK −8.4m in revenue and NOK −8.6m in operating profit.

Key figures · 2024

Revenue
NOK −8.4m
Operating profit
NOK −8.6m
Equity
NOK 34.5m
Est. value
NOK 40.5m

Financial health · 2024

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

Who owns VI ØNSKER STYREPLASS AS?

ROFLCOPTER AS
VI ØNSKER STYREPLASS AS
NOK −8.4m rev. · NOK −8.6m profit

VI ØNSKER STYREPLASS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VI ØNSKER STYREPLASS AS own?

VI ØNSKER STYREPLASS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VI ØNSKER STYREPLASS AS

Who owns VI ØNSKER STYREPLASS AS?

ROFLCOPTER AS is the largest registered owner, with 50.0%.

What is the revenue of VI ØNSKER STYREPLASS AS?

VI ØNSKER STYREPLASS AS had revenue of NOK −8.4m in 2024.

Where is VI ØNSKER STYREPLASS AS based?

VI ØNSKER STYREPLASS 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.