BIZTRAC BETA
Construction of roads and motorways

SPESIALDEKKER AS

Org. no. 992269359 Limited company (AS) Nittedal Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 37.6m
Operating profit NOK −1.7m
Equity NOK 566,000
Incorporated 2008
Employees 13
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

SPESIALDEKKER AS is registered as a limited company in Nittedal, Akershus with organisation number 992269359. The business is classified under construction of roads and motorways (NACE 42.110). The company was incorporated in 2008 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Anleggsvirksomhet innen asfalt, membraner, broer, parkeringshus og lignende virksomhetsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 37.6m in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 37.6m
Operating profit
NOK −1.7m
Equity
NOK 566,000
Est. value
NOK 13.3m

Financial health · 2024

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

Who owns SPESIALDEKKER AS?

DAB DOMIFLEX AB
SPESIALDEKKER AS
NOK 37.6m rev. · NOK −1.7m profit

SPESIALDEKKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPESIALDEKKER AS

Who owns SPESIALDEKKER AS?

DAB DOMIFLEX AB is the largest registered owner, with 100.0%.

What is the revenue of SPESIALDEKKER AS?

SPESIALDEKKER AS had revenue of NOK 37.6m in 2024.

Who is the general manager of SPESIALDEKKER AS?

Kim Patrik Gøransson is registered as general manager of SPESIALDEKKER AS.

Where is SPESIALDEKKER AS based?

SPESIALDEKKER AS has its business address in Slattum.

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.