BIZTRAC BETA
Retail sale of watches and jewellery

GULLSMED DAHLSVEEN AS

Org. no. 967412023 Limited company (AS) Trondheim Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 12.5m
Operating profit NOK 1.0m
Equity NOK 7.0m
Incorporated 1993
Employees 8
Share capital NOK 330,000

GULLSMED DAHLSVEEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 967412023. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1993 and has 8 registered employees. Registered share capital is NOK 330,000, divided into 300 shares. The company's stated purpose is: “Drive gullsmedbutikk, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.5m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 12.5m
Operating profit
NOK 1.0m
Equity
NOK 7.0m
Est. value
NOK 7.3m

Financial health · 2024

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

Who owns GULLSMED DAHLSVEEN AS?

MESTERGULL INVEST AS
GULLSMED DAHLSVEEN AS
NOK 12.5m rev. · NOK 1.0m profit

GULLSMED DAHLSVEEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLSMED DAHLSVEEN AS

Who owns GULLSMED DAHLSVEEN AS?

MESTERGULL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GULLSMED DAHLSVEEN AS?

GULLSMED DAHLSVEEN AS had revenue of NOK 12.5m in 2024.

Who is the general manager of GULLSMED DAHLSVEEN AS?

Jeanette Holmen Strømmen is registered as general manager of GULLSMED DAHLSVEEN AS.

Where is GULLSMED DAHLSVEEN AS based?

GULLSMED DAHLSVEEN AS has its business address in Trondheim.

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.