BIZTRAC BETA
COMPANY REGISTER PROFILE
975822257 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Site preparation

KÅRE HAALAND AS

Org. no. 975822257 Limited company (AS) Fjaler Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK −1.2m
Equity NOK −651,000
Incorporated 1995
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−651k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,2 mill kr).

KÅRE HAALAND AS is registered as a limited company in Fjaler, Vestland with organisation number 975822257. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1995. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Maskinentreprenør innen bygg og anlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK −1.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
▼ −9 %
Operating profit
NOK −1.2m
▼ −1126 %
Equity
NOK −651,000
▼ −209 %

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
-28.6%
Not satisfactory
Return on total assets
Solidity
-17.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KÅRE HAALAND AS?

KÅRE HAALAND AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KÅRE HAALAND AS

Who owns KÅRE HAALAND AS?

KÅRE HAALAND is the largest registered owner, with 64.0%.

What is the revenue of KÅRE HAALAND AS?

KÅRE HAALAND AS had revenue of NOK 3.2m in 2025.

Who is the general manager of KÅRE HAALAND AS?

Kåre Haaland is registered as general manager of KÅRE HAALAND AS.

Where is KÅRE HAALAND AS based?

KÅRE HAALAND AS has its business address in Dale I Sunnfjord.

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

Report a problem

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