BIZTRAC BETA
Retail sale of furniture, including mattresses and box springs

ØYEHOL EIENDOM AS

Org. no. 929218248 Limited company (AS) Ulstein Incorporated 1981 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 4.0m
Equity NOK 18.5m
Incorporated 1981
Share capital NOK 220,000

ØYEHOL EIENDOM AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 929218248. The business is classified under retail sale of furniture, including mattresses and box springs (NACE 47.551). The company was incorporated in 1981. Registered share capital is NOK 220,000, divided into 88 shares. The company's stated purpose is: “Leie ut forretningseiendommer og forvalte øvrige verdier i selskapet.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 4.0m in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 4.0m
Equity
NOK 18.5m
Est. value
NOK 23.8m

Financial health · 2024

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

Who owns ØYEHOL EIENDOM AS?

TOMAR INVEST AS
ØYEHOL EIENDOM AS
NOK 7.1m rev. · NOK 4.0m profit

ØYEHOL EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ØYEHOL EIENDOM AS own?

ØYEHOL EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ØYEHOL EIENDOM AS

Who owns ØYEHOL EIENDOM AS?

TOMAR INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of ØYEHOL EIENDOM AS?

ØYEHOL EIENDOM AS had revenue of NOK 7.1m in 2024.

Who is the general manager of ØYEHOL EIENDOM AS?

Tore Øyehol is registered as general manager of ØYEHOL EIENDOM AS.

Where is ØYEHOL EIENDOM AS based?

ØYEHOL EIENDOM AS has its business address in Ulsteinvik.

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.