BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

HAAKON ELLINGSEN AS

Org. no. 911406829 Limited company (AS) Bærum Incorporated 1962 Active
Ownership graph ↗
Revenue 2025 NOK 262.1m
Operating profit NOK 34.0m
Equity NOK 40.0m
Incorporated 1962
Employees 42
Share capital NOK 3.2m

HAAKON ELLINGSEN AS is registered as a limited company in Bærum, Akershus with organisation number 911406829. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1962 and has 42 registered employees. Registered share capital is NOK 3.2m, divided into 31920 shares. The company's stated purpose is: “Produksjon og handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 262.1m in revenue and NOK 34.0m in operating profit.

Key figures · 2025

Revenue
NOK 262.1m
Operating profit
NOK 34.0m
Equity
NOK 40.0m
Est. value
NOK 127.9m

Financial health · 2025

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

Who owns HAAKON ELLINGSEN AS?

NAMO HOLDING AS
HAAKON ELLINGSEN AS
NOK 262.1m rev. · NOK 34.0m profit

HAAKON ELLINGSEN AS has 5 registered shareholders:

All shareholders and roles →

Group structure

HAAKON ELLINGSEN AS er morselskap for 4 datterselskaper:

Frequently asked questions about HAAKON ELLINGSEN AS

Who owns HAAKON ELLINGSEN AS?

NAMO HOLDING AS is the largest registered owner, with 93.4%.

What is the revenue of HAAKON ELLINGSEN AS?

HAAKON ELLINGSEN AS had revenue of NOK 262.1m in 2025.

Who is the general manager of HAAKON ELLINGSEN AS?

Tina Louise Ree Eines is registered as general manager of HAAKON ELLINGSEN AS.

Where is HAAKON ELLINGSEN AS based?

HAAKON ELLINGSEN AS has its business address in Skui.

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.