biztrac. BETA
COMPANY REGISTER PROFILE
927649349 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

DIB HOLDING AS

Org. no. 927649349 Limited company (AS) Gloppen Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −34,000
Equity NOK 2.6m
Incorporated 2021
Share capital NOK 85,000

Signals

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

DIB HOLDING AS is registered as a limited company in Gloppen, Vestland with organisation number 927649349. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 85,000, divided into 84825 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper samt forvalte eierinteressene av disse. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Former names: DAMAMA AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −34,000
▲ +70 %
Equity
NOK 2.6m
▼ −60 %
Est. value
NOK 27.9m

Financial health · 2025

Liquidity
16.83
Very good
Current assets ÷ current liabilities
Profitability
90.1%
Very good
Return on total assets
Solidity
97.6%
Very good
Equity as a share of total capital

Who owns DIB HOLDING AS?

DIB HOLDING AS
NOK 0 rev. · NOK −34,000 profit

DIB HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DIB HOLDING AS own?

DIB HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DIB HOLDING AS

Who owns DIB HOLDING AS?

Jan Helge Bolseth is the largest registered owner, with 100.0%.

What is the revenue of DIB HOLDING AS?

DIB HOLDING AS had revenue of NOK 0 in 2025.

Where is DIB HOLDING AS based?

DIB HOLDING AS has its business address in Sandane.

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.