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

DEVA HOLDING AS

Org. no. 928787710 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −2.1m
Equity NOK −2.2m
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,2 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,1 mill kr).

DEVA HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 928787710. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Formuesforvaltning, herunder investering i aksjer og andre verdipapirer samt annen tilknyttet virksomhet”.

Key figures · 2024

Operating profit
NOK −2.1m
Equity
NOK −2.2m

Financial health · 2024

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

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

Who owns DEVA HOLDING AS?

Ashwani Kumar
DEVA HOLDING AS
· NOK −2.1m profit

DEVA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does DEVA HOLDING AS own?

DEVA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

DEVA HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about DEVA HOLDING AS

Who owns DEVA HOLDING AS?

Ashwani Kumar is the largest registered owner, with 50.0%.

Who is the general manager of DEVA HOLDING AS?

Rahul Vidwat is registered as general manager of DEVA HOLDING AS.

Where is DEVA HOLDING AS based?

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