BIZTRAC BETA
Graphic design and visual communication activities

BELUGA SVALBARD AS

Org. no. 922244669 Limited company (AS) Svalbard Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 182,000
Operating profit NOK −37,000
Equity NOK 35,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−37k kr).

BELUGA SVALBARD AS is registered as a limited company in Svalbard, Svalbard with organisation number 922244669. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Guiding og tilrettelegging av turer, utleie av turutstyr, fotografering, grafisk design og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 182,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 182,000
Operating profit
NOK −37,000
Equity
NOK 35,000
Est. value
NOK 208,000

Financial health · 2025

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

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

Who owns BELUGA SVALBARD AS?

KANERVA KARPO
BELUGA SVALBARD AS
NOK 182,000 rev. · NOK −37,000 profit

BELUGA SVALBARD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BELUGA SVALBARD AS

Who owns BELUGA SVALBARD AS?

KANERVA KARPO is the largest registered owner, with 100.0%.

What is the revenue of BELUGA SVALBARD AS?

BELUGA SVALBARD AS had revenue of NOK 182,000 in 2025.

Where is BELUGA SVALBARD AS based?

BELUGA SVALBARD AS has its business address in Longyearbyen.

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.