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

SIGDALPUKK AS

Org. no. 998348897 Limited company (AS) Sigdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 9.8m
Operating profit NOK −1.5m
Equity NOK 2.0m
Incorporated 2012
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).

SIGDALPUKK AS is registered as a limited company in Sigdal, Buskerud with organisation number 998348897. 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 300,000, divided into 300 shares. The company's stated purpose is: “Pukkverk, steinknusing, transport, sprengning, entreprenørvirksomhet og investering i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.8m in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 9.8m
Operating profit
NOK −1.5m
Equity
NOK 2.0m
Est. value
NOK 7.9m

Financial health · 2024

Liquidity
1.36
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.0%
Good
Equity as a share of total capital

Who owns SIGDALPUKK AS?

S&E HOLDING AS
SIGDALPUKK AS
NOK 9.8m rev. · NOK −1.5m profit

SIGDALPUKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIGDALPUKK AS

Who owns SIGDALPUKK AS?

S&E HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SIGDALPUKK AS?

SIGDALPUKK AS had revenue of NOK 9.8m in 2024.

Who is the general manager of SIGDALPUKK AS?

Per Enger is registered as general manager of SIGDALPUKK AS.

Where is SIGDALPUKK AS based?

SIGDALPUKK AS has its business address in Nedre Eggedal.

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.