BIZTRAC BETA
Rental and operating of own or leased real estate

KALNES EIENDOM AS

Org. no. 986295925 Limited company (AS) Sarpsborg Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 38.0m
Operating profit NOK 17.2m
Equity NOK 98.2m
Incorporated 2003
Share capital NOK 41.3m

KALNES EIENDOM AS is registered as a limited company in Sarpsborg, Østfold with organisation number 986295925. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 41.3m, divided into 41300 shares. The company's stated purpose is: “Selskapets virksomhet er kjøp og salg av fast eiendom, eiendomsutvikling, eiendomsbesittelse, utleie av fast eiendom, prosjektutvikling av tomter og næringsbygg samt alt hva hermed måtte stå i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 38.0m in revenue and NOK 17.2m in operating profit.

Key figures · 2024

Revenue
NOK 38.0m
Operating profit
NOK 17.2m
Equity
NOK 98.2m
Est. value
NOK 99.6m

Financial health · 2024

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.9%
Good
Equity as a share of total capital

Who owns KALNES EIENDOM AS?

COLLIGO AS
KALNES EIENDOM AS
NOK 38.0m rev. · NOK 17.2m profit

KALNES EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KALNES EIENDOM AS

Who owns KALNES EIENDOM AS?

COLLIGO AS is the largest registered owner, with 100.0%.

What is the revenue of KALNES EIENDOM AS?

KALNES EIENDOM AS had revenue of NOK 38.0m in 2024.

Who is the general manager of KALNES EIENDOM AS?

Ole Anders Engebretsen is registered as general manager of KALNES EIENDOM AS.

Where is KALNES EIENDOM AS based?

KALNES EIENDOM AS has its business address in Grålum.

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.