BIZTRAC BETA
COMPANY REGISTER PROFILE
922717710 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

HASSUM HOLDING AS

Org. no. 922717710 Limited company (AS) Tønsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −20,000
Equity NOK 6.8m
Incorporated 2019
Share capital NOK 30,000

Signals

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

HASSUM HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 922717710. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 250 shares. The company's stated purpose is: “Investering i aksjer, verdipapirer og eiendommer og hva som dermed står i naturlig forbindelse med dette, herunder også deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 6.8m
Est. value
NOK 17.8m

Financial health · 2025

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

Who owns HASSUM HOLDING AS?

HASSUM HOLDING AS
NOK 0 rev. · NOK −20,000 profit

HASSUM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HASSUM HOLDING AS

Who owns HASSUM HOLDING AS?

ØYVIND HASSUM is the largest registered owner, with 100.0%.

What is the revenue of HASSUM HOLDING AS?

HASSUM HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of HASSUM HOLDING AS?

Øyvind Hassum is registered as general manager of HASSUM HOLDING AS.

Where is HASSUM HOLDING AS based?

HASSUM HOLDING AS has its business address in Tønsberg.

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

Report a problem

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