BIZTRAC BETA
Other specialised construction activities n.e.c.

POLARKRAN AS

Org. no. 999514081 Limited company (AS) Rana Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 21.0m
Operating profit NOK 1.5m
Equity NOK 6.3m
Incorporated 2012
Employees 14
Share capital NOK 1.0m

POLARKRAN AS is registered as a limited company in Rana, Nordland with organisation number 999514081. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2012 and has 14 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kranutleie, og andre tjenester som naturlig hører sammen med dette, herunder å delta på eiersiden i selskap som driver innen sammen næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.0m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 21.0m
Operating profit
NOK 1.5m
Equity
NOK 6.3m
Est. value
NOK 5.4m

Financial health · 2024

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.8%
Good
Equity as a share of total capital

Who owns POLARKRAN AS?

POLARTRANS AS
POLARKRAN AS
NOK 21.0m rev. · NOK 1.5m profit

POLARKRAN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does POLARKRAN AS own?

POLARKRAN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about POLARKRAN AS

Who owns POLARKRAN AS?

POLARTRANS AS is the largest registered owner, with 100.0%.

What is the revenue of POLARKRAN AS?

POLARKRAN AS had revenue of NOK 21.0m in 2024.

Who is the general manager of POLARKRAN AS?

Ronny Solli is registered as general manager of POLARKRAN AS.

Where is POLARKRAN AS based?

POLARKRAN AS has its business address in Mo I Rana.

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.