BIZTRAC BETA
COMPANY REGISTER PROFILE
916041977 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

ARKTISK KOMPETANSE AS

Org. no. 916041977 Limited company (AS) Vågan Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 15,000
Operating profit NOK −21,000
Equity NOK 3.2m
Incorporated 2015
Share capital NOK 30,000

Signals

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

ARKTISK KOMPETANSE AS is registered as a limited company in Vågan, Nordland with organisation number 916041977. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Rådgivning og produktutvikling for reiseliv og tilknyttede næringer”. The most recent filed accounts, for the 2024 financial year, show NOK 15,000 in revenue and NOK −21,000 in operating profit.

Former names: STCS AS

Key figures · 2024

Revenue
NOK 15,000
Operating profit
NOK −21,000
Equity
NOK 3.2m
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns ARKTISK KOMPETANSE AS?

TRYGVE STEEN
ARKTISK KOMPETANSE AS
NOK 15,000 rev. · NOK −21,000 profit

ARKTISK KOMPETANSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARKTISK KOMPETANSE AS

Who owns ARKTISK KOMPETANSE AS?

TRYGVE STEEN is the largest registered owner, with 100.0%.

What is the revenue of ARKTISK KOMPETANSE AS?

ARKTISK KOMPETANSE AS had revenue of NOK 15,000 in 2024.

Where is ARKTISK KOMPETANSE AS based?

ARKTISK KOMPETANSE AS has its business address in Kabelvåg.

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.