biztrac. BETA
COMPANY REGISTER PROFILE
892624992 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

HADARHUS AS

Org. no. 892624992 Limited company (AS) Hareid Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 30.0m
Operating profit NOK 370,000
Equity NOK 2.9m
Incorporated 2008
Employees 10
Share capital NOK 3.0m

HADARHUS AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 892624992. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008 and has 10 registered employees. Registered share capital is NOK 3.0m, divided into 3000 shares. The company's stated purpose is: “Entreprenør virksomhet innen bygg og anlegg, samt deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 30.0m in revenue and NOK 370,000 in operating profit.

Former names: TRELAST AS

Key figures · 2025

Revenue
NOK 30.0m
▼ −44 %
Operating profit
NOK 370,000
▼ −59 %
Equity
NOK 2.9m
▲ +3 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
2.2%
Weak
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns HADARHUS AS?

HADARHUS AS
NOK 30.0m rev. · NOK 370,000 profit

HADARHUS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HADARHUS AS

Who owns HADARHUS AS?

Kristoffer Kvammen is the largest registered owner, with 50.0%.

What is the revenue of HADARHUS AS?

HADARHUS AS had revenue of NOK 30.0m in 2025.

Who is the general manager of HADARHUS AS?

Terje Giskeødegård Balsnes is registered as general manager of HADARHUS AS.

Where is HADARHUS AS based?

HADARHUS AS has its business address in Hareid.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.