BIZTRAC BETA
Activities of adventure companies

TASTE OF THE ARCTIC AS

Org. no. 929553691 Limited company (AS) Harstad Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 250,000
Equity NOK 324,000
Incorporated 2022
Share capital NOK 30,000

TASTE OF THE ARCTIC AS is registered as a limited company in Harstad, Troms with organisation number 929553691. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Levere tjenester innenfor reiseliv, arrangement og opplevelser, Samt det som hører naturlig til. Selskapet skal også kunne kjøpe og eie aksjer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 250,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 250,000
Equity
NOK 324,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns TASTE OF THE ARCTIC AS?

PER HELGE JOHNSEN
TASTE OF THE ARCTIC AS
NOK 1.4m rev. · NOK 250,000 profit

TASTE OF THE ARCTIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TASTE OF THE ARCTIC AS

Who owns TASTE OF THE ARCTIC AS?

PER HELGE JOHNSEN is the largest registered owner, with 100.0%.

What is the revenue of TASTE OF THE ARCTIC AS?

TASTE OF THE ARCTIC AS had revenue of NOK 1.4m in 2024.

Who is the general manager of TASTE OF THE ARCTIC AS?

Per Helge Johnsen is registered as general manager of TASTE OF THE ARCTIC AS.

Where is TASTE OF THE ARCTIC AS based?

TASTE OF THE ARCTIC AS has its business address in Harstad.

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.