BIZTRAC BETA
Other real estate activities on a fee or contract basis

SINCHR EIENDOM AS

Org. no. 816218942 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK 5.4m
Incorporated 2015
Share capital NOK 60,000

Signals

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

SINCHR EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 816218942. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. Registered share capital is NOK 60,000, divided into 2000 shares. The company's stated purpose is: “Forvaltning av eiendom, og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −46,000
Equity
NOK 5.4m
Est. value
NOK 11.0m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.5%
Satisfactory
Equity as a share of total capital

Who owns SINCHR EIENDOM AS?

SAXEN HOLDING AS
SINCHR EIENDOM AS
· NOK −46,000 profit

SINCHR EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SINCHR EIENDOM AS own?

SINCHR EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SINCHR EIENDOM AS

Who owns SINCHR EIENDOM AS?

SAXEN HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of SINCHR EIENDOM AS?

Christian Reitan Hatlehol is registered as general manager of SINCHR EIENDOM AS.

Where is SINCHR EIENDOM AS based?

SINCHR EIENDOM 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.