BIZTRAC BETA
Civil engineering activities

ØVREHUS HOLDING AS

Org. no. 989142828 Limited company (AS) Hjelmeland Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 129,000
Equity NOK 6.8m
Incorporated 2005
Share capital NOK 280,000

ØVREHUS HOLDING AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 989142828. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2005. Registered share capital is NOK 280,000, divided into 280 shares. The company's stated purpose is: “Konsulentvirksomhet innen bygg og anlegg og å eie aksjer og andeler i andre selskap, samt beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 129,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 129,000
Equity
NOK 6.8m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns ØVREHUS HOLDING AS?

FRODE ØVREHUS
ØVREHUS HOLDING AS
NOK 1.1m rev. · NOK 129,000 profit

ØVREHUS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØVREHUS HOLDING AS own?

ØVREHUS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ØVREHUS HOLDING AS

Who owns ØVREHUS HOLDING AS?

FRODE ØVREHUS is the largest registered owner, with 100.0%.

What is the revenue of ØVREHUS HOLDING AS?

ØVREHUS HOLDING AS had revenue of NOK 1.1m in 2025.

Who is the general manager of ØVREHUS HOLDING AS?

Frode Øvrehus is registered as general manager of ØVREHUS HOLDING AS.

Where is ØVREHUS HOLDING AS based?

ØVREHUS HOLDING AS has its business address in Fister.

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.