BIZTRAC BETA
Development of building projects

DIDSIV HOLDING AS

Org. no. 921230249 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −28,000
Equity NOK 1.4m
Incorporated 2018
Share capital NOK 30,000

Signals

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

DIDSIV HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 921230249. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, utvikling, drift og salg av fast eiendom. Investeringer i aksjer og andeler. Samt hva herved står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 1.4m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns DIDSIV HOLDING AS?

DIDRIK SIVERTSEN
DIDSIV HOLDING AS
NOK 0 rev. · NOK −28,000 profit

DIDSIV HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DIDSIV HOLDING AS own?

DIDSIV HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DIDSIV HOLDING AS

Who owns DIDSIV HOLDING AS?

DIDRIK SIVERTSEN is the largest registered owner, with 100.0%.

What is the revenue of DIDSIV HOLDING AS?

DIDSIV HOLDING AS had revenue of NOK 0 in 2024.

Where is DIDSIV HOLDING AS based?

DIDSIV HOLDING AS has its business address in Rådal.

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.