BIZTRAC BETA
Manufacture of jewellery and related articles

SYLVSMIDJA AS

Org. no. 914302307 Limited company (AS) Voss Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 113.4m
Operating profit NOK 7.9m
Equity NOK 47.6m
Incorporated 2014
Employees 71
Share capital NOK 1.0m

SYLVSMIDJA AS is registered as a limited company in Voss, Vestland with organisation number 914302307. The business is classified under manufacture of jewellery and related articles (NACE 32.120). The company was incorporated in 2014 and has 71 registered employees. Registered share capital is NOK 1.0m, divided into 596 shares. The company's stated purpose is: “Produksjon, handel, agenturvirksomhet, samt ved aksjetegning eller på annen måte delta i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 113.4m in revenue and NOK 7.9m in operating profit.

Key figures · 2024

Revenue
NOK 113.4m
Operating profit
NOK 7.9m
Equity
NOK 47.6m
Est. value
NOK 58.1m

Financial health · 2024

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

Who owns SYLVSMIDJA AS?

VOSSASKRINET AS
SYLVSMIDJA AS
NOK 113.4m rev. · NOK 7.9m profit

SYLVSMIDJA AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SYLVSMIDJA AS own?

SYLVSMIDJA AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SYLVSMIDJA AS

Who owns SYLVSMIDJA AS?

VOSSASKRINET AS is the largest registered owner, with 50.0%.

What is the revenue of SYLVSMIDJA AS?

SYLVSMIDJA AS had revenue of NOK 113.4m in 2024.

Who is the general manager of SYLVSMIDJA AS?

Trond Syversen is registered as general manager of SYLVSMIDJA AS.

Where is SYLVSMIDJA AS based?

SYLVSMIDJA AS has its business address in Voss.

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.