BIZTRAC BETA
COMPANY REGISTER PROFILE
915327788 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

RAVISRAL AKSJESELSKAP

Org. no. 915327788 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK −57,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

RAVISRAL AKSJESELSKAP is registered as a limited company in Bærum, Akershus with organisation number 915327788. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Drive næringsutvikling gjennom kjøp og salg av aksjer eller lignende, direkte eller gjennom eierskap i andre bedrifter.”.

Key figures · 2024

Operating profit
NOK −2,000
Equity
NOK −57,000

Financial health · 2024

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

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

Who owns RAVISRAL AKSJESELSKAP?

LARS IVAR KURE BJUGSTAD
RAVISRAL AKSJESELSKAP
· NOK −2,000 profit

RAVISRAL AKSJESELSKAP has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAVISRAL AKSJESELSKAP

Who owns RAVISRAL AKSJESELSKAP?

LARS IVAR KURE BJUGSTAD is the largest registered owner, with 100.0%.

Who is the general manager of RAVISRAL AKSJESELSKAP?

Lars Ivar Kure Bjugstad is registered as general manager of RAVISRAL AKSJESELSKAP.

Where is RAVISRAL AKSJESELSKAP based?

RAVISRAL AKSJESELSKAP has its business address in Fornebu.

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.