biztrac. BETA
COMPANY REGISTER PROFILE
988629901 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

LADAKH AS

Org. no. 988629901 Limited company (AS) Nittedal Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −46,000
Incorporated 2005
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−46k kr).
  • Nylig endring 2026-10-07 Aksjekapital registrert 2026-10-07.

LADAKH AS is registered as a limited company in Nittedal, Akershus with organisation number 988629901. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 200000 shares. The company's stated purpose is: “Selskapets formål er investeringer i verdipapirer og fast eiendom, samt dertil hørende virksomhet, samt handel med aksjer og verdipapirer, herunder lånefinansierte investeringer med verdipapirer og valuta, hvor selskapet kan pantsette sine aktiver i den forbindelse.”.

Key figures · 2025

Operating profit
NOK −46,000
▲ +1 %

Financial health · 2025

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

Who owns LADAKH AS?

LADAKH AS
· NOK −46,000 profit

LADAKH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LADAKH AS own?

LADAKH AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LADAKH AS

Who owns LADAKH AS?

Aron Kobberstad Krishna is the largest registered owner, with 100.0%.

Who is the general manager of LADAKH AS?

Aron Kobberstad Krishna is registered as general manager of LADAKH AS.

Where is LADAKH AS based?

LADAKH AS has its business address in Hagan.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.