BIZTRAC BETA
Site preparation

HANS G HASVOLD AS

Org. no. 929500652 Limited company (AS) Nordre Land Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 19.1m
Operating profit NOK 2.1m
Equity NOK 2.9m
Incorporated 2022
Share capital NOK 2.0m

HANS G HASVOLD AS is registered as a limited company in Nordre Land, Innlandet with organisation number 929500652. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 2.0m, divided into 100 shares. The company's stated purpose is: “Utleie av maskiner og utstyr, entreprenørvirksomhet som omfatter grunnarbeider og drift av pukkverk, samt annet som naturlig hører inn under denne type virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.1m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 19.1m
Operating profit
NOK 2.1m
Equity
NOK 2.9m
Est. value
NOK 7.4m

Financial health · 2024

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

Who owns HANS G HASVOLD AS?

HANS GJEFLE HASVOLD
HANS G HASVOLD AS
NOK 19.1m rev. · NOK 2.1m profit

HANS G HASVOLD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HANS G HASVOLD AS own?

HANS G HASVOLD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HANS G HASVOLD AS

Who owns HANS G HASVOLD AS?

HANS GJEFLE HASVOLD is the largest registered owner, with 100.0%.

What is the revenue of HANS G HASVOLD AS?

HANS G HASVOLD AS had revenue of NOK 19.1m in 2024.

Who is the general manager of HANS G HASVOLD AS?

Hans Gjefle Hasvold is registered as general manager of HANS G HASVOLD AS.

Where is HANS G HASVOLD AS based?

HANS G HASVOLD AS has its business address in Dokka.

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.