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

URMAKERMESTER TIDEMANN AS

Org. no. 817291082 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −31,000
Equity NOK −7.3m
Incorporated 2016
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

URMAKERMESTER TIDEMANN AS is registered as a limited company in Oslo, Oslo with organisation number 817291082. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Import, eksport og omsetning av bl.a. klokker og smykker samt annet som står i naturlig forbindelse med dette.”.

Former names: TIDEMANN UR AS

Key figures · 2025

Operating profit
NOK −31,000
▼ −63 %
Equity
NOK −7.3m
▼ −0 %

Financial health · 2025

Liquidity
2.69
Very good
Current assets ÷ current liabilities
Profitability
-22.4%
Not satisfactory
Return on total assets
Solidity
-5191.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns URMAKERMESTER TIDEMANN AS?

URMAKERMESTER TIDEMANN AS
· NOK −31,000 profit

URMAKERMESTER TIDEMANN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about URMAKERMESTER TIDEMANN AS

Who owns URMAKERMESTER TIDEMANN AS?

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

Where is URMAKERMESTER TIDEMANN AS based?

URMAKERMESTER TIDEMANN 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 03.10.2026.

Report a problem

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