BIZTRAC BETA
Activities of excursion and event organisers

OS LIVE AS

Org. no. 917855587 Limited company (AS) Bjørnafjorden Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2,000
Operating profit NOK 10,000
Equity NOK −1.2m
Incorporated 2016
Share capital NOK 75,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,2 mill kr).

OS LIVE AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 917855587. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2016. Registered share capital is NOK 75,000, divided into 75000 shares. The company's stated purpose is: “Arrangere musikkfestivaler og konserter, og andre produkter/tjenester som naturlig hører sammen med dette , herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2024

Revenue
NOK 2,000
Operating profit
NOK 10,000
Equity
NOK −1.2m
Est. value
NOK 44,000

Financial health · 2024

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

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

Who owns OS LIVE AS?

HYLLAND INVEST AS
OS LIVE AS
NOK 2,000 rev. · NOK 10,000 profit

OS LIVE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about OS LIVE AS

Who owns OS LIVE AS?

HYLLAND INVEST AS is the largest registered owner, with 70.0%.

What is the revenue of OS LIVE AS?

OS LIVE AS had revenue of NOK 2,000 in 2024.

Where is OS LIVE AS based?

OS LIVE AS has its business address in Os.

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.