BIZTRAC BETA
Retail sale of watches and jewellery

GULLSMED ANTON HUSEBY AS

Org. no. 954919250 Limited company (AS) Indre Østfold Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 7.8m
Operating profit NOK 1.4m
Equity NOK 5.4m
Incorporated 1989
Employees 6
Share capital NOK 500,000

GULLSMED ANTON HUSEBY AS is registered as a limited company in Indre Østfold, Østfold with organisation number 954919250. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1989 and has 6 registered employees. Registered share capital is NOK 500,000. The company's stated purpose is: “Kjøp, salg og reparasjon av gullsmedvarer og gaveartikler samt alt som naturlig hører med til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 7.8m
Operating profit
NOK 1.4m
Equity
NOK 5.4m
Est. value
NOK 8.0m

Financial health · 2025

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

Who owns GULLSMED ANTON HUSEBY AS?

GULLGRUVA AS
GULLSMED ANTON HUSEBY AS
NOK 7.8m rev. · NOK 1.4m profit

GULLSMED ANTON HUSEBY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLSMED ANTON HUSEBY AS

Who owns GULLSMED ANTON HUSEBY AS?

GULLGRUVA AS is the largest registered owner, with 100.0%.

What is the revenue of GULLSMED ANTON HUSEBY AS?

GULLSMED ANTON HUSEBY AS had revenue of NOK 7.8m in 2025.

Who is the general manager of GULLSMED ANTON HUSEBY AS?

Siw Johnsrud Rande is registered as general manager of GULLSMED ANTON HUSEBY AS.

Where is GULLSMED ANTON HUSEBY AS based?

GULLSMED ANTON HUSEBY AS has its business address in Mysen.

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.