BIZTRAC BETA
Other captive investment companies

JUPITER PRODUKSJON AS

Org. no. 992108088 Limited company (AS) Stavanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −44,000
Equity NOK 5.1m
Incorporated 2007
Share capital NOK 100,000

Signals

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

JUPITER PRODUKSJON AS is registered as a limited company in Stavanger, Rogaland with organisation number 992108088. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1855804 shares. The company's stated purpose is: “Investering i verdipapirer, herunder deltakelse i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −44,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −44,000
Equity
NOK 5.1m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns JUPITER PRODUKSJON AS?

OLIVER KERSBERGEN
JUPITER PRODUKSJON AS
NOK 0 rev. · NOK −44,000 profit

JUPITER PRODUKSJON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JUPITER PRODUKSJON AS own?

JUPITER PRODUKSJON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JUPITER PRODUKSJON AS

Who owns JUPITER PRODUKSJON AS?

OLIVER KERSBERGEN is the largest registered owner, with 100.0%.

What is the revenue of JUPITER PRODUKSJON AS?

JUPITER PRODUKSJON AS had revenue of NOK 0 in 2025.

Where is JUPITER PRODUKSJON AS based?

JUPITER PRODUKSJON 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.