BIZTRAC BETA
Computer programming activities

VEDAH HOLDING AS

Org. no. 927546345 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 824,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).

VEDAH HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 927546345. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte rettigheter, aksjer, obligasjoner og andre verdipapir, eie og forvalte eiendom, deltakelse i andre selskaper, samt hva som står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 824,000
Est. value
NOK 9.9m

Financial health · 2024

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

Who owns VEDAH HOLDING AS?

KARANDEEP SINGH BHARJ
VEDAH HOLDING AS
NOK 0 rev. · NOK −8,000 profit

VEDAH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VEDAH HOLDING AS own?

VEDAH HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VEDAH HOLDING AS

Who owns VEDAH HOLDING AS?

KARANDEEP SINGH BHARJ is the largest registered owner, with 100.0%.

What is the revenue of VEDAH HOLDING AS?

VEDAH HOLDING AS had revenue of NOK 0 in 2024.

Where is VEDAH HOLDING AS based?

VEDAH HOLDING AS has its business address in Loddefjord.

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.