BIZTRAC BETA
Freight transport by road

JRD INVEST AS

Org. no. 829761122 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −295
Equity NOK −32,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−32k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−295 kr).

JRD INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 829761122. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å investere i andre virksomheter gjennom aksjer eller på annen måte. Eiendomsutvikling, eiendomsbesittelse, kjøp og salg av fast eiendom, utleie, aksjebesittelse, å engasjere seg i beslektede virksomheter, samt alt hva hermed måtte stå i forbindelse.”.

Key figures · 2024

Operating profit
NOK −295
Equity
NOK −32,000

Financial health · 2024

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

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

Who owns JRD INVEST AS?

Kiyan Malang
JRD INVEST AS
· NOK −295 profit

JRD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JRD INVEST AS own?

JRD INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JRD INVEST AS

Who owns JRD INVEST AS?

Kiyan Malang is the largest registered owner, with 100.0%.

Who is the general manager of JRD INVEST AS?

Kiyan Malang is registered as general manager of JRD INVEST AS.

Where is JRD INVEST AS based?

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