BIZTRAC BETA
Wholesale of watches and jewellery

TIDEMANN & HEIER AS

Org. no. 933763641 Limited company (AS) Enebakk Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −287
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

TIDEMANN & HEIER AS is registered as a limited company in Enebakk, Akershus with organisation number 933763641. The business is classified under wholesale of watches and jewellery (NACE 46.480). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Import, eksport og produsere og selge klokker og deler og tilbehør til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −287 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −287
Equity
NOK 23,000
Est. value
NOK 29,000

Financial health · 2024

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

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

Who owns TIDEMANN & HEIER AS?

LARS CHRISTIAN TIDEMANN
TIDEMANN & HEIER AS
NOK 0 rev. · NOK −287 profit

TIDEMANN & HEIER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIDEMANN & HEIER AS

Who owns TIDEMANN & HEIER AS?

LARS CHRISTIAN TIDEMANN is the largest registered owner, with 50.0%.

What is the revenue of TIDEMANN & HEIER AS?

TIDEMANN & HEIER AS had revenue of NOK 0 in 2024.

Who is the general manager of TIDEMANN & HEIER AS?

Lars Christian Tidemann is registered as general manager of TIDEMANN & HEIER AS.

Where is TIDEMANN & HEIER AS based?

TIDEMANN & HEIER AS has its business address in Enebakk.

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.