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

TYNSET BETONG AS

Org. no. 938997144 Limited company (AS) Tynset Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −276,000
Equity NOK 9.8m
Incorporated 1986
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−276k kr).

TYNSET BETONG AS is registered as a limited company in Tynset, Innlandet with organisation number 938997144. 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 1986. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Produksjon og salg av ferdigbetong, betongele- menter o.l. til betongindustrien.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −276,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK −276,000
Equity
NOK 9.8m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns TYNSET BETONG AS?

JON BERNHARD WINTERVOLD
TYNSET BETONG AS
NOK 1.6m rev. · NOK −276,000 profit

TYNSET BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TYNSET BETONG AS

Who owns TYNSET BETONG AS?

JON BERNHARD WINTERVOLD is the largest registered owner, with 100.0%.

What is the revenue of TYNSET BETONG AS?

TYNSET BETONG AS had revenue of NOK 1.6m in 2025.

Who is the general manager of TYNSET BETONG AS?

Jon Bernhard Wintervold is registered as general manager of TYNSET BETONG AS.

Where is TYNSET BETONG AS based?

TYNSET BETONG AS has its business address in Tynset.

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.