BIZTRAC BETA
COMPANY REGISTER PROFILE
922352836 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

JOPPE HOLDING AS

Org. no. 922352836 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 447,000
Operating profit NOK 332,000
Equity NOK 70.1m
Incorporated 2019
Share capital NOK 40,000

JOPPE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 922352836. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap med konsulentvirksomhet, investeringer, event, restaurant og uteliv.”. The most recent filed accounts, for the 2025 financial year, show NOK 447,000 in revenue and NOK 332,000 in operating profit.

Key figures · 2025

Revenue
NOK 447,000
▲ +1134 %
Operating profit
NOK 332,000
▲ +172 %
Equity
NOK 70.1m
▲ +388 %
Est. value
NOK 35.5m

Financial health · 2025

Liquidity
2.19
Very good
Current assets ÷ current liabilities
Profitability
89.0%
Very good
Return on total assets
Solidity
99.0%
Very good
Equity as a share of total capital

Who owns JOPPE HOLDING AS?

JOPPE HOLDING AS
NOK 447,000 rev. · NOK 332,000 profit

JOPPE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JOPPE HOLDING AS own?

JOPPE HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about JOPPE HOLDING AS

Who owns JOPPE HOLDING AS?

FRIDTJOF HAVIG-GJELSETH is the largest registered owner, with 100.0%.

What is the revenue of JOPPE HOLDING AS?

JOPPE HOLDING AS had revenue of NOK 447,000 in 2025.

Where is JOPPE HOLDING AS based?

JOPPE 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.