BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

DEKKBUTIKKEN AS

Org. no. 990337934 Limited company (AS) Stavanger Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 8.8m
Operating profit NOK 600,000
Equity NOK 3.2m
Incorporated 2006
Employees 11
Share capital NOK 50,000

DEKKBUTIKKEN AS is registered as a limited company in Stavanger, Rogaland with organisation number 990337934. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2006 and has 11 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Salg og montering av dekk og felg til motorkjøretøy. Generell handelsvirksomhet innen området motorkjøretøy. Import av deler til motorkjøretøy. Utleie av motorkjøretøy/båt.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.8m in revenue and NOK 600,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.8m
Operating profit
NOK 600,000
Equity
NOK 3.2m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns DEKKBUTIKKEN AS?

ÅRESKJOLD INVEST AS
DEKKBUTIKKEN AS
NOK 8.8m rev. · NOK 600,000 profit

DEKKBUTIKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DEKKBUTIKKEN AS

Who owns DEKKBUTIKKEN AS?

ÅRESKJOLD INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of DEKKBUTIKKEN AS?

DEKKBUTIKKEN AS had revenue of NOK 8.8m in 2025.

Who is the general manager of DEKKBUTIKKEN AS?

Andrea Eritsland Olsen is registered as general manager of DEKKBUTIKKEN AS.

Where is DEKKBUTIKKEN AS based?

DEKKBUTIKKEN AS has its business address in Stavanger.

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.