BIZTRAC BETA
Manufacture of ready-mixed concrete

NUMEDAL BETONG AS

Org. no. 981678834 Limited company (AS) Nore Og Uvdal Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 14.2m
Operating profit NOK 809,000
Equity NOK 2.1m
Incorporated 2000
Share capital NOK 105,000

NUMEDAL BETONG AS is registered as a limited company in Nore Og Uvdal, Buskerud with organisation number 981678834. The business is classified under manufacture of ready-mixed concrete (NACE 23.630). The company was incorporated in 2000. Registered share capital is NOK 105,000, divided into 105 shares. The company's stated purpose is: “Produksjon og salg av betong med alt som naturlig hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.2m in revenue and NOK 809,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.2m
Operating profit
NOK 809,000
Equity
NOK 2.1m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns NUMEDAL BETONG AS?

BERGSTØL PUKKVERK OG SANDTAK AS
NUMEDAL BETONG AS
NOK 14.2m rev. · NOK 809,000 profit

NUMEDAL BETONG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NUMEDAL BETONG AS own?

NUMEDAL BETONG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NUMEDAL BETONG AS

Who owns NUMEDAL BETONG AS?

BERGSTØL PUKKVERK OG SANDTAK AS is the largest registered owner, with 66.7%.

What is the revenue of NUMEDAL BETONG AS?

NUMEDAL BETONG AS had revenue of NOK 14.2m in 2024.

Who is the general manager of NUMEDAL BETONG AS?

Tore Gunnar Bergstøl is registered as general manager of NUMEDAL BETONG AS.

Where is NUMEDAL BETONG AS based?

NUMEDAL BETONG AS has its business address in Nore.

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.