BIZTRAC BETA
Uoppgitt

JUBEL BOOST AS

Org. no. 932855747 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

JUBEL BOOST AS is registered as a limited company in Oslo, Oslo with organisation number 932855747. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2024

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

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

Who owns JUBEL BOOST AS?

MINATO AS
JUBEL BOOST AS
NOK 0 rev. · NOK −7,000 profit

JUBEL BOOST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does JUBEL BOOST AS own?

JUBEL BOOST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JUBEL BOOST AS

Who owns JUBEL BOOST AS?

MINATO AS is the largest registered owner, with 33.3%.

What is the revenue of JUBEL BOOST AS?

JUBEL BOOST AS had revenue of NOK 0 in 2024.

Where is JUBEL BOOST AS based?

JUBEL BOOST 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.