BIZTRAC BETA
COMPANY REGISTER PROFILE
926204238 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Legal activities

ADVOKAT MORTEN HASSUM

Org. no. 926204238 Sole proprietorship (ENK) Tønsberg Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.5m
Equity NOK 540,000

ADVOKAT MORTEN HASSUM is registered as a sole proprietorship in Tønsberg, Vestfold with organisation number 926204238. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.5m
Equity
NOK 540,000
Est. value
NOK 5.3m

Financial health · 2025

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

Who owns ADVOKAT MORTEN HASSUM?

No shareholders are registered for ADVOKAT MORTEN HASSUM in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ADVOKAT MORTEN HASSUM

What is the revenue of ADVOKAT MORTEN HASSUM?

ADVOKAT MORTEN HASSUM had revenue of NOK 1.9m in 2025.

Who is the general manager of ADVOKAT MORTEN HASSUM?

Morten Hassum is registered as general manager of ADVOKAT MORTEN HASSUM.

Where is ADVOKAT MORTEN HASSUM based?

ADVOKAT MORTEN HASSUM has its business address in Tønsberg.

Property

Business address Storgaten 41A, 3126 Tønsberg
Cadastral unit 3905-1002/158/0/0
Building Butikkbygning · 3 units

9 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.