BIZTRAC BETA
Rental and operating of own or leased real estate

CF EIENDOM AS

Org. no. 922569428 Limited company (AS) Ringsaker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 500,000
Operating profit NOK 452,000
Equity NOK 4.3m
Incorporated 2019
Share capital NOK 30,000

CF EIENDOM AS is registered as a limited company in Ringsaker, Innlandet with organisation number 922569428. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet, investeringer i eiendom og aksjer og annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 500,000 in revenue and NOK 452,000 in operating profit.

Key figures · 2024

Revenue
NOK 500,000
Operating profit
NOK 452,000
Equity
NOK 4.3m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns CF EIENDOM AS?

CFS HOEL INVEST AS
CF EIENDOM AS
NOK 500,000 rev. · NOK 452,000 profit

CF EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CF EIENDOM AS own?

CF EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about CF EIENDOM AS

Who owns CF EIENDOM AS?

CFS HOEL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of CF EIENDOM AS?

CF EIENDOM AS had revenue of NOK 500,000 in 2024.

Who is the general manager of CF EIENDOM AS?

Christian Fredrik Sandberg Hoel is registered as general manager of CF EIENDOM AS.

Where is CF EIENDOM AS based?

CF EIENDOM AS has its business address in Nes På Hedmarken.

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.