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

MØLLENG MASKIN & PUKK AS

Org. no. 876081172 Limited company (AS) Nordreisa Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 39
Incorporated 1996
Share capital NOK 100,000

MØLLENG MASKIN & PUKK AS is registered as a limited company in Nordreisa, Troms with organisation number 876081172. 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 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Knuseverk, entreprenørvirksomhet og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 39
Est. value
NOK 39

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MØLLENG MASKIN & PUKK AS?

KJELL OLAV MØLLENG
MØLLENG MASKIN & PUKK AS
NOK 0 rev. · NOK 0 profit

MØLLENG MASKIN & PUKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MØLLENG MASKIN & PUKK AS

Who owns MØLLENG MASKIN & PUKK AS?

KJELL OLAV MØLLENG is the largest registered owner, with 100.0%.

What is the revenue of MØLLENG MASKIN & PUKK AS?

MØLLENG MASKIN & PUKK AS had revenue of NOK 0 in 2025.

Who is the general manager of MØLLENG MASKIN & PUKK AS?

Kjell Olav Mølleng is registered as general manager of MØLLENG MASKIN & PUKK AS.

Where is MØLLENG MASKIN & PUKK AS based?

MØLLENG MASKIN & PUKK AS has its business address in Storslett.

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.