BIZTRAC BETA
Legal activities

ADVOKAT TOM HERMANSEN AS

Org. no. 978684432 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 144,000
Operating profit NOK −106,000
Equity NOK 336,000
Incorporated 1997
Share capital NOK 100,000

Signals

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

ADVOKAT TOM HERMANSEN AS is registered as a limited company in Oslo, Oslo with organisation number 978684432. The business is classified under legal activities (NACE 69.100). The company was incorporated in 1997. Registered share capital is NOK 100,000. The company's stated purpose is: “Advokatvirksomhet for derved å fremme rett og hindre urett.”. The most recent filed accounts, for the 2025 financial year, show NOK 144,000 in revenue and NOK −106,000 in operating profit.

Key figures · 2025

Revenue
NOK 144,000
Operating profit
NOK −106,000
Equity
NOK 336,000
Est. value
NOK 315,000

Financial health · 2025

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

Who owns ADVOKAT TOM HERMANSEN AS?

TOM ALEXANDER BERGMANN HERMANSEN
ADVOKAT TOM HERMANSEN AS
NOK 144,000 rev. · NOK −106,000 profit

ADVOKAT TOM HERMANSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKAT TOM HERMANSEN AS

Who owns ADVOKAT TOM HERMANSEN AS?

TOM ALEXANDER BERGMANN HERMANSEN is the largest registered owner, with 100.0%.

What is the revenue of ADVOKAT TOM HERMANSEN AS?

ADVOKAT TOM HERMANSEN AS had revenue of NOK 144,000 in 2025.

Who is the general manager of ADVOKAT TOM HERMANSEN AS?

Tom Alexander Bergmann Hermansen is registered as general manager of ADVOKAT TOM HERMANSEN AS.

Where is ADVOKAT TOM HERMANSEN AS based?

ADVOKAT TOM HERMANSEN 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 15.06.2026.

Report a problem

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