BIZTRAC BETA
Activities of excursion and event organisers

SOGNDAL LIVE AS

Org. no. 927400006 Limited company (AS) Sogndal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 167,000
Operating profit NOK −92,000
Equity NOK −25,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−25k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−92k kr).

SOGNDAL LIVE AS is registered as a limited company in Sogndal, Vestland with organisation number 927400006. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Arrangere konsertar, eventar, festivalar og annna tilhøyrande verksemd. Selskapet kan ta del i anna liknande verksemder, herunder kjøpe aksjar i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 167,000 in revenue and NOK −92,000 in operating profit.

Key figures · 2024

Revenue
NOK 167,000
Operating profit
NOK −92,000
Equity
NOK −25,000

Financial health · 2024

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

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

Who owns SOGNDAL LIVE AS?

ØYRE LYD AS
SOGNDAL LIVE AS
NOK 167,000 rev. · NOK −92,000 profit

SOGNDAL LIVE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOGNDAL LIVE AS

Who owns SOGNDAL LIVE AS?

ØYRE LYD AS is the largest registered owner, with 100.0%.

What is the revenue of SOGNDAL LIVE AS?

SOGNDAL LIVE AS had revenue of NOK 167,000 in 2024.

Where is SOGNDAL LIVE AS based?

SOGNDAL LIVE AS has its business address in Sogndal.

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.