BIZTRAC BETA
Manufacture of doors and windows of wood

HOVLAND TREVAREFABRIKK AS

Org. no. 811280852 Limited company (AS) Eigersund Incorporated 1972 Active
Ownership graph ↗
Revenue 2025 NOK 32.9m
Operating profit NOK 1.2m
Equity NOK 1.9m
Incorporated 1972
Employees 19
Share capital NOK 41,000

HOVLAND TREVAREFABRIKK AS is registered as a limited company in Eigersund, Rogaland with organisation number 811280852. The business is classified under manufacture of doors and windows of wood (NACE 16.250). The company was incorporated in 1972 and has 19 registered employees. Registered share capital is NOK 41,000, divided into 203 shares. The company's stated purpose is: “Fabrikk- og handelsvirksomhet samt deltakelse i andre selskaper og finansiering av disse.”. The most recent filed accounts, for the 2025 financial year, show NOK 32.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 32.9m
Operating profit
NOK 1.2m
Equity
NOK 1.9m
Est. value
NOK 5.5m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.6%
Good
Equity as a share of total capital

Who owns HOVLAND TREVAREFABRIKK AS?

OLAF HOVLAND
HOVLAND TREVAREFABRIKK AS
NOK 32.9m rev. · NOK 1.2m profit

HOVLAND TREVAREFABRIKK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOVLAND TREVAREFABRIKK AS

Who owns HOVLAND TREVAREFABRIKK AS?

OLAF HOVLAND is the largest registered owner, with 59.1%.

What is the revenue of HOVLAND TREVAREFABRIKK AS?

HOVLAND TREVAREFABRIKK AS had revenue of NOK 32.9m in 2025.

Who is the general manager of HOVLAND TREVAREFABRIKK AS?

Olaf Hovland is registered as general manager of HOVLAND TREVAREFABRIKK AS.

Where is HOVLAND TREVAREFABRIKK AS based?

HOVLAND TREVAREFABRIKK AS has its business address in Hellvik.

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.