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

ELDEN PUKK OG MASKIN AS

Org. no. 912780651 Limited company (AS) Namsos Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK 618,000
Equity NOK 3.8m
Incorporated 2013
Share capital NOK 250,000

ELDEN PUKK OG MASKIN AS is registered as a limited company in Namsos, Trøndelag with organisation number 912780651. 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 2013. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Knusing og frakt av stein, maskinarbeid og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK 618,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK 618,000
Equity
NOK 3.8m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns ELDEN PUKK OG MASKIN AS?

JARLE ELDEN
ELDEN PUKK OG MASKIN AS
NOK 8.1m rev. · NOK 618,000 profit

ELDEN PUKK OG MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ELDEN PUKK OG MASKIN AS own?

ELDEN PUKK OG MASKIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELDEN PUKK OG MASKIN AS

Who owns ELDEN PUKK OG MASKIN AS?

JARLE ELDEN is the largest registered owner, with 50.0%.

What is the revenue of ELDEN PUKK OG MASKIN AS?

ELDEN PUKK OG MASKIN AS had revenue of NOK 8.1m in 2024.

Where is ELDEN PUKK OG MASKIN AS based?

ELDEN PUKK OG MASKIN AS has its business address in Jøa.

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.