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

ADVOKAT BJØRN SOLHEIM

Org. no. 914042135 Sole proprietorship (ENK) Drammen Active
Ownership graph ↗
Revenue 2025 NOK 206,000
Operating profit NOK −214
Equity NOK 126,000

Signals

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

ADVOKAT BJØRN SOLHEIM is registered as a sole proprietorship in Drammen, Buskerud with organisation number 914042135. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2025 financial year, show NOK 206,000 in revenue and NOK −214 in operating profit.

Former names: RÅDGIVER BJØRN SOLHEIM

Key figures · 2025

Revenue
NOK 206,000
Operating profit
NOK −214
Equity
NOK 126,000
Est. value
NOK 278,000

Financial health · 2025

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

Who owns ADVOKAT BJØRN SOLHEIM?

No shareholders are registered for ADVOKAT BJØRN SOLHEIM in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ADVOKAT BJØRN SOLHEIM

What is the revenue of ADVOKAT BJØRN SOLHEIM?

ADVOKAT BJØRN SOLHEIM had revenue of NOK 206,000 in 2025.

Where is ADVOKAT BJØRN SOLHEIM based?

ADVOKAT BJØRN SOLHEIM has its business address in Drammen.

Property

Business address Havreveien 10, 3039 Drammen
Cadastral unit 3301-41/132/0/0
Building Enebolig · 1 unit

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