BIZTRAC BETA
Rental and operating of own or leased real estate

IVAN EIENDOM AS

Org. no. 962952771 Limited company (AS) Karmøy Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 12.8m
Operating profit NOK 5.3m
Equity NOK 628,000
Incorporated 1991
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.

IVAN EIENDOM AS is registered as a limited company in Karmøy, Rogaland with organisation number 962952771. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Eie og forvalte eiendom samt hva hermed står i forbindelse, herunder å delta i andre foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.8m in revenue and NOK 5.3m in operating profit.

Key figures · 2024

Revenue
NOK 12.8m
Operating profit
NOK 5.3m
Equity
NOK 628,000
Est. value
NOK 6.0m

Financial health · 2024

Liquidity
0.63
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.8%
Not satisfactory
Equity as a share of total capital

Who owns IVAN EIENDOM AS?

SOLSTAD INVEST AS
IVAN EIENDOM AS
NOK 12.8m rev. · NOK 5.3m profit

IVAN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

IVAN EIENDOM AS er morselskap for 10 datterselskaper:

Frequently asked questions about IVAN EIENDOM AS

Who owns IVAN EIENDOM AS?

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

What is the revenue of IVAN EIENDOM AS?

IVAN EIENDOM AS had revenue of NOK 12.8m in 2024.

Where is IVAN EIENDOM AS based?

IVAN EIENDOM AS has its business address in Skudeneshavn.

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.