BIZTRAC BETA
Repair and maintenance of motor vehicles

DUELAND BILSERVICE AS

Org. no. 925592412 Limited company (AS) Haugesund Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 18.3m
Operating profit NOK 182,000
Equity NOK 432,000
Incorporated 2020
Employees 14
Share capital NOK 100,000

DUELAND BILSERVICE AS is registered as a limited company in Haugesund, Rogaland with organisation number 925592412. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2020 and has 14 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Vedlikehold og reparasjon av motorvogner, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.3m in revenue and NOK 182,000 in operating profit.

Key figures · 2024

Revenue
NOK 18.3m
Operating profit
NOK 182,000
Equity
NOK 432,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns DUELAND BILSERVICE AS?

GEIR TERJE DUELAND
DUELAND BILSERVICE AS
NOK 18.3m rev. · NOK 182,000 profit

DUELAND BILSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DUELAND BILSERVICE AS

Who owns DUELAND BILSERVICE AS?

GEIR TERJE DUELAND is the largest registered owner, with 100.0%.

What is the revenue of DUELAND BILSERVICE AS?

DUELAND BILSERVICE AS had revenue of NOK 18.3m in 2024.

Who is the general manager of DUELAND BILSERVICE AS?

Silje Dueland is registered as general manager of DUELAND BILSERVICE AS.

Where is DUELAND BILSERVICE AS based?

DUELAND BILSERVICE AS has its business address in Haugesund.

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.