BIZTRAC BETA
COMPANY REGISTER PROFILE
923552340 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SYDEN HOLDING AS

Org. no. 923552340 Limited company (AS) Time Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −39,000
Equity NOK 8.0m
Incorporated 2019
Share capital NOK 45,000

Signals

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

SYDEN HOLDING AS is registered as a limited company in Time, Rogaland with organisation number 923552340. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 45,000, divided into 100 shares. The company's stated purpose is: “Investeringer.”.

Key figures · 2025

Operating profit
NOK −39,000
▼ −86 %
Equity
NOK 8.0m
▲ +149 %
Est. value
NOK 35.7m

Financial health · 2025

Liquidity
22.78
Very good
Current assets ÷ current liabilities
Profitability
96.7%
Very good
Return on total assets
Solidity
94.7%
Very good
Equity as a share of total capital

Who owns SYDEN HOLDING AS?

SYDEN HOLDING AS
· NOK −39,000 profit

SYDEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SYDEN HOLDING AS own?

SYDEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SYDEN HOLDING AS

Who owns SYDEN HOLDING AS?

MAGNUS ALEKSANDER GRØDEM is the largest registered owner, with 100.0%.

Where is SYDEN HOLDING AS based?

SYDEN HOLDING AS has its business address in Bryne.

Property

Business address Loen 22, 4340 Bryne
Cadastral unit 1121-1/859/0/0
Building Kjede/atriumhus · 1 unit

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.