BIZTRAC BETA
COMPANY REGISTER PROFILE
919856599 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Performing arts activities in music

TUSH PARTYROCK AS

Org. no. 919856599 Limited company (AS) Sandefjord Incorporated 2017 Active
Ownership graph ↗
Equity NOK 46,000
Incorporated 2017
Share capital NOK 30,000

TUSH PARTYROCK AS is registered as a limited company in Sandefjord, Vestfold with organisation number 919856599. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 120 shares. The company's stated purpose is: “Musikkfremføring og andre produkter/tjenester som naturlig faller innenfor dette.”.

Key figures · 2025

Equity
NOK 46,000
Est. value
NOK 58,000

Financial health · 2025

Liquidity
50.74
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.6%
Weak
Equity as a share of total capital

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

Who owns TUSH PARTYROCK AS?

TUSH PARTYROCK AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about TUSH PARTYROCK AS

Who owns TUSH PARTYROCK AS?

EGIL HÅGENSEN is the largest registered owner, with 16.7%.

Who is the general manager of TUSH PARTYROCK AS?

Egil Hågensen is registered as general manager of TUSH PARTYROCK AS.

Where is TUSH PARTYROCK AS based?

TUSH PARTYROCK AS has its business address in Kodal.

Property

Business address Sagbakken 2B, 3243 Kodal
Cadastral unit 3907-307/34/2/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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