BIZTRAC BETA
Uoppgitt

DUSPARE AS

Org. no. 919656808 Limited company (AS) Melhus Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 309,000
Operating profit NOK 178,000
Equity NOK 3.0m
Incorporated 2017
Share capital NOK 30,000

DUSPARE AS is registered as a limited company in Melhus, Trøndelag with organisation number 919656808. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet innenfor aksjer og andeler i andre selskaper, samt det som naturlig står i forbindelse med dette. Selskapet har i tillegg som formål å drive handel med motorkjøretøyer, samt deler og rekvisita til motorkjøretøy.”. The most recent filed accounts, for the 2024 financial year, show NOK 309,000 in revenue and NOK 178,000 in operating profit.

Key figures · 2024

Revenue
NOK 309,000
Operating profit
NOK 178,000
Equity
NOK 3.0m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns DUSPARE AS?

BØRGE GULSTAD RØDLI
DUSPARE AS
NOK 309,000 rev. · NOK 178,000 profit

DUSPARE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DUSPARE AS own?

DUSPARE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DUSPARE AS

Who owns DUSPARE AS?

BØRGE GULSTAD RØDLI is the largest registered owner, with 100.0%.

What is the revenue of DUSPARE AS?

DUSPARE AS had revenue of NOK 309,000 in 2024.

Who is the general manager of DUSPARE AS?

Børge Gulstad Rødli is registered as general manager of DUSPARE AS.

Where is DUSPARE AS based?

DUSPARE AS has its business address in Ler.

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.