BIZTRAC BETA
Performing arts activities in music

G FOSSER HOLDING AS

Org. no. 928429067 Limited company (AS) Indre Østfold Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK 0
Incorporated 2021
Share capital NOK 30,000

Signals

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

G FOSSER HOLDING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 928429067. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eierskap i elektrofirma, musikk/konsertvirksomhet, kjøp og salg av andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 0

Financial health · 2024

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

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

Who owns G FOSSER HOLDING AS?

GLENN JOSTEIN FOSSER
G FOSSER HOLDING AS
NOK 0 rev. · NOK −5,000 profit

G FOSSER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does G FOSSER HOLDING AS own?

G FOSSER HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about G FOSSER HOLDING AS

Who owns G FOSSER HOLDING AS?

GLENN JOSTEIN FOSSER is the largest registered owner, with 100.0%.

What is the revenue of G FOSSER HOLDING AS?

G FOSSER HOLDING AS had revenue of NOK 0 in 2024.

Where is G FOSSER HOLDING AS based?

G FOSSER HOLDING AS has its business address in Mysen.

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.