biztrac. BETA
COMPANY REGISTER PROFILE
911718383 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of adventure companies

PANG EVENT AS

Org. no. 911718383 Limited company (AS) Ullensaker Incorporated 2013 Active
Revenue 2025 NOK 3.9m
Operating profit NOK −206,000
Equity NOK −88,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

PANG EVENT AS is registered as a limited company in Ullensaker, Akershus with organisation number 911718383. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel, impressario, konsulent, kurs, seminar, kulturformidling, arrangementsgjennomføring, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK −206,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
▼ −13 %
Operating profit
NOK −206,000
▼ −148 %
Equity
NOK −88,000
▼ −145 %
Est. value
NOK 412,000

Financial health · 2025

Liquidity
1.75
Good
Current assets ÷ current liabilities
Profitability
-18.1%
Not satisfactory
Return on total assets
Solidity
-9.2%
Weak
Equity as a share of total capital

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

Who owns PANG EVENT AS?

PANG EVENT AS
NOK 3.9m rev. · NOK −206,000 profit

PANG EVENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PANG EVENT AS

Who owns PANG EVENT AS?

Charlie Kai Anders Rønneseth is the largest registered owner, with 100.0%.

What is the revenue of PANG EVENT AS?

PANG EVENT AS had revenue of NOK 3.9m in 2025.

Where is PANG EVENT AS based?

PANG EVENT AS has its business address in Jessheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.