BIZTRAC BETA
Combined facilities support activities

POLARDRIFT AS

Org. no. 931152491 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 14,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

POLARDRIFT AS is registered as a limited company in Tromsø, Troms with organisation number 931152491. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive konsulentvirksomhet, utleie av utstyr og kjøretøy, vaktmestertjenester og annen naturlig tilknyttet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 14,000
Est. value
NOK 20,000

Financial health · 2024

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

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

Who owns POLARDRIFT AS?

BJØRN VIDAR BUGJERDE SØRENSEN
POLARDRIFT AS
NOK 0 rev. · NOK −6,000 profit

POLARDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does POLARDRIFT AS own?

POLARDRIFT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about POLARDRIFT AS

Who owns POLARDRIFT AS?

BJØRN VIDAR BUGJERDE SØRENSEN is the largest registered owner, with 100.0%.

What is the revenue of POLARDRIFT AS?

POLARDRIFT AS had revenue of NOK 0 in 2024.

Where is POLARDRIFT AS based?

POLARDRIFT AS has its business address in Kvaløysletta.

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.