biztrac. BETA
COMPANY REGISTER PROFILE
997979230 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

DISEN HOLDING AS

Org. no. 997979230 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −182,000
Equity NOK 286,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

DISEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 997979230. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i andre selskaper, eiendom og verdipapirer.”.

Former names: DISEN BYGG AS

Key figures · 2025

Operating profit
NOK −182,000
▼ −52 %
Equity
NOK 286,000
▼ −76 %
Est. value
NOK 293,000

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
-11.3%
Not satisfactory
Return on total assets
Solidity
23.4%
Good
Equity as a share of total capital

Who owns DISEN HOLDING AS?

DISEN HOLDING AS
· NOK −182,000 profit

DISEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DISEN HOLDING AS own?

DISEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

DISEN HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about DISEN HOLDING AS

Who owns DISEN HOLDING AS?

Bård Fornebo is the largest registered owner, with 100.0%.

Who is the general manager of DISEN HOLDING AS?

Bård Fornebo is registered as general manager of DISEN HOLDING AS.

Where is DISEN HOLDING AS based?

DISEN HOLDING 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 03.10.2026.

Report a problem

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