BIZTRAC BETA
COMPANY REGISTER PROFILE
992123680 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

SICH HOLDING AS

Org. no. 992123680 Limited company (AS) Asker Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −32,000
Equity NOK 6.5m
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−32k kr).

SICH HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 992123680. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 400 shares. The company's stated purpose is: “Investere i verdipapirer og fast eiendom herunder også innleie og fremleie.”.

Key figures · 2025

Operating profit
NOK −32,000
▼ −25 %
Equity
NOK 6.5m
▼ −7 %
Est. value
NOK 5.9m

Financial health · 2025

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.3%
Not satisfactory
Return on total assets
Solidity
93.4%
Very good
Equity as a share of total capital

Who owns SICH HOLDING AS?

SICH HOLDING AS
· NOK −32,000 profit

SICH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SICH HOLDING AS

Who owns SICH HOLDING AS?

CHRISTIAN BRENNUM is the largest registered owner, with 100.0%.

Where is SICH HOLDING AS based?

SICH HOLDING AS has its business address in Asker.

Property

Business address Øvre Båstad vei 21, 1387 Asker
Cadastral unit 3203-48/54/0/0
Building Enebolig · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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