BIZTRAC BETA
Rental and operating of own or leased real estate

BALLANGEN HOLDING AS

Org. no. 927915685 Limited company (AS) Narvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 885,000
Operating profit NOK −417,000
Equity NOK 114.4m
Incorporated 2021
Share capital NOK 1.4m

Signals

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

BALLANGEN HOLDING AS is registered as a limited company in Narvik, Nordland with organisation number 927915685. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 1.4m, divided into 1446 shares. The company's stated purpose is: “Investeringsselskap for både aktive og passive kapitalplasseringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 885,000 in revenue and NOK −417,000 in operating profit.

Key figures · 2024

Revenue
NOK 885,000
Operating profit
NOK −417,000
Equity
NOK 114.4m
Est. value
NOK 763.6m

Financial health · 2024

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

Who owns BALLANGEN HOLDING AS?

KRAUM AS
BALLANGEN HOLDING AS
NOK 885,000 rev. · NOK −417,000 profit

BALLANGEN HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BALLANGEN HOLDING AS

Who owns BALLANGEN HOLDING AS?

KRAUM AS is the largest registered owner, with 40.0%.

What is the revenue of BALLANGEN HOLDING AS?

BALLANGEN HOLDING AS had revenue of NOK 885,000 in 2024.

Who is the general manager of BALLANGEN HOLDING AS?

Svein Olaf Bakke is registered as general manager of BALLANGEN HOLDING AS.

Where is BALLANGEN HOLDING AS based?

BALLANGEN HOLDING AS has its business address in Ballangen.

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.