BIZTRAC BETA
Manufacture of glass fibres

SPILKA COMPOSITES AS

Org. no. 971207361 Limited company (AS) Ålesund Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 68.0m
Operating profit NOK 6.0m
Equity NOK 15.5m
Incorporated 1994
Employees 29
Share capital NOK 4.8m

SPILKA COMPOSITES AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 971207361. The business is classified under manufacture of glass fibres (NACE 23.140). The company was incorporated in 1994 and has 29 registered employees. Registered share capital is NOK 4.8m, divided into 24000 shares. The company's stated purpose is: “Produksjon, markedsføring og salg av kompositt- produkter. Selskapet kan engasjere seg i andre selskap med beslektet formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 68.0m in revenue and NOK 6.0m in operating profit.

Key figures · 2024

Revenue
NOK 68.0m
Operating profit
NOK 6.0m
Equity
NOK 15.5m
Est. value
NOK 31.5m

Financial health · 2024

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

Who owns SPILKA COMPOSITES AS?

SPILCOM AS
SPILKA COMPOSITES AS
NOK 68.0m rev. · NOK 6.0m profit

SPILKA COMPOSITES AS has 2 registered shareholders:

All shareholders and roles →

Group structure

SPILKA COMPOSITES AS er morselskap for 2 datterselskaper:

Frequently asked questions about SPILKA COMPOSITES AS

Who owns SPILKA COMPOSITES AS?

SPILCOM AS is the largest registered owner, with 90.1%.

What is the revenue of SPILKA COMPOSITES AS?

SPILKA COMPOSITES AS had revenue of NOK 68.0m in 2024.

Who is the general manager of SPILKA COMPOSITES AS?

Kåre Dybvik is registered as general manager of SPILKA COMPOSITES AS.

Where is SPILKA COMPOSITES AS based?

SPILKA COMPOSITES AS has its business address in Skodje.

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.