BIZTRAC BETA
Rental and operating of own or leased real estate

C5 INVEST AS

Org. no. 915524486 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 19.7m
Operating profit NOK 9.0m
Equity NOK −2.3m
Incorporated 2015
Share capital NOK 364,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,3 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

C5 INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 915524486. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 364,000, divided into 363692 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.7m in revenue and NOK 9.0m in operating profit.

Key figures · 2024

Revenue
NOK 19.7m
Operating profit
NOK 9.0m
Equity
NOK −2.3m
Est. value
NOK 90.9m

Financial health · 2024

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

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

Who owns C5 INVEST AS?

BULK PARK ENEBAKK II AS
C5 INVEST AS
NOK 19.7m rev. · NOK 9.0m profit

C5 INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about C5 INVEST AS

Who owns C5 INVEST AS?

BULK PARK ENEBAKK II AS is the largest registered owner, with 100.0%.

What is the revenue of C5 INVEST AS?

C5 INVEST AS had revenue of NOK 19.7m in 2024.

Where is C5 INVEST AS based?

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