BIZTRAC BETA
Construction of residential and non-residential buildings

HAUG BYGGTEKNIKK AS

Org. no. 918853723 Limited company (AS) Haugesund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 420,000
Operating profit NOK 2,000
Equity NOK 121,000
Incorporated 2017
Share capital NOK 30,000

HAUG BYGGTEKNIKK AS is registered as a limited company in Haugesund, Rogaland with organisation number 918853723. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tømrervirksomhet, oppføring av bygninger og programvirksomhet innen bygg og anlegg, samt det som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 420,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2024

Revenue
NOK 420,000
Operating profit
NOK 2,000
Equity
NOK 121,000
Est. value
NOK 60,000

Financial health · 2024

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

Who owns HAUG BYGGTEKNIKK AS?

LARS MARTIN WHITE HAUG
HAUG BYGGTEKNIKK AS
NOK 420,000 rev. · NOK 2,000 profit

HAUG BYGGTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAUG BYGGTEKNIKK AS

Who owns HAUG BYGGTEKNIKK AS?

LARS MARTIN WHITE HAUG is the largest registered owner, with 100.0%.

What is the revenue of HAUG BYGGTEKNIKK AS?

HAUG BYGGTEKNIKK AS had revenue of NOK 420,000 in 2024.

Who is the general manager of HAUG BYGGTEKNIKK AS?

Lars Martin White Haug is registered as general manager of HAUG BYGGTEKNIKK AS.

Where is HAUG BYGGTEKNIKK AS based?

HAUG BYGGTEKNIKK AS has its business address in Haugesund.

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.