BIZTRAC BETA
Business and other management consultancy activities

RAO AS

Org. no. 913023455 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −181,000
Equity NOK −943,000
Incorporated 2013
Share capital NOK 230,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−943k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−181k kr).

RAO AS is registered as a limited company in Oslo, Oslo with organisation number 913023455. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 230,000, divided into 230 shares. The company's stated purpose is: “Drive med formidling av finansieringstjenester og bedriftsrådgivning, samt å være agent for norske og utenlandske selskaper. I samarbeid med andre skal også selskapet drive som konsert- og festivalarrangør samt konsulentvirksomhet innen kulturnæringen.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −181,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −181,000
Equity
NOK −943,000

Financial health · 2024

Liquidity
-0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22767.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RAO AS?

RUNE ANDRÉ OLSEN
RAO AS
NOK 0 rev. · NOK −181,000 profit

RAO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAO AS

Who owns RAO AS?

RUNE ANDRÉ OLSEN is the largest registered owner, with 100.0%.

What is the revenue of RAO AS?

RAO AS had revenue of NOK 0 in 2024.

Where is RAO AS based?

RAO 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.