BIZTRAC BETA
Construction of residential and non-residential buildings

HAKO TOTAL AS

Org. no. 917074275 Limited company (AS) Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 60.7m
Operating profit NOK 2.5m
Equity NOK 10.6m
Incorporated 2016
Employees 18
Share capital NOK 300,000

HAKO TOTAL AS is registered as a limited company in Hå, Rogaland with organisation number 917074275. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016 and has 18 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Levering av komplett bygg for landbruk og industri, handel og dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 60.7m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 60.7m
Operating profit
NOK 2.5m
Equity
NOK 10.6m
Est. value
NOK 14.0m

Financial health · 2024

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

Who owns HAKO TOTAL AS?

HIGGS HOLDING AS
HAKO TOTAL AS
NOK 60.7m rev. · NOK 2.5m profit

HAKO TOTAL AS has 3 registered shareholders:

All shareholders and roles →

Which companies does HAKO TOTAL AS own?

HAKO TOTAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAKO TOTAL AS

Who owns HAKO TOTAL AS?

HIGGS HOLDING AS is the largest registered owner, with 45.0%.

What is the revenue of HAKO TOTAL AS?

HAKO TOTAL AS had revenue of NOK 60.7m in 2024.

Who is the general manager of HAKO TOTAL AS?

Erik Lunde is registered as general manager of HAKO TOTAL AS.

Where is HAKO TOTAL AS based?

HAKO TOTAL AS has its business address in Varhaug.

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.