BIZTRAC BETA
Construction of residential and non-residential buildings

ZURHAAR AS

Org. no. 966767790 Limited company (AS) Bergen Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 16.5m
Operating profit NOK −7.9m
Equity NOK 565.4m
Incorporated 1993
Share capital NOK 8.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7,9 mill kr).

ZURHAAR AS is registered as a limited company in Bergen, Vestland with organisation number 966767790. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1993. Registered share capital is NOK 8.0m, divided into 5000 shares. The company's stated purpose is: “Investering og drift av fast eiendom, også ved aksjebesittelse, samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.5m in revenue and NOK −7.9m in operating profit.

Key figures · 2024

Revenue
NOK 16.5m
Operating profit
NOK −7.9m
Equity
NOK 565.4m
Est. value
NOK 668.5m

Financial health · 2024

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

Who owns ZURHAAR AS?

ZB PROGRESSAS AS
ZURHAAR AS
NOK 16.5m rev. · NOK −7.9m profit

ZURHAAR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ZURHAAR AS own?

ZURHAAR AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about ZURHAAR AS

Who owns ZURHAAR AS?

ZB PROGRESSAS AS is the largest registered owner, with 50.0%.

What is the revenue of ZURHAAR AS?

ZURHAAR AS had revenue of NOK 16.5m in 2024.

Who is the general manager of ZURHAAR AS?

Rune Birkeland is registered as general manager of ZURHAAR AS.

Where is ZURHAAR AS based?

ZURHAAR AS has its business address in Nesttun.

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.