BIZTRAC BETA
Manufacture of jewellery and related articles

SØLV & GULLSMIA AS

Org. no. 971235705 Limited company (AS) Stjørdal Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 144,000
Operating profit NOK −33,000
Equity NOK 300,000
Incorporated 1994
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−33k kr).

SØLV & GULLSMIA AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 971235705. The business is classified under manufacture of jewellery and related articles (NACE 32.120). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Gullsmedverksted, handel og det som naturlig tilhører slik virksomhet, samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 144,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 144,000
Operating profit
NOK −33,000
Equity
NOK 300,000
Est. value
NOK 214,000

Financial health · 2025

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

Who owns SØLV & GULLSMIA AS?

TROND OVERVIK
SØLV & GULLSMIA AS
NOK 144,000 rev. · NOK −33,000 profit

SØLV & GULLSMIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØLV & GULLSMIA AS

Who owns SØLV & GULLSMIA AS?

TROND OVERVIK is the largest registered owner, with 100.0%.

What is the revenue of SØLV & GULLSMIA AS?

SØLV & GULLSMIA AS had revenue of NOK 144,000 in 2025.

Who is the general manager of SØLV & GULLSMIA AS?

Trond Overvik is registered as general manager of SØLV & GULLSMIA AS.

Where is SØLV & GULLSMIA AS based?

SØLV & GULLSMIA AS has its business address in Stjørdal.

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.