BIZTRAC BETA
Masonry and bricklaying activities

HÅLOGALAND BYGG OG BETONG AS

Org. no. 995218666 Limited company (AS) Kvæfjord Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 81,000
Operating profit NOK 9,000
Equity NOK 586,000
Incorporated 2010
Share capital NOK 125,000

HÅLOGALAND BYGG OG BETONG AS is registered as a limited company in Kvæfjord, Troms with organisation number 995218666. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2010. Registered share capital is NOK 125,000, divided into 125 shares. The company's stated purpose is: “Drive med utførende arbeider innen bygnings- og betongarbeid på bygg og andre konstruksjoner. Selskapet skal også gjøre flisearbeid, maling og annet relatert bygningsarbeid.”. The most recent filed accounts, for the 2024 financial year, show NOK 81,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 81,000
Operating profit
NOK 9,000
Equity
NOK 586,000
Est. value
NOK 283,000

Financial health · 2024

Liquidity
41.26
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
97.2%
Very good
Equity as a share of total capital

Who owns HÅLOGALAND BYGG OG BETONG AS?

HÅLOGALAND BRANNTEKNIKK AS
HÅLOGALAND BYGG OG BETONG AS
NOK 81,000 rev. · NOK 9,000 profit

HÅLOGALAND BYGG OG BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HÅLOGALAND BYGG OG BETONG AS

Who owns HÅLOGALAND BYGG OG BETONG AS?

HÅLOGALAND BRANNTEKNIKK AS is the largest registered owner, with 100.0%.

What is the revenue of HÅLOGALAND BYGG OG BETONG AS?

HÅLOGALAND BYGG OG BETONG AS had revenue of NOK 81,000 in 2024.

Where is HÅLOGALAND BYGG OG BETONG AS based?

HÅLOGALAND BYGG OG BETONG AS has its business address in Borkenes.

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.