BIZTRAC BETA
Rental and operating of own or leased real estate

ORMAHAUGVEGEN 2 AS

Org. no. 972417483 Limited company (AS) Øygarden Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −164,000
Equity NOK 4.4m
Incorporated 1995
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−164k kr).

ORMAHAUGVEGEN 2 AS is registered as a limited company in Øygarden, Vestland with organisation number 972417483. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1995. Registered share capital is NOK 400,000, divided into 800 shares. The company's stated purpose is: “Kjøp, utleie, salg og drift av eiendommer og dertil hørende virksomhet samt investering i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −164,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −164,000
Equity
NOK 4.4m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns ORMAHAUGVEGEN 2 AS?

RAPTUS AS
ORMAHAUGVEGEN 2 AS
NOK 1.2m rev. · NOK −164,000 profit

ORMAHAUGVEGEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORMAHAUGVEGEN 2 AS

Who owns ORMAHAUGVEGEN 2 AS?

RAPTUS AS is the largest registered owner, with 100.0%.

What is the revenue of ORMAHAUGVEGEN 2 AS?

ORMAHAUGVEGEN 2 AS had revenue of NOK 1.2m in 2025.

Who is the general manager of ORMAHAUGVEGEN 2 AS?

Trond Turøy is registered as general manager of ORMAHAUGVEGEN 2 AS.

Where is ORMAHAUGVEGEN 2 AS based?

ORMAHAUGVEGEN 2 AS has its business address in Ågotnes.

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.