BIZTRAC BETA
Buying and selling of own real estate

ØYO EIENDOM AS

Org. no. 994911341 Limited company (AS) Hol Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 105,000
Equity NOK 10.0m
Incorporated 2009
Share capital NOK 473,000

Signals

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

ØYO EIENDOM AS is registered as a limited company in Hol, Buskerud with organisation number 994911341. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2009. Registered share capital is NOK 473,000, divided into 1000 shares. The company's stated purpose is: “Å kjøpe, eie og forvalte fast eiendom og aksjer. Selskapet kan ved deltagelse eller på annen måte investere i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 105,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 105,000
Equity
NOK 10.0m
Est. value
NOK 7.4m

Financial health · 2024

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

Who owns ØYO EIENDOM AS?

ØYO HOLDING AS
ØYO EIENDOM AS
NOK 2.5m rev. · NOK 105,000 profit

ØYO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYO EIENDOM AS

Who owns ØYO EIENDOM AS?

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

What is the revenue of ØYO EIENDOM AS?

ØYO EIENDOM AS had revenue of NOK 2.5m in 2024.

Who is the general manager of ØYO EIENDOM AS?

Knut Olav Øyo is registered as general manager of ØYO EIENDOM AS.

Where is ØYO EIENDOM AS based?

ØYO EIENDOM AS has its business address in Geilo.

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.