BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

VIPAN INVEST AS

Org. no. 990196125 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −106,000
Equity NOK 2.6m
Incorporated 2006
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−106k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VIPAN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 990196125. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom, aksjer og næringsvirksomhet, herunder å delta i andre selskaper med lignende virksomhet. ”.

Key figures · 2025

Operating profit
NOK −106,000
Equity
NOK 2.6m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns VIPAN INVEST AS?

VIPAN KUMAR AGNIHOTRI
VIPAN INVEST AS
· NOK −106,000 profit

VIPAN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIPAN INVEST AS own?

VIPAN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIPAN INVEST AS

Who owns VIPAN INVEST AS?

VIPAN KUMAR AGNIHOTRI is the largest registered owner, with 100.0%.

Who is the general manager of VIPAN INVEST AS?

Vipan Kumar Agnihotri is registered as general manager of VIPAN INVEST AS.

Where is VIPAN INVEST AS based?

VIPAN INVEST 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.