biztrac. BETA
COMPANY REGISTER PROFILE
927462397 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

C3 EIENDOM AS

Org. no. 927462397 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 512,000
Equity NOK −4.8m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,8 mill kr).

C3 EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 927462397. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikling av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 512,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +42 %
Operating profit
NOK 512,000
▲ +86 %
Equity
NOK −4.8m
▼ −38 %
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
3.7%
Weak
Return on total assets
Solidity
-7.8%
Weak
Equity as a share of total capital

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

Who owns C3 EIENDOM AS?

C3 EIENDOM AS
NOK 1.6m rev. · NOK 512,000 profit

C3 EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does C3 EIENDOM AS own?

C3 EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about C3 EIENDOM AS

Who owns C3 EIENDOM AS?

HCBS HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of C3 EIENDOM AS?

C3 EIENDOM AS had revenue of NOK 1.6m in 2025.

Where is C3 EIENDOM AS based?

C3 EIENDOM AS has its business address in Kolsås.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.