BIZTRAC BETA
Retail sale of watches and jewellery

URMAKER LARSEN STRØMMEN AS

Org. no. 980713032 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 13.5m
Operating profit NOK 629,000
Equity NOK 285,000
Incorporated 1999
Employees 8
Share capital NOK 100,000

URMAKER LARSEN STRØMMEN AS is registered as a limited company in Oslo, Oslo with organisation number 980713032. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1999 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Urmakervirksomhet, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.5m in revenue and NOK 629,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.5m
Operating profit
NOK 629,000
Equity
NOK 285,000
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
0.81
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.6%
Not satisfactory
Equity as a share of total capital

Who owns URMAKER LARSEN STRØMMEN AS?

CHRISTIAN BJERKE AS
URMAKER LARSEN STRØMMEN AS
NOK 13.5m rev. · NOK 629,000 profit

URMAKER LARSEN STRØMMEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about URMAKER LARSEN STRØMMEN AS

Who owns URMAKER LARSEN STRØMMEN AS?

CHRISTIAN BJERKE AS is the largest registered owner, with 100.0%.

What is the revenue of URMAKER LARSEN STRØMMEN AS?

URMAKER LARSEN STRØMMEN AS had revenue of NOK 13.5m in 2024.

Who is the general manager of URMAKER LARSEN STRØMMEN AS?

Christian Bjerke is registered as general manager of URMAKER LARSEN STRØMMEN AS.

Where is URMAKER LARSEN STRØMMEN AS based?

URMAKER LARSEN STRØMMEN AS has its business address in Oslo.

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.