BIZTRAC BETA
COMPANY REGISTER PROFILE
984919492 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

KAMSO EIENDOM AS

Org. no. 984919492 Limited company (AS) Indre Fosen Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 19.6m
Operating profit NOK 978,000
Equity NOK 5.7m
Incorporated 2002
Share capital NOK 100,000

KAMSO EIENDOM AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 984919492. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling, utleie og salg av fast eiendom og alt som hermed står i forbindelse med dette, samt utleie av maskiner og å være delaktig i tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.6m in revenue and NOK 978,000 in operating profit.

Former names: GEGGEN EIENDOM AS

Key figures · 2025

Revenue
NOK 19.6m
Operating profit
NOK 978,000
Equity
NOK 5.7m
Est. value
NOK 6.6m

Financial health · 2025

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

Who owns KAMSO EIENDOM AS?

KAMSO EIENDOM AS
NOK 19.6m rev. · NOK 978,000 profit

KAMSO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAMSO EIENDOM AS

Who owns KAMSO EIENDOM AS?

KAMSO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KAMSO EIENDOM AS?

KAMSO EIENDOM AS had revenue of NOK 19.6m in 2025.

Where is KAMSO EIENDOM AS based?

KAMSO EIENDOM AS has its business address in Stadsbygd.

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

Report a problem

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