BIZTRAC BETA
Retail sale of watches and jewellery

LØRENSKOG UR OG GULL AS

Org. no. 984352689 Limited company (AS) Lørenskog Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 5.9m
Operating profit NOK −189,000
Equity NOK 1.5m
Incorporated 2002
Employees 10
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−189k kr).

LØRENSKOG UR OG GULL AS is registered as a limited company in Lørenskog, Akershus with organisation number 984352689. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2002 and has 10 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Handel, agenturvirksomhet, eksport og import 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 5.9m in revenue and NOK −189,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.9m
Operating profit
NOK −189,000
Equity
NOK 1.5m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns LØRENSKOG UR OG GULL AS?

HBS 1969 AS
LØRENSKOG UR OG GULL AS
NOK 5.9m rev. · NOK −189,000 profit

LØRENSKOG UR OG GULL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØRENSKOG UR OG GULL AS

Who owns LØRENSKOG UR OG GULL AS?

HBS 1969 AS is the largest registered owner, with 100.0%.

What is the revenue of LØRENSKOG UR OG GULL AS?

LØRENSKOG UR OG GULL AS had revenue of NOK 5.9m in 2024.

Where is LØRENSKOG UR OG GULL AS based?

LØRENSKOG UR OG GULL AS has its business address in Lørenskog.

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.