BIZTRAC BETA
Retail sale of watches and jewellery

OPAL GULLSMEDFORRETNING AS

Org. no. 915011012 Limited company (AS) Bodø Incorporated 1966 Active
Ownership graph ↗
Revenue 2025 NOK 9.8m
Operating profit NOK 932,000
Equity NOK 3.4m
Incorporated 1966
Employees 10
Share capital NOK 500,000

OPAL GULLSMEDFORRETNING AS is registered as a limited company in Bodø, Nordland with organisation number 915011012. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1966 and has 10 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Handel og produksjon innen gullsmedbransjen og beslektede bransjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.8m in revenue and NOK 932,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.8m
Operating profit
NOK 932,000
Equity
NOK 3.4m
Est. value
NOK 5.1m

Financial health · 2025

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

Who owns OPAL GULLSMEDFORRETNING AS?

JAN CHRISTIAN ENGAN
OPAL GULLSMEDFORRETNING AS
NOK 9.8m rev. · NOK 932,000 profit

OPAL GULLSMEDFORRETNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPAL GULLSMEDFORRETNING AS

Who owns OPAL GULLSMEDFORRETNING AS?

JAN CHRISTIAN ENGAN is the largest registered owner, with 100.0%.

What is the revenue of OPAL GULLSMEDFORRETNING AS?

OPAL GULLSMEDFORRETNING AS had revenue of NOK 9.8m in 2025.

Who is the general manager of OPAL GULLSMEDFORRETNING AS?

Jan Christian Engan is registered as general manager of OPAL GULLSMEDFORRETNING AS.

Where is OPAL GULLSMEDFORRETNING AS based?

OPAL GULLSMEDFORRETNING AS has its business address in Bodø.

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.