BIZTRAC BETA
Legal activities

ADVOKATFIRMAET DUESUND AS

Org. no. 914801141 Limited company (AS) Drammen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK −33,000
Equity NOK 385,000
Incorporated 2015
Employees 5
Share capital NOK 30,000

Signals

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

ADVOKATFIRMAET DUESUND AS is registered as a limited company in Drammen, Buskerud with organisation number 914801141. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2015 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Juridisk tjenesteyting.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK −33,000
Equity
NOK 385,000
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.2%
Good
Equity as a share of total capital

Who owns ADVOKATFIRMAET DUESUND AS?

SVEIN OLAV DUESUND
ADVOKATFIRMAET DUESUND AS
NOK 4.2m rev. · NOK −33,000 profit

ADVOKATFIRMAET DUESUND AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATFIRMAET DUESUND AS

Who owns ADVOKATFIRMAET DUESUND AS?

SVEIN OLAV DUESUND is the largest registered owner, with 50.0%.

What is the revenue of ADVOKATFIRMAET DUESUND AS?

ADVOKATFIRMAET DUESUND AS had revenue of NOK 4.2m in 2025.

Who is the general manager of ADVOKATFIRMAET DUESUND AS?

Aisha Ahmed is registered as general manager of ADVOKATFIRMAET DUESUND AS.

Where is ADVOKATFIRMAET DUESUND AS based?

ADVOKATFIRMAET DUESUND AS has its business address in Drammen.

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.