One cited deathJujutsu Kaisen
Does this death move the ranking?

Confirms the ladder

The higher-ranked entity killed the lower-ranked one. Record and ladder agree.

Ryomen Sukuna vs Hajime Kashimo

The killerRyomen SukunaJujutsu Kaisen · rank 1
5 places
The victimHajime KashimoJujutsu Kaisen · rank 6

The only death on this page the loser arranged himself, which makes it nearly worthless as evidence about either of them. The opponent was named at the point of purchase, and named as a man already centuries dead by the time the buyer drew breath — so the outcome was fixed by the selection rather than discovered in the fight. Nothing can move on a result the contract already described. What it does establish is the ceiling on what four centuries buys, and the answer is a seat rather than a win.

The connecting record

shownJujutsu Kaisen

Ryomen Sukuna killed Hajime Kashimo in Jujutsu Kaisen.

What each of them is ranked on

The killer · Ryomen Sukuna · rank 1

The King of Curses

Jujutsu Kaisencomicanimationcontested

Negotiated one minute inside a borrowed body, called it a single time, and spent it taking Megumi Fushiguro. Kept those hands, and used them to cut Gojo Satoru down in front of the sorcerers who had staked the whole plan on the opposite result. The stretch of Shibuya he cut apart earlier was a longer stay in the same borrowed body, bought by other people forcing his fingers down its throat.

  • shownJujutsu Kaisen · ch. 8

    Takes control of Yuji's body and tears Yuji's own heart out of his chest.

  • statedJujutsu Kaisen · ch. 11

    Sets the terms of a binding vow granting him one minute of control, with Yuji left no memory of the agreement.

  • shownJujutsu Kaisen · ch. 119

    Cuts apart a large area of Shibuya and the people standing in it.

All 9 citations
  • shownJujutsu Kaisen · ch. 115

    Dodges Jogo's Maximum: Meteor.

  • statedJujutsu Kaisen · ch. 115

    Sukuna says the meteor would have hurt him if it had connected.

  • shownJujutsu Kaisen · ch. 116

    Burns Jogo to death.

  • shownJujutsu Kaisen · ch. 236

    Cuts Gojo Satoru in half at Shinjuku.

  • statedJujutsu Kaisen · ch. 236

    Sukuna buys the strike with a binding vow that lifts the conditions the world-cutting slash normally carries.

  • statedJujutsu Kaisen · ch. 119

    Malevolent Shrine is described as a domain opened without a barrier around it.

Ryomen Sukuna on the Jujutsu Kaisen ladder

The victim · Hajime Kashimo · rank 6

Jujutsu Kaisencomiccontested

Paid four centuries and the body he was born in for a seat at a single fight, and set those terms with Kenjaku directly instead of being written into the game by somebody else. Spent the seat on Sukuna and died in it, having first put enough through Hakari — an arm, a head, and a last one into the lower torso just as the wager ran out — to establish that a domain built on a bet does not stop when the man inside it runs out of blood.

  • statedJujutsu Kaisen · ch. 187

    Kashimo made a binding vow with Kenjaku to be reincarnated four hundred years after his own lifetime.

  • statedJujutsu Kaisen · ch. 187

    Kenjaku names the opponent as Sukuna.

  • statedJujutsu Kaisen · ch. 116

    Sukuna is placed a thousand years back, in the Heian era.

All 7 citations
  • shownJujutsu Kaisen · ch. 186

    Turns his cursed energy into electricity against Hakari.

  • shownJujutsu Kaisen · ch. 188–189

    Fails to put Hakari down while Hakari's wounds keep closing.

  • shownJujutsu Kaisen · ch. 237

    Fights Sukuna at Shinjuku.

  • shownJujutsu Kaisen · ch. 238

    Sukuna kills him.

Hajime Kashimo on the Jujutsu Kaisen ladder

What this does not settle

One death in one work. It is the only place the record puts these two in the same room, and it is evidence about that meeting and nothing wider — not a general matchup, not a rematch, and not a ranking of its own.

The ladder above it is argued from everything either of them has been shown doing; this page is argued from one citation.

Where the two disagree, the disagreement is the point, and it stays visible rather than being resolved by whichever of them happens to be on this page.