BIZTRAC BETA
Marine fishing

POLARTRADE AS

Org. no. 997795156 Limited company (AS) Alstahaug Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −29,000
Equity NOK −148,000
Incorporated 2011
Share capital NOK 401,000

Signals

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

POLARTRADE AS is registered as a limited company in Alstahaug, Nordland with organisation number 997795156. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2011. Registered share capital is NOK 401,000, divided into 573 shares. The company's stated purpose is: “Drive fiske og fangst og dertil knyttet virksomhet samt drive rådgiving og ha konsulentoppdrag til marine og havromsrelaterte næringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK −148,000

Financial health · 2024

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

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

Who owns POLARTRADE AS?

BOE CONSULT AS
POLARTRADE AS
NOK 0 rev. · NOK −29,000 profit

POLARTRADE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POLARTRADE AS

Who owns POLARTRADE AS?

BOE CONSULT AS is the largest registered owner, with 100.0%.

What is the revenue of POLARTRADE AS?

POLARTRADE AS had revenue of NOK 0 in 2024.

Who is the general manager of POLARTRADE AS?

Jan Tore Bø is registered as general manager of POLARTRADE AS.

Where is POLARTRADE AS based?

POLARTRADE AS has its business address in Sandnessjøen.

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.