biztrac. BETA
COMPANY REGISTER PROFILE
914086159 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in music

SIXPACK SA

Org. no. 914086159 Co-operation (SA) Stavanger Incorporated 2014 Active
Revenue 2025 NOK 160,000
Operating profit NOK −1,000
Equity NOK 7,000
Incorporated 2014

Signals

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

SIXPACK SA is registered as a co-operation in Stavanger, Rogaland with organisation number 914086159. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2014. The company's stated purpose is: “Bandvirksomhet herunder framføring av musikk og annet som hører naturlig til. Foretaket har til formål å fremme medlemmenes økonomiske interesser gjennom deres deltakelse i virksomheten som leverandør av tjenester til foretaket.”. The most recent filed accounts, for the 2025 financial year, show NOK 160,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 160,000
▼ −23 %
Operating profit
NOK −1,000
▲ +71 %
Equity
NOK 7,000
▲ +56 %
Est. value
NOK 166,000

Financial health · 2025

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
10.0%
Weak
Equity as a share of total capital

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

Who owns SIXPACK SA?

No shareholders are registered for SIXPACK SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SIXPACK SA

What is the revenue of SIXPACK SA?

SIXPACK SA had revenue of NOK 160,000 in 2025.

Who is the general manager of SIXPACK SA?

Helge Thoresen is registered as general manager of SIXPACK SA.

Where is SIXPACK SA based?

SIXPACK SA has its business address in Hafrsfjord.

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.