BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

DIESELGROSSISTEN AS

Org. no. 993828629 Limited company (AS) Ringerike Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 12.6m
Operating profit NOK 1.7m
Equity NOK 363,000
Incorporated 2009
Share capital NOK 100,000

DIESELGROSSISTEN AS is registered as a limited company in Ringerike, Buskerud with organisation number 993828629. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av produkter tilknyttet bil og derav beslektet virksomhet, kurs, investeringer i verdipapirer, eie og drive fast eiendom og derav beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.6m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 12.6m
Operating profit
NOK 1.7m
Equity
NOK 363,000
Est. value
NOK 5.2m

Financial health · 2024

Liquidity
1.07
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 DIESELGROSSISTEN AS?

BJØRN ERIK JACOBSEN
DIESELGROSSISTEN AS
NOK 12.6m rev. · NOK 1.7m profit

DIESELGROSSISTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIESELGROSSISTEN AS

Who owns DIESELGROSSISTEN AS?

BJØRN ERIK JACOBSEN is the largest registered owner, with 100.0%.

What is the revenue of DIESELGROSSISTEN AS?

DIESELGROSSISTEN AS had revenue of NOK 12.6m in 2024.

Who is the general manager of DIESELGROSSISTEN AS?

Brita Dakaj Jacobsen is registered as general manager of DIESELGROSSISTEN AS.

Where is DIESELGROSSISTEN AS based?

DIESELGROSSISTEN AS has its business address in Hønefoss.

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.