BIZTRAC BETA
Retail sale of watches and jewellery

STORBYEN UR & GULL AS

Org. no. 986997911 Limited company (AS) Sarpsborg Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 6.1m
Operating profit NOK 422,000
Equity NOK 1.3m
Incorporated 2004
Employees 10
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STORBYEN UR & GULL AS is registered as a limited company in Sarpsborg, Østfold with organisation number 986997911. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2004 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel, samt hva som herved står i forbindelse, herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.1m in revenue and NOK 422,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.1m
Operating profit
NOK 422,000
Equity
NOK 1.3m
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.7%
Good
Equity as a share of total capital

Who owns STORBYEN UR & GULL AS?

BJØRKLUND RETAIL AS
STORBYEN UR & GULL AS
NOK 6.1m rev. · NOK 422,000 profit

STORBYEN UR & GULL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORBYEN UR & GULL AS

Who owns STORBYEN UR & GULL AS?

BJØRKLUND RETAIL AS is the largest registered owner, with 100.0%.

What is the revenue of STORBYEN UR & GULL AS?

STORBYEN UR & GULL AS had revenue of NOK 6.1m in 2024.

Where is STORBYEN UR & GULL AS based?

STORBYEN UR & GULL AS has its business address in Sarpsborg.

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.