BIZTRAC BETA
Other specialised construction activities n.e.c.

HAFS BETONGBYGG AS

Org. no. 812232002 Limited company (AS) Fjaler Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 25.1m
Operating profit NOK −2.4m
Equity NOK 1.1m
Incorporated 2013
Employees 11
Share capital NOK 88,000

Signals

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

HAFS BETONGBYGG AS is registered as a limited company in Fjaler, Vestland with organisation number 812232002. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2013 and has 11 registered employees. Registered share capital is NOK 88,000, divided into 88 shares. The company's stated purpose is: “Utføre mur- og betongarbeid, og anna verksemd som naturleg høyrer til.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.1m in revenue and NOK −2.4m in operating profit.

Key figures · 2024

Revenue
NOK 25.1m
Operating profit
NOK −2.4m
Equity
NOK 1.1m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns HAFS BETONGBYGG AS?

EIVIND ANTONISEN
HAFS BETONGBYGG AS
NOK 25.1m rev. · NOK −2.4m profit

HAFS BETONGBYGG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAFS BETONGBYGG AS

Who owns HAFS BETONGBYGG AS?

EIVIND ANTONISEN is the largest registered owner, with 34.1%.

What is the revenue of HAFS BETONGBYGG AS?

HAFS BETONGBYGG AS had revenue of NOK 25.1m in 2024.

Who is the general manager of HAFS BETONGBYGG AS?

Eivind Antonisen is registered as general manager of HAFS BETONGBYGG AS.

Where is HAFS BETONGBYGG AS based?

HAFS BETONGBYGG 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 15.06.2026.

Report a problem

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