BIZTRAC BETA
Repair and maintenance of motor vehicles

IKOEN EIENDOM AS

Org. no. 911922673 Limited company (AS) Sveio Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 3.1m
Equity NOK 6.2m
Incorporated 2013
Share capital NOK 100,000

Signals

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

IKOEN EIENDOM AS is registered as a limited company in Sveio, Vestland with organisation number 911922673. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, utvikle og utleie av egen eiendom og alt som står i naturlig forbindelse med dette. I tillegg til kjøp og utleie av maskiner og -utstyr til private samt entreprenørvirksomhet innen bygg og anlegg, og delta i tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 3.1m
Equity
NOK 6.2m
Est. value
NOK 10.3m

Financial health · 2024

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

Who owns IKOEN EIENDOM AS?

LAST HAUGESUND AS
IKOEN EIENDOM AS
NOK 4.1m rev. · NOK 3.1m profit

IKOEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IKOEN EIENDOM AS

Who owns IKOEN EIENDOM AS?

LAST HAUGESUND AS is the largest registered owner, with 100.0%.

What is the revenue of IKOEN EIENDOM AS?

IKOEN EIENDOM AS had revenue of NOK 4.1m in 2024.

Where is IKOEN EIENDOM AS based?

IKOEN EIENDOM AS has its business address in Sveio.

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.