BIZTRAC BETA
Activities of fitness centres

POLARGYMALTA AS

Org. no. 930800430 Limited company (AS) Alta Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 585,000
Operating profit NOK −56,000
Equity NOK −25,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−25k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−56k kr).

POLARGYMALTA AS is registered as a limited company in Alta, Finnmark with organisation number 930800430. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av treningssenter og det som medfølger innen denne bransje.”. The most recent filed accounts, for the 2024 financial year, show NOK 585,000 in revenue and NOK −56,000 in operating profit.

Key figures · 2024

Revenue
NOK 585,000
Operating profit
NOK −56,000
Equity
NOK −25,000

Financial health · 2024

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-20.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns POLARGYMALTA AS?

HÅVARD DØNNESTAD
POLARGYMALTA AS
NOK 585,000 rev. · NOK −56,000 profit

POLARGYMALTA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POLARGYMALTA AS

Who owns POLARGYMALTA AS?

HÅVARD DØNNESTAD is the largest registered owner, with 100.0%.

What is the revenue of POLARGYMALTA AS?

POLARGYMALTA AS had revenue of NOK 585,000 in 2024.

Who is the general manager of POLARGYMALTA AS?

Håvard Dønnestad is registered as general manager of POLARGYMALTA AS.

Where is POLARGYMALTA AS based?

POLARGYMALTA AS has its business address in Alta.

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.