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

TRYSIL PUKKVERK AS

Org. no. 995976285 Limited company (AS) Trysil Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 11.8m
Operating profit NOK 1.3m
Equity NOK 3.1m
Incorporated 2010
Share capital NOK 3.0m

TRYSIL PUKKVERK AS is registered as a limited company in Trysil, Innlandet with organisation number 995976285. 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 2010. Registered share capital is NOK 3.0m, divided into 3000 shares. The company's stated purpose is: “Drive pukkverk og annen virksomhet som naturlig hører inn under dette. Selskapet kan også gjøre seg interessert i andre selskaper ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 11.8m
Operating profit
NOK 1.3m
Equity
NOK 3.1m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns TRYSIL PUKKVERK AS?

MIKAEL MELBY BAKKEN
TRYSIL PUKKVERK AS
NOK 11.8m rev. · NOK 1.3m profit

TRYSIL PUKKVERK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRYSIL PUKKVERK AS

Who owns TRYSIL PUKKVERK AS?

MIKAEL MELBY BAKKEN is the largest registered owner, with 50.0%.

What is the revenue of TRYSIL PUKKVERK AS?

TRYSIL PUKKVERK AS had revenue of NOK 11.8m in 2024.

Who is the general manager of TRYSIL PUKKVERK AS?

Mikael Melby Bakken is registered as general manager of TRYSIL PUKKVERK AS.

Where is TRYSIL PUKKVERK AS based?

TRYSIL PUKKVERK AS has its business address in Trysil.

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.