BIZTRAC BETA
Rental and operating of own or leased real estate

KOH EIENDOM AS

Org. no. 826272732 Limited company (AS) Karmøy Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 9.4m
Operating profit NOK 8.0m
Equity NOK 9.2m
Incorporated 1987
Share capital NOK 300,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KOH EIENDOM AS is registered as a limited company in Karmøy, Rogaland with organisation number 826272732. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 300,000, divided into 200 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom, og drive handel, tjenesteytende virksomhet og produksjon, samt hva hermed står i forbindelse, herunder å delta i andre foretagender som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.4m in revenue and NOK 8.0m in operating profit.

Key figures · 2024

Revenue
NOK 9.4m
Operating profit
NOK 8.0m
Equity
NOK 9.2m
Est. value
NOK 21.0m

Financial health · 2024

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.3%
Satisfactory
Equity as a share of total capital

Who owns KOH EIENDOM AS?

CIC PROPERTY AS
KOH EIENDOM AS
NOK 9.4m rev. · NOK 8.0m profit

KOH EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOH EIENDOM AS

Who owns KOH EIENDOM AS?

CIC PROPERTY AS is the largest registered owner, with 100.0%.

What is the revenue of KOH EIENDOM AS?

KOH EIENDOM AS had revenue of NOK 9.4m in 2024.

Where is KOH EIENDOM AS based?

KOH EIENDOM AS has its business address in Avaldsnes.

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.