# How many ODI runs has Gulsan Jha scored?

Gulsan Jha has 1,089 runs in 48 ODI innings from 56 matches at an average of 28.65 and a strike rate of 83.96. Highest score: 67*.

Source: https://crickrida.com/questions/how-many-odi-runs-has-gulsan-jha-scored/

PLAYER STATS

- ODI runs: 1,089

*Gulsan Jha: official career runs by format*

- ODI: 1,089
- T20I: 672

Official career snapshot. Formats without a recorded value stay blank.

## See the full Gulsan Jha record

This is the official international snapshot, not a scorecard sample. [Gulsan Jha career profile](https://crickrida.com/players/gulsan-jha/) has format cards, charts and the complete batting, bowling and fielding tables. [Open the related leaderboard](https://crickrida.com/records/men/odi/most-runs/) to see this figure in rank order.

## More Gulsan Jha questions

## [What is Gulsan Jha's ODI batting average?](https://crickrida.com/questions/what-is-gulsan-jha-odi-batting-average/)

ODI

Gulsan Jha's ODI batting average is 28.65, from 1,089 runs and 48 innings.

## [How many ODI wickets has Gulsan Jha taken?](https://crickrida.com/questions/how-many-odi-wickets-has-gulsan-jha-taken/)

ODI

Gulsan Jha has taken 43 wickets in ODI from 56 matches at a bowling average of 34.30. Best innings: 5/38.

## [How many T20I runs has Gulsan Jha scored?](https://crickrida.com/questions/how-many-t20i-runs-has-gulsan-jha-scored/)

T20I

Gulsan Jha has 672 runs in 47 T20I innings from 59 matches at an average of 19.76 and a strike rate of 138.55. Highest score: 54.

## [What is Gulsan Jha's T20I batting average?](https://crickrida.com/questions/what-is-gulsan-jha-t20i-batting-average/)

T20I

Gulsan Jha's T20I batting average is 19.76, from 672 runs and 47 innings.

## [How many T20I wickets has Gulsan Jha taken?](https://crickrida.com/questions/how-many-t20i-wickets-has-gulsan-jha-taken/)

T20I

Gulsan Jha has taken 29 wickets in T20I from 59 matches at a bowling average of 22.06. Best innings: 3/31.

Career records checked: 2026-11-09. Official career figures. A missing field stays missing; it is never inferred from a partial scorecard.
