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

GULLSMED 1 AS

Org. no. 989198874 Limited company (AS) Moss Incorporated 2005 Active
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 2.7m
Incorporated 2005
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

GULLSMED 1 AS is registered as a limited company in Moss, Østfold with organisation number 989198874. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 50 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom, samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
▼ −1 %
Equity
NOK 2.7m
▼ −0 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.4%
Not satisfactory
Return on total assets
Solidity
97.1%
Very good
Equity as a share of total capital

Who owns GULLSMED 1 AS?

GULLSMED 1 AS
NOK 0 rev. · NOK −12,000 profit

GULLSMED 1 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GULLSMED 1 AS own?

GULLSMED 1 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GULLSMED 1 AS

Who owns GULLSMED 1 AS?

Odd Christer Kvæken Johnsen is the largest registered owner, with 100.0%.

What is the revenue of GULLSMED 1 AS?

GULLSMED 1 AS had revenue of NOK 0 in 2025.

Where is GULLSMED 1 AS based?

GULLSMED 1 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 03.10.2026.

Report a problem

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