BIZTRAC BETA
Rental and operating of own or leased real estate

ØYNA PARKEN EIENDOM AS

Org. no. 828063332 Limited company (AS) Inderøy Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 1.7m
Equity NOK 20.4m
Incorporated 2021
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.

ØYNA PARKEN EIENDOM AS is registered as a limited company in Inderøy, Trøndelag with organisation number 828063332. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverve, eie, samt drive utleie av fast eiendom og virksomhet som hermed står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 1.7m
Equity
NOK 20.4m
Est. value
NOK 16.0m

Financial health · 2024

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

Who owns ØYNA PARKEN EIENDOM AS?

ØYNA PARKEN AS
ØYNA PARKEN EIENDOM AS
NOK 3.1m rev. · NOK 1.7m profit

ØYNA PARKEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYNA PARKEN EIENDOM AS

Who owns ØYNA PARKEN EIENDOM AS?

ØYNA PARKEN AS is the largest registered owner, with 100.0%.

What is the revenue of ØYNA PARKEN EIENDOM AS?

ØYNA PARKEN EIENDOM AS had revenue of NOK 3.1m in 2024.

Where is ØYNA PARKEN EIENDOM AS based?

ØYNA PARKEN EIENDOM AS has its business address in Inderøy.

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.