BIZTRAC BETA
Aluminium production

ALUDYNE NORWAY AS

Org. no. 919789891 Limited company (AS) Farsund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 405.4m
Operating profit NOK −23.5m
Equity NOK 41.4m
Incorporated 2017
Employees 219
Share capital NOK 3.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23,5 mill kr).
  • Nylig endring 2026-05-13 Aksjekapital registrert 2026-05-13.

ALUDYNE NORWAY AS is registered as a limited company in Farsund, Agder with organisation number 919789891. The business is classified under aluminium production (NACE 24.420). The company was incorporated in 2017 and has 219 registered employees. Registered share capital is NOK 3.0m, divided into 3030000 shares. The company's stated purpose is: “Aluminiumsstøping og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 405.4m in revenue and NOK −23.5m in operating profit.

Key figures · 2024

Revenue
NOK 405.4m
Operating profit
NOK −23.5m
Equity
NOK 41.4m
Est. value
NOK 179.6m

Financial health · 2024

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

Who owns ALUDYNE NORWAY AS?

ALUDYNE INC.
ALUDYNE NORWAY AS
NOK 405.4m rev. · NOK −23.5m profit

ALUDYNE NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALUDYNE NORWAY AS

Who owns ALUDYNE NORWAY AS?

ALUDYNE INC. is the largest registered owner, with 100.0%.

What is the revenue of ALUDYNE NORWAY AS?

ALUDYNE NORWAY AS had revenue of NOK 405.4m in 2024.

Who is the general manager of ALUDYNE NORWAY AS?

Lill Hege Hals is registered as general manager of ALUDYNE NORWAY AS.

Where is ALUDYNE NORWAY AS based?

ALUDYNE NORWAY AS has its business address in Farsund.

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.