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

NUMEDAL PUKK & STEINPRODUKSJON AS

Org. no. 988322512 Limited company (AS) Nore Og Uvdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 420,000
Equity NOK 4.4m
Incorporated 2005
Share capital NOK 100,000

NUMEDAL PUKK & STEINPRODUKSJON AS is registered as a limited company in Nore Og Uvdal, Buskerud with organisation number 988322512. 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 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon og foredling av masse og pukk, produksjon av murstein samt anleggs- og entreprenørvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 420,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 420,000
Equity
NOK 4.4m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns NUMEDAL PUKK & STEINPRODUKSJON AS?

DOZERDRIFT HOLDING AS
NUMEDAL PUKK & STEINPRODUKSJON AS
NOK 7.0m rev. · NOK 420,000 profit

NUMEDAL PUKK & STEINPRODUKSJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NUMEDAL PUKK & STEINPRODUKSJON AS

Who owns NUMEDAL PUKK & STEINPRODUKSJON AS?

DOZERDRIFT HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of NUMEDAL PUKK & STEINPRODUKSJON AS?

NUMEDAL PUKK & STEINPRODUKSJON AS had revenue of NOK 7.0m in 2024.

Where is NUMEDAL PUKK & STEINPRODUKSJON AS based?

NUMEDAL PUKK & STEINPRODUKSJON AS has its business address in Uvdal.

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.