BIZTRAC BETA
Manufacture of wire products, chain and springs

SIKTEDUKFABRIKKEN AS

Org. no. 938026998 Limited company (AS) Namsos Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 83.6m
Operating profit NOK 9.9m
Equity NOK 45.7m
Incorporated 1986
Employees 39
Share capital NOK 600,000

SIKTEDUKFABRIKKEN AS is registered as a limited company in Namsos, Trøndelag with organisation number 938026998. The business is classified under manufacture of wire products, chain and springs (NACE 25.930). The company was incorporated in 1986 and has 39 registered employees. Registered share capital is NOK 600,000, divided into 300 shares. The company's stated purpose is: “Produksjon og salg av sikteduk til knuseverket, samt salg av maskiner og produkter som har tilknytning til knuseverket. ”. The most recent filed accounts, for the 2024 financial year, show NOK 83.6m in revenue and NOK 9.9m in operating profit.

Key figures · 2024

Revenue
NOK 83.6m
Operating profit
NOK 9.9m
Equity
NOK 45.7m
Est. value
NOK 60.6m

Financial health · 2024

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

Who owns SIKTEDUKFABRIKKEN AS?

STOCKHOLM PLÅT & GUNNIPERFO.
SIKTEDUKFABRIKKEN AS
NOK 83.6m rev. · NOK 9.9m profit

SIKTEDUKFABRIKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIKTEDUKFABRIKKEN AS

Who owns SIKTEDUKFABRIKKEN AS?

STOCKHOLM PLÅT & GUNNIPERFO. is the largest registered owner, with 100.0%.

What is the revenue of SIKTEDUKFABRIKKEN AS?

SIKTEDUKFABRIKKEN AS had revenue of NOK 83.6m in 2024.

Who is the general manager of SIKTEDUKFABRIKKEN AS?

Edvart Østby is registered as general manager of SIKTEDUKFABRIKKEN AS.

Where is SIKTEDUKFABRIKKEN AS based?

SIKTEDUKFABRIKKEN AS has its business address in Spillum.

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.