BIZTRAC BETA
Manufacture of metal structures and parts of structures

ALUMETALL NORGE AS

Org. no. 914516234 Limited company (AS) Sirdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK −224,000
Equity NOK 117,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

ALUMETALL NORGE AS is registered as a limited company in Sirdal, Agder with organisation number 914516234. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Produksjon og salg av metallkonstruksjoner og alt som naturlig hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK −224,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK −224,000
Equity
NOK 117,000
Est. value
NOK 4.4m

Financial health · 2024

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.9%
Not satisfactory
Equity as a share of total capital

Who owns ALUMETALL NORGE AS?

ALU METALL GROUP O
ALUMETALL NORGE AS
NOK 8.1m rev. · NOK −224,000 profit

ALUMETALL NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALUMETALL NORGE AS

Who owns ALUMETALL NORGE AS?

ALU METALL GROUP O is the largest registered owner, with 100.0%.

What is the revenue of ALUMETALL NORGE AS?

ALUMETALL NORGE AS had revenue of NOK 8.1m in 2024.

Who is the general manager of ALUMETALL NORGE AS?

Elar Meriloo is registered as general manager of ALUMETALL NORGE AS.

Where is ALUMETALL NORGE AS based?

ALUMETALL NORGE AS has its business address in Tonstad.

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.