biztrac. BETA
COMPANY REGISTER PROFILE
934987934 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

SPEEDY DAWAN AS

Org. no. 934987934 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 713,000
Equity NOK 586,000
Incorporated 2025
Share capital NOK 30,000

SPEEDY DAWAN AS is registered as a limited company in Drammen, Buskerud with organisation number 934987934. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen godstransport på vei - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 713,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 713,000
Equity
NOK 586,000
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
51.5%
Very good
Equity as a share of total capital

Who owns SPEEDY DAWAN AS?

SPEEDY DAWAN AS
NOK 2.3m rev. · NOK 713,000 profit

SPEEDY DAWAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPEEDY DAWAN AS

Who owns SPEEDY DAWAN AS?

Dawan Ababakar is the largest registered owner, with 100.0%.

What is the revenue of SPEEDY DAWAN AS?

SPEEDY DAWAN AS had revenue of NOK 2.3m in 2025.

Who is the general manager of SPEEDY DAWAN AS?

Dawan Ababakar is registered as general manager of SPEEDY DAWAN AS.

Where is SPEEDY DAWAN AS based?

SPEEDY DAWAN AS has its business address in Solbergelva.

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

Report a problem

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