BIZTRAC BETA
COMPANY REGISTER PROFILE
929571177 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 02.09.2026
NITRO HOLDING AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Sound recording and music publishing activities

NITRO HOLDING AS

Org. no. 929571177 Limited company (AS) Oslo Incorporated 2022 In liquidation
Ownership graph ↗
Operating profit NOK −480
Equity NOK 10,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−480 kr).

NITRO HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 929571177. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, selskaper, selskapsandeler og fast eiendom samt alt som står i forbindelse med dette.”.

Former names: NFH 220708 AS

Key figures · 2025

Operating profit
NOK −480
Equity
NOK 10,000

Financial health · 2025

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

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

Who owns NITRO HOLDING AS?

NITRO HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NITRO HOLDING AS own?

NITRO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NITRO HOLDING AS

Who owns NITRO HOLDING AS?

BAMERI HOLDING AS is the largest registered owner, with 50.0%.

Where is NITRO HOLDING AS based?

NITRO HOLDING 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 02.09.2026.

Report a problem

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