BIZTRAC BETA
Retail sale of watches and jewellery

SAFIR GULLSMEDFORRETNING AS

Org. no. 983768059 Limited company (AS) Moss Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 745,000
Equity NOK 4.4m
Incorporated 2001
Share capital NOK 100,000

SAFIR GULLSMEDFORRETNING AS is registered as a limited company in Moss, Østfold with organisation number 983768059. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Gullsmedforretning, kjøp og salg av handelsvarer samt investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 745,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 745,000
Equity
NOK 4.4m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns SAFIR GULLSMEDFORRETNING AS?

LASSE NORMANN PETTERSEN
SAFIR GULLSMEDFORRETNING AS
NOK 1.3m rev. · NOK 745,000 profit

SAFIR GULLSMEDFORRETNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAFIR GULLSMEDFORRETNING AS own?

SAFIR GULLSMEDFORRETNING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SAFIR GULLSMEDFORRETNING AS

Who owns SAFIR GULLSMEDFORRETNING AS?

LASSE NORMANN PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of SAFIR GULLSMEDFORRETNING AS?

SAFIR GULLSMEDFORRETNING AS had revenue of NOK 1.3m in 2024.

Where is SAFIR GULLSMEDFORRETNING AS based?

SAFIR GULLSMEDFORRETNING AS has its business address in Moss.

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.