biztrac. BETA
COMPANY REGISTER PROFILE
933261107 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

DOBLYKKEN HOLDING AS

Org. no. 933261107 Limited company (AS) Ringsaker Incorporated 2024 Active
Operating profit NOK −1,000
Equity NOK 777,000
Incorporated 2024
Share capital NOK 50,000

Signals

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

DOBLYKKEN HOLDING AS is registered as a limited company in Ringsaker, Innlandet with organisation number 933261107. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −1,000
Equity
NOK 777,000
▲ +1454 %
Est. value
NOK 9.4m

Financial health · 2025

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
28.2%
Good
Equity as a share of total capital

Who owns DOBLYKKEN HOLDING AS?

DOBLYKKEN HOLDING AS
· NOK −1,000 profit

DOBLYKKEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DOBLYKKEN HOLDING AS own?

DOBLYKKEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DOBLYKKEN HOLDING AS

Who owns DOBLYKKEN HOLDING AS?

Andreas Haandlykken is the largest registered owner, with 100.0%.

Where is DOBLYKKEN HOLDING AS based?

DOBLYKKEN HOLDING AS has its business address in Brumunddal.

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.