BIZTRAC BETA
Retail sale of watches and jewellery

Gullsmed Harry Ulsteen AS

Org. no. 917002347 Limited company (AS) Drammen Incorporated 1981 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 704,000
Equity NOK 5.6m
Incorporated 1981
Share capital NOK 100,000

Gullsmed Harry Ulsteen AS is registered as a limited company in Drammen, Buskerud with organisation number 917002347. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1981. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handel. Selskapet kan eie aksjer eller interesser i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 704,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 704,000
Equity
NOK 5.6m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns Gullsmed Harry Ulsteen AS?

NILS PETTER ULSTEEN HETTY
Gullsmed Harry Ulsteen AS
NOK 5.3m rev. · NOK 704,000 profit

Gullsmed Harry Ulsteen AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Gullsmed Harry Ulsteen AS

Who owns Gullsmed Harry Ulsteen AS?

NILS PETTER ULSTEEN HETTY is the largest registered owner, with 100.0%.

What is the revenue of Gullsmed Harry Ulsteen AS?

Gullsmed Harry Ulsteen AS had revenue of NOK 5.3m in 2025.

Who is the general manager of Gullsmed Harry Ulsteen AS?

Nils Petter Ulsteen Hetty is registered as general manager of Gullsmed Harry Ulsteen AS.

Where is Gullsmed Harry Ulsteen AS based?

Gullsmed Harry Ulsteen AS has its business address in Drammen.

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.