BIZTRAC BETA
Security activities n.e.c.

POLARVAKT AS

Org. no. 979922914 Limited company (AS) Fauske Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 17.7m
Operating profit NOK 3.2m
Equity NOK 5.5m
Incorporated 1998
Employees 8
Share capital NOK 100,000

POLARVAKT AS is registered as a limited company in Fauske, Nordland with organisation number 979922914. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 1998 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av vaktholdstjenester samt salg av låse- og sikringsmateriell. Intensjonen er også å delta i, eller være eier av lignende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.7m in revenue and NOK 3.2m in operating profit.

Key figures · 2025

Revenue
NOK 17.7m
Operating profit
NOK 3.2m
Equity
NOK 5.5m
Est. value
NOK 13.9m

Financial health · 2025

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

Who owns POLARVAKT AS?

POLARVAKT HOLDING AS
POLARVAKT AS
NOK 17.7m rev. · NOK 3.2m profit

POLARVAKT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does POLARVAKT AS own?

POLARVAKT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about POLARVAKT AS

Who owns POLARVAKT AS?

POLARVAKT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of POLARVAKT AS?

POLARVAKT AS had revenue of NOK 17.7m in 2025.

Who is the general manager of POLARVAKT AS?

Kjell Sverre Jakobsen is registered as general manager of POLARVAKT AS.

Where is POLARVAKT AS based?

POLARVAKT AS has its business address in Fauske.

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.