BIZTRAC BETA
Sports and recreation education

SVALBARD YOGA AS

Org. no. 919363339 Limited company (AS) Svalbard Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK −24,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−24k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

SVALBARD YOGA AS is registered as a limited company in Svalbard, Svalbard with organisation number 919363339. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Yogaundervisning og yogaretreats og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK −24,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-38288.9%
Weak
Equity as a share of total capital

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

Who owns SVALBARD YOGA AS?

Tone Lise Gjelsten Rekdal
SVALBARD YOGA AS
NOK 0 rev. · NOK −14,000 profit

SVALBARD YOGA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVALBARD YOGA AS

Who owns SVALBARD YOGA AS?

Tone Lise Gjelsten Rekdal is the largest registered owner, with 100.0%.

What is the revenue of SVALBARD YOGA AS?

SVALBARD YOGA AS had revenue of NOK 0 in 2025.

Where is SVALBARD YOGA AS based?

SVALBARD YOGA 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.