BIZTRAC BETA
Uoppgitt

DOBBELBOGEY AS

Org. no. 925782548 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK 77,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

DOBBELBOGEY AS is registered as a limited company in Oslo, Oslo with organisation number 925782548. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet, konsulenttjenester og all dertilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
Equity
NOK 77,000
Est. value
NOK 79,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DOBBELBOGEY AS?

INGRID HAGEN L'ORANGE
DOBBELBOGEY AS
NOK 0 rev. · NOK −21,000 profit

DOBBELBOGEY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DOBBELBOGEY AS own?

DOBBELBOGEY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DOBBELBOGEY AS

Who owns DOBBELBOGEY AS?

INGRID HAGEN L'ORANGE is the largest registered owner, with 100.0%.

What is the revenue of DOBBELBOGEY AS?

DOBBELBOGEY AS had revenue of NOK 0 in 2025.

Who is the general manager of DOBBELBOGEY AS?

Ingrid Hagen L'orange is registered as general manager of DOBBELBOGEY AS.

Where is DOBBELBOGEY AS based?

DOBBELBOGEY 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 15.06.2026.

Report a problem

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