BIZTRAC BETA
Uoppgitt

KUMAR IN VEST AS

Org. no. 932204878 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2023
Share capital NOK 30,000

KUMAR IN VEST AS is registered as a limited company in Oslo, Oslo with organisation number 932204878. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i og eie aksjer, finansielle instrumenter og andeler i andre selskaper, både ved egenkapital og gjeld, samt annen virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns KUMAR IN VEST AS?

DANIEL KUMAR
KUMAR IN VEST AS
NOK 0 rev. · NOK 0 profit

KUMAR IN VEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KUMAR IN VEST AS own?

KUMAR IN VEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KUMAR IN VEST AS

Who owns KUMAR IN VEST AS?

DANIEL KUMAR is the largest registered owner, with 100.0%.

What is the revenue of KUMAR IN VEST AS?

KUMAR IN VEST AS had revenue of NOK 0 in 2025.

Who is the general manager of KUMAR IN VEST AS?

Daniel Kumar is registered as general manager of KUMAR IN VEST AS.

Where is KUMAR IN VEST AS based?

KUMAR IN VEST 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.