biztrac. BETA
COMPANY REGISTER PROFILE
832008672 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠JOVIAL AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other support activities to arts and performing arts

JOVIAL AS

Org. no. 832008672 Limited company (AS) Stavanger Incorporated 2023 In liquidation
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −75,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−75k kr).

JOVIAL AS is registered as a limited company in Stavanger, Rogaland with organisation number 832008672. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Er å arrangere utdrikningslag og sosiale sammenkomster i inn- og utland. Drift av nettbutikk med salg av festutstyr samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK 0
▲ +100 %
Equity
NOK −75,000
▲ +0 %

Financial health · 2025

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

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

Who owns JOVIAL AS?

JOVIAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JOVIAL AS

Who owns JOVIAL AS?

IUSSISTI INVEST AS is the largest registered owner, with 66.7%.

What is the revenue of JOVIAL AS?

JOVIAL AS had revenue of NOK 0 in 2025.

Where is JOVIAL AS based?

JOVIAL AS has its business address in Hafrsfjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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