BIZTRAC BETA
Operation of gravel and sand pits and mining of clay and kaolin

PUKK 1 HADELAND AS

Org. no. 998443822 Limited company (AS) Gran Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 12.5m
Operating profit NOK 46,000
Equity NOK 5.4m
Incorporated 2012
Share capital NOK 30,000

PUKK 1 HADELAND AS is registered as a limited company in Gran, Innlandet with organisation number 998443822. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av pukk og andre masser og andre produkter/tjenester som naturlig hører sammen med dette. Samt mottak av rene masser for lagring på angitt område.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.5m in revenue and NOK 46,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.5m
Operating profit
NOK 46,000
Equity
NOK 5.4m
Est. value
NOK 3.4m

Financial health · 2024

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

Who owns PUKK 1 HADELAND AS?

NICOLAI STENERSEN
PUKK 1 HADELAND AS
NOK 12.5m rev. · NOK 46,000 profit

PUKK 1 HADELAND AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PUKK 1 HADELAND AS

Who owns PUKK 1 HADELAND AS?

NICOLAI STENERSEN is the largest registered owner, with 60.0%.

What is the revenue of PUKK 1 HADELAND AS?

PUKK 1 HADELAND AS had revenue of NOK 12.5m in 2024.

Who is the general manager of PUKK 1 HADELAND AS?

Nicolai Stenersen is registered as general manager of PUKK 1 HADELAND AS.

Where is PUKK 1 HADELAND AS based?

PUKK 1 HADELAND AS has its business address in Jaren.

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.