BIZTRAC BETA
Non-specialised wholesale of food, beverages and tobacco

DLVRY HOLDING AS

Org. no. 827436712 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −104,000
Equity NOK 727.6m
Incorporated 2021
Share capital NOK 840,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−104k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-02 Aksjekapital registrert 2026-02-02.

DLVRY HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 827436712. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2021. Registered share capital is NOK 840,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, utvikle og selge eller på annet vis helt eller delvis realisere virksomhet og selskaper, samt deltagelse i andre selskaper og dertil hørende virksomhet.”.

Key figures · 2024

Operating profit
NOK −104,000
Equity
NOK 727.6m
Est. value
NOK 357.0m

Financial health · 2024

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

Who owns DLVRY HOLDING AS?

DLVRY GROUP AS
DLVRY HOLDING AS
· NOK −104,000 profit

DLVRY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DLVRY HOLDING AS own?

DLVRY HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DLVRY HOLDING AS

Who owns DLVRY HOLDING AS?

DLVRY GROUP AS is the largest registered owner, with 100.0%.

Where is DLVRY HOLDING AS based?

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

Report a problem

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