BIZTRAC BETA
Activities of advertising agencies

WE ARE LIVE HOLDING AS

Org. no. 812079042 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −322,000
Equity NOK 12.6m
Incorporated 2013
Share capital NOK 160,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−322k kr).

WE ARE LIVE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 812079042. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2013. Registered share capital is NOK 160,000, divided into 160000 shares. The company's stated purpose is: “Arrangør- og konsulentvirksomhet innenfor områdene PR, reklame, markedsføring og events, samt produsere varer og tjenester innefor disse områdene, herunder deltagelse i andre virksomheter, samt investeringsvirksomhet.”.

Key figures · 2024

Operating profit
NOK −322,000
Equity
NOK 12.6m
Est. value
NOK 107.4m

Financial health · 2024

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

Who owns WE ARE LIVE HOLDING AS?

GJEINE HOLDING AS
WE ARE LIVE HOLDING AS
· NOK −322,000 profit

WE ARE LIVE HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does WE ARE LIVE HOLDING AS own?

WE ARE LIVE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WE ARE LIVE HOLDING AS

Who owns WE ARE LIVE HOLDING AS?

GJEINE HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of WE ARE LIVE HOLDING AS?

Øystein Lasse Tynning is registered as general manager of WE ARE LIVE HOLDING AS.

Where is WE ARE LIVE HOLDING AS based?

WE ARE LIVE HOLDING AS has its business address in Oslo.

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.