BIZTRAC BETA
Building of civilian ships and floating structures

ORTNEVIK EIENDOM AS

Org. no. 919029110 Limited company (AS) Høyanger Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 759,000
Equity NOK 796,000
Incorporated 2017
Share capital NOK 1.5m

Signals

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

ORTNEVIK EIENDOM AS is registered as a limited company in Høyanger, Vestland with organisation number 919029110. The business is classified under building of civilian ships and floating structures (NACE 30.110). The company was incorporated in 2017. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Kjøp og salg og drift av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 759,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 759,000
Equity
NOK 796,000
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns ORTNEVIK EIENDOM AS?

ORTNA HOLDING AS
ORTNEVIK EIENDOM AS
NOK 1.4m rev. · NOK 759,000 profit

ORTNEVIK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORTNEVIK EIENDOM AS

Who owns ORTNEVIK EIENDOM AS?

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

What is the revenue of ORTNEVIK EIENDOM AS?

ORTNEVIK EIENDOM AS had revenue of NOK 1.4m in 2025.

Who is the general manager of ORTNEVIK EIENDOM AS?

Helge Dyrrdal is registered as general manager of ORTNEVIK EIENDOM AS.

Where is ORTNEVIK EIENDOM AS based?

ORTNEVIK EIENDOM AS has its business address in Bjordal.

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.