BIZTRAC BETA
Buying and selling of own real estate

CHRIMA EIENDOM AS

Org. no. 933572544 Limited company (AS) Lier Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 64,000
Operating profit NOK −155,000
Equity NOK −1.2m
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,2 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−155k kr).

CHRIMA EIENDOM AS is registered as a limited company in Lier, Buskerud with organisation number 933572544. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 64,000 in revenue and NOK −155,000 in operating profit.

Key figures · 2025

Revenue
NOK 64,000
Operating profit
NOK −155,000
Equity
NOK −1.2m

Financial health · 2025

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

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

Who owns CHRIMA EIENDOM AS?

Hakon Brandt
CHRIMA EIENDOM AS
NOK 64,000 rev. · NOK −155,000 profit

CHRIMA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHRIMA EIENDOM AS

Who owns CHRIMA EIENDOM AS?

Hakon Brandt is the largest registered owner, with 100.0%.

What is the revenue of CHRIMA EIENDOM AS?

CHRIMA EIENDOM AS had revenue of NOK 64,000 in 2025.

Who is the general manager of CHRIMA EIENDOM AS?

Hakon Brandt is registered as general manager of CHRIMA EIENDOM AS.

Where is CHRIMA EIENDOM AS based?

CHRIMA EIENDOM AS has its business address in Lier.

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.