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

DLVRY AS

Org. no. 926493353 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 47.1m
Operating profit NOK −41.8m
Equity NOK 677.6m
Incorporated 2021
Employees 40
Share capital NOK 700,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−41,8 mill kr).

DLVRY AS is registered as a limited company in Oslo, Oslo with organisation number 926493353. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2021 and has 40 registered employees. Registered share capital is NOK 700,000, divided into 10000 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.”. The most recent filed accounts, for the 2024 financial year, show NOK 47.1m in revenue and NOK −41.8m in operating profit.

Key figures · 2024

Revenue
NOK 47.1m
Operating profit
NOK −41.8m
Equity
NOK 677.6m
Est. value
NOK 847.0m

Financial health · 2024

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

Who owns DLVRY AS?

DLVRY HOLDING AS
DLVRY AS
NOK 47.1m rev. · NOK −41.8m profit

DLVRY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DLVRY AS own?

DLVRY AS holds stakes in 17 companies:

See the full ownership structure →

Frequently asked questions about DLVRY AS

Who owns DLVRY AS?

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

What is the revenue of DLVRY AS?

DLVRY AS had revenue of NOK 47.1m in 2024.

Where is DLVRY AS based?

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