BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

DEKKSPESIALISTEN SKIEN AS

Org. no. 984719639 Limited company (AS) Skien Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 9.2m
Operating profit NOK −165,000
Equity NOK 1.7m
Incorporated 2002
Employees 11
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−165k kr).

DEKKSPESIALISTEN SKIEN AS is registered as a limited company in Skien, Telemark with organisation number 984719639. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2002 and has 11 registered employees. Registered share capital is NOK 400,000, divided into 4000 shares. The company's stated purpose is: “Yte tjeneste innen salg av dekk, felger og andre tilknyttede produkter, samt deltagelse i selskaper med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.2m in revenue and NOK −165,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.2m
Operating profit
NOK −165,000
Equity
NOK 1.7m
Est. value
NOK 3.8m

Financial health · 2024

Liquidity
1.50
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.1%
Good
Equity as a share of total capital

Who owns DEKKSPESIALISTEN SKIEN AS?

SMH HOLDING AS
DEKKSPESIALISTEN SKIEN AS
NOK 9.2m rev. · NOK −165,000 profit

DEKKSPESIALISTEN SKIEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DEKKSPESIALISTEN SKIEN AS

Who owns DEKKSPESIALISTEN SKIEN AS?

SMH HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of DEKKSPESIALISTEN SKIEN AS?

DEKKSPESIALISTEN SKIEN AS had revenue of NOK 9.2m in 2024.

Where is DEKKSPESIALISTEN SKIEN AS based?

DEKKSPESIALISTEN SKIEN AS has its business address in Skien.

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.