biztrac. BETA
COMPANY REGISTER PROFILE
983082807 ORG. NO. 2018 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BALLANGEN FLERBRUKSHALL SA

Org. no. 983082807 Co-operation (SA) Narvik Incorporated 1999 Active
Ownership graph ↗
Revenue 2018 NOK 2.4m
Operating profit NOK 245,000
Equity NOK 730,000
Incorporated 1999

BALLANGEN FLERBRUKSHALL SA is registered as a co-operation in Narvik, Nordland with organisation number 983082807. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. The company's stated purpose is: “Bygge og drive en flerbrukshall for dermed å skaffe stedets innbyggere en idrettshall, kantine, treningssenter, møterom, ungdomslokaler, kontorer og utleieareal.”. The most recent filed accounts, for the 2018 financial year, show NOK 2.4m in revenue and NOK 245,000 in operating profit.

Former names: BALLANGEN FLERBRUKSHALL BA

Key figures · 2018

Revenue
NOK 2.4m
▲ +9 %
Operating profit
NOK 245,000
▲ +86 %
Equity
NOK 730,000
▼ −9 %
Est. value
NOK 821,000

Financial health · 2018

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
1.3%
Weak
Return on total assets
Solidity
3.9%
Weak
Equity as a share of total capital

Who owns BALLANGEN FLERBRUKSHALL SA?

No shareholders are registered for BALLANGEN FLERBRUKSHALL SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BALLANGEN FLERBRUKSHALL SA

What is the revenue of BALLANGEN FLERBRUKSHALL SA?

BALLANGEN FLERBRUKSHALL SA had revenue of NOK 2.4m in 2018.

Who is the general manager of BALLANGEN FLERBRUKSHALL SA?

Ove Harald Storøy is registered as general manager of BALLANGEN FLERBRUKSHALL SA.

Where is BALLANGEN FLERBRUKSHALL SA based?

BALLANGEN FLERBRUKSHALL SA has its business address in Ballangen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.