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

KVÅLSGREND PUKK AS

Org. no. 985512159 Limited company (AS) Tokke Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −800,000
Equity NOK 5.3m
Incorporated 2003
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−800k kr).

KVÅLSGREND PUKK AS is registered as a limited company in Tokke, Telemark with organisation number 985512159. 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 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvinning fra grus- og sandtak, godstransport på veg og alt som dertil tilhører.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −800,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −800,000
Equity
NOK 5.3m
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns KVÅLSGREND PUKK AS?

HÅVARD ÅMOT
KVÅLSGREND PUKK AS
NOK 1.9m rev. · NOK −800,000 profit

KVÅLSGREND PUKK AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVÅLSGREND PUKK AS

Who owns KVÅLSGREND PUKK AS?

HÅVARD ÅMOT is the largest registered owner, with 25.0%.

What is the revenue of KVÅLSGREND PUKK AS?

KVÅLSGREND PUKK AS had revenue of NOK 1.9m in 2024.

Who is the general manager of KVÅLSGREND PUKK AS?

Håvard Åmot is registered as general manager of KVÅLSGREND PUKK AS.

Where is KVÅLSGREND PUKK AS based?

KVÅLSGREND PUKK AS has its business address in Høydalsmo.

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.