BIZTRAC BETA
Retail sale of watches and jewellery

GULLSMED RØNNING AS

Org. no. 989952994 Limited company (AS) Larvik Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 746,000
Equity NOK 8.6m
Incorporated 2006
Employees 8
Share capital NOK 100,000

GULLSMED RØNNING AS is registered as a limited company in Larvik, Vestfold with organisation number 989952994. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2006 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Varehandel, herunder kjøp og salg av gullvarer og klokker. Produksjon og reparasjon av nevnte varer, samt alt som herved står i forbindelse. Deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 746,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 746,000
Equity
NOK 8.6m
Est. value
NOK 6.9m

Financial health · 2024

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

Who owns GULLSMED RØNNING AS?

TONNY HARALD RØNNING
GULLSMED RØNNING AS
NOK 9.5m rev. · NOK 746,000 profit

GULLSMED RØNNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLSMED RØNNING AS

Who owns GULLSMED RØNNING AS?

TONNY HARALD RØNNING is the largest registered owner, with 100.0%.

What is the revenue of GULLSMED RØNNING AS?

GULLSMED RØNNING AS had revenue of NOK 9.5m in 2024.

Who is the general manager of GULLSMED RØNNING AS?

Tonny Harald Rønning is registered as general manager of GULLSMED RØNNING AS.

Where is GULLSMED RØNNING AS based?

GULLSMED RØNNING AS has its business address in Larvik.

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.