BIZTRAC BETA
Other support activities to arts and performing arts

H3 GRUPPEN AS

Org. no. 913535588 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −117,000
Equity NOK 1.3m
Incorporated 2014
Share capital NOK 37,000

Signals

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

H3 GRUPPEN AS is registered as a limited company in Oslo, Oslo with organisation number 913535588. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2014. Registered share capital is NOK 37,000, divided into 10200 shares. The company's stated purpose is: “Å eie selskaper innen underholdning, show-produksjon, impressario virksomhet, tv-produksjon, teaterdrift og annen beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −117,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −117,000
Equity
NOK 1.3m
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.6%
Very good
Equity as a share of total capital

Who owns H3 GRUPPEN AS?

HANS-CHRISTOPH MAJOR-WERNERSEN
H3 GRUPPEN AS
NOK 0 rev. · NOK −117,000 profit

H3 GRUPPEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does H3 GRUPPEN AS own?

H3 GRUPPEN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about H3 GRUPPEN AS

Who owns H3 GRUPPEN AS?

HANS-CHRISTOPH MAJOR-WERNERSEN is the largest registered owner, with 100.0%.

What is the revenue of H3 GRUPPEN AS?

H3 GRUPPEN AS had revenue of NOK 0 in 2024.

Where is H3 GRUPPEN AS based?

H3 GRUPPEN 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.