BIZTRAC BETA
Other investment companies, except captive companies

CUBERA IMPACT 2022 INVEST AS

Org. no. 928986896 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 6.7m
Equity NOK 108.6m
Incorporated 2022
Share capital NOK 243,000

Signals

1 flags
  • Nylig endring 2026-03-09 Aksjekapital registrert 2026-03-09.

CUBERA IMPACT 2022 INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 928986896. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2022. Registered share capital is NOK 243,000, divided into 485625 shares. The company's stated purpose is: “Investere i fond som igjen investerer i andre fond (fond-i-fond) og å utøve all virksomhet som har en naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK 6.7m in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 6.7m
Equity
NOK 108.6m
Est. value
NOK 79.8m

Financial health · 2024

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

Who owns CUBERA IMPACT 2022 INVEST AS?

CORAGRUPPEN AS
CUBERA IMPACT 2022 INVEST AS
NOK 8.2m rev. · NOK 6.7m profit

CUBERA IMPACT 2022 INVEST AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about CUBERA IMPACT 2022 INVEST AS

Who owns CUBERA IMPACT 2022 INVEST AS?

CORAGRUPPEN AS is the largest registered owner, with 5.1%.

What is the revenue of CUBERA IMPACT 2022 INVEST AS?

CUBERA IMPACT 2022 INVEST AS had revenue of NOK 8.2m in 2024.

Where is CUBERA IMPACT 2022 INVEST AS based?

CUBERA IMPACT 2022 INVEST 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.