BIZTRAC BETA
Retail sale of cultural and recreational goods n.e.c.

POLAR SHIP BROKER AS

Org. no. 961204127 Limited company (AS) Bodø Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 100,000
Operating profit NOK −49,000
Equity NOK 33,000
Incorporated 1991
Share capital NOK 273,000

Signals

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

POLAR SHIP BROKER AS is registered as a limited company in Bodø, Nordland with organisation number 961204127. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 1991. Registered share capital is NOK 273,000, divided into 273 shares. The company's stated purpose is: “Handelsvirksomhet, herunder brukthandel, skipsmegling, deltakelse i andre aksjeselskaper samt det som derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 100,000 in revenue and NOK −49,000 in operating profit.

Key figures · 2024

Revenue
NOK 100,000
Operating profit
NOK −49,000
Equity
NOK 33,000
Est. value
NOK 48,000

Financial health · 2024

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

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

Who owns POLAR SHIP BROKER AS?

SIGURD TORRISSEN
POLAR SHIP BROKER AS
NOK 100,000 rev. · NOK −49,000 profit

POLAR SHIP BROKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POLAR SHIP BROKER AS

Who owns POLAR SHIP BROKER AS?

SIGURD TORRISSEN is the largest registered owner, with 100.0%.

What is the revenue of POLAR SHIP BROKER AS?

POLAR SHIP BROKER AS had revenue of NOK 100,000 in 2024.

Where is POLAR SHIP BROKER AS based?

POLAR SHIP BROKER AS has its business address in Bodø.

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.