BIZTRAC BETA
Organisation of conventions and trade shows

BLACK PHENIX AS

Org. no. 917992851 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 30,000
Incorporated 2016
Share capital NOK 40,000

Signals

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

BLACK PHENIX AS is registered as a limited company in Stavanger, Rogaland with organisation number 917992851. The business is classified under organisation of conventions and trade shows (NACE 82.300). The company was incorporated in 2016. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Kongress-, messe- og utstillingsvirksomhet, og annet som naturlig faller sammen med dette, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 30,000
Est. value
NOK 43,000

Financial health · 2025

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

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

Who owns BLACK PHENIX AS?

GYTE AS
BLACK PHENIX AS
NOK 0 rev. · NOK −14,000 profit

BLACK PHENIX AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLACK PHENIX AS

Who owns BLACK PHENIX AS?

GYTE AS is the largest registered owner, with 40.4%.

What is the revenue of BLACK PHENIX AS?

BLACK PHENIX AS had revenue of NOK 0 in 2025.

Who is the general manager of BLACK PHENIX AS?

Bjørn Olaf Helgøy is registered as general manager of BLACK PHENIX AS.

Where is BLACK PHENIX AS based?

BLACK PHENIX AS has its business address in Stavanger.

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.