BIZTRAC BETA
Other support activities to arts and performing arts

LOUD EVENT AS

Org. no. 912445909 Limited company (AS) Ringerike Incorporated 2013 Active
Ownership graph ↗
Equity NOK −12,000
Incorporated 2013
Share capital NOK 35,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−12k kr).

LOUD EVENT AS is registered as a limited company in Ringerike, Buskerud with organisation number 912445909. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2013. Registered share capital is NOK 35,000, divided into 35 shares. The company's stated purpose is: “Leverandør av event produksjoner i form av konserter, og øvrige arrangementer. Selskapet skal på egen hånd etablere og utvikle event konsepter, parallelt med at det gjøres oppdrag for tredjeparter. Videre har selskapet all design av promo og markedsmateriell internt, noe som også utføres for kunde i prosjekter hvor det er behov for dette. Som en del av dette arbeidet vil også selskapet formidle sponsoravtaler, inngås på egne og andres vegne når dette gjør seg gjeldene.”.

Key figures · 2024

Equity
NOK −12,000

Financial health · 2024

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

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

Who owns LOUD EVENT AS?

PER INGE JOHANSEN
LOUD EVENT AS

LOUD EVENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOUD EVENT AS

Who owns LOUD EVENT AS?

PER INGE JOHANSEN is the largest registered owner, with 100.0%.

Who is the general manager of LOUD EVENT AS?

Per Inge Johansen is registered as general manager of LOUD EVENT AS.

Where is LOUD EVENT AS based?

LOUD EVENT AS has its business address in Sokna.

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.