biztrac. BETA
COMPANY REGISTER PROFILE
965407553 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of watches and jewellery

GULLSMED WESTBY AS

Org. no. 965407553 Limited company (AS) Østre Toten Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 285,000
Equity NOK 402,000
Incorporated 1992
Share capital NOK 310,000

GULLSMED WESTBY AS is registered as a limited company in Østre Toten, Innlandet with organisation number 965407553. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1992. Registered share capital is NOK 310,000, divided into 310 shares. The company's stated purpose is: “Gullsmedforretning og handel, samt annen virksomhet forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 285,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
▲ +18 %
Operating profit
NOK 285,000
▲ +875 %
Equity
NOK 402,000
▲ +263 %
Est. value
NOK 921,000

Financial health · 2025

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
19.3%
Very good
Return on total assets
Solidity
23.3%
Good
Equity as a share of total capital

Who owns GULLSMED WESTBY AS?

GULLSMED WESTBY AS
NOK 2.8m rev. · NOK 285,000 profit

GULLSMED WESTBY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLSMED WESTBY AS

Who owns GULLSMED WESTBY AS?

LILLE GULLKORN GULLSMED AS is the largest registered owner, with 100.0%.

What is the revenue of GULLSMED WESTBY AS?

GULLSMED WESTBY AS had revenue of NOK 2.8m in 2025.

Who is the general manager of GULLSMED WESTBY AS?

Tone Furuseth Kristiansen is registered as general manager of GULLSMED WESTBY AS.

Where is GULLSMED WESTBY AS based?

GULLSMED WESTBY AS has its business address in Lena.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.