Reaching 1300 in rapid: my game 1313

By · Updated

Reaching 1300 in rapid took me 1,313 games in my recorded Chess.com history. On January 15, 2025, I beat mafimoshgele (1290) with Black in a Modern Defense, Three Pawns Attack, and my recorded rating went from 1298 in game 1312 to 1306. It was not a pretty win: Stockfish gave my play 62.1% accuracy and found a mate in two that I didn't see.

I like this milestone because it is honest about what a rating threshold is. I didn't cross 1300 by playing a perfect game. I crossed it in a messy, sharp game in which both sides blundered, and I happened to be the last one to take the chance.

Reaching 1300 in rapid, in context

My first recorded rapid game was on January 10, 2024, at 631. By game 1313 the totals read 616 wins, 662 losses and 35 draws. I lost more games than I won on the way to 1300. The first crossing of 1100 came in game 656, and the first crossing of 1200 in game 1237. So 1200 to 1300 took 76 games, much faster than the 581 games between 1100 and 1200.

The run-up was the best stretch of the series so far. Game 1298 was a loss that left me at 1229, my fourth defeat in a row. Then I won seven straight games (1299 to 1305) and reached 1287. From game 1298 to game 1313 I went 12 wins and 3 losses, gaining 77 points in fifteen games. The weekly diary for that week has every result.

Game detail Recorded fact
Date January 15, 2025
Opponent mafimoshgele, 1290
My colour Black
Recorded rating 1298 in game 1312, 1306 in this game
Time control 10 minutes, no increment
Opening Modern Defense, Three Pawns Attack (B06)
Result Win, White resigned after my 31st move
Engine accuracy Black 62.1%, White 63.2%
My blunders / mistakes / inaccuracies 5 / 1 / 7

The opening: a free pawn

After 1.e4 d6 2.d4 g6 3.f4, White set up the three-pawn centre that gives the line its name. My bishop took the knight on f3 on move 6, and on move 8 White played 8.Bd3, which the analysis marks as a blunder (from +1.06 to -0.76). My reply 8...Nxd4 took the pawn on d4 and matched the engine's choice. That was the first time in the game I was better.

From there, both of us kept making errors. White castled long on move 12, and I answered with 12...a6, which the engine calls a blunder: it wanted the faster 12...b5. On move 13 I played 13...Qa5 when Stockfish preferred taking on f5 with the g-pawn. My queenside attack was slow, but White's play wasn't perfect either, and by move 17 I had a big advantage again.

Position one: move 17, the pawn capture I skipped

Before my 17th move the saved evaluation was -5.84. The numbers are from White's side, so a big negative number was very good for me. I moved my knight from f6 back to e8. The evaluation jumped to +0.38, roughly equal. The analysis marks this as a blunder and picks it as the lesson of the game.

r . . . . r k .
. p . . . p b p
. . . p . n p .
q . p . p P . .
. p . . P . . P
P . . . B . . .
N P P . . Q P .
. K . R . . . R
Game 1313, Black to move on move 17
Knight from f6 to e8 Pawn takes the pawn on a3, next to White's king

Stockfish wanted 17...bxa3: my b-pawn takes the pawn on a3, one of the pawns in front of White's king on b1. Its line continues 18.b4 cxb4, with another pawn capture on the queenside. I took on a3 one move later anyway, but by then White had pushed h4 to h5 and the moment was different. The knight move was defensive when the position was asking me to attack.

Position two: move 22, the right capture

Five moves later I got another chance, and this time I took it. White's 22.Bg5 was marked as a blunder (from +1.52 to -4.18). My pawn on c4 captured on b3.

r . . . . r k .
. p . . . . b p
. . . p . n p .
q . . . p P B .
. . p . P . . Q
p P . . . . . .
N . P . . . P .
. K . R . . . R
Game 1313, Black to move on move 22
Pawn takes the pawn on b3 and attacks the knight on a2 Same move: Stockfish's first choice

The checker describes it as a pawn capture that attacks the knight on a2. It is the engine's first choice, and the evaluation stayed around -4. I want to keep this board in my notes as much as the mistakes. When the position offered a capture next to the enemy king, I found it.

Position three: move 26, mate in two

This is the moment I think about most from this game. White had just taken a pawn on h6 with the queen. The saved evaluation before my 26th move was -M2: Black had a forced mate in two moves. I moved my king to f7, and the evaluation became +1.25, slightly better for White.

r . . . . r k .
. p . . . . . .
. q . p . b p Q
. . . . p P . .
. . . . P . . .
p P . . . . . .
N . . . . . P .
. K . R . . . R
Game 1313, Black to move on move 26 (the turning point)
King from g8 to f7 Queen takes the pawn on b3 with check, then mates on b2

The mate is short: 26...Qxb3+ (the queen takes the pawn on b3 with check, also attacking the rook on d1 and the knight on a2), 27.Kc1 and 27...Qb2 is checkmate. The checker labels the position "black can force checkmate". I had almost five minutes on my clock after the move, so it wasn't time trouble. The record can't tell me what I was looking at, but the board shows what I missed: a capture with check, two moves from mate.

A check is a move that attacks the king. The most useful habit I can take from this board is to look at every check before I defend, even when I feel under attack. Here a capture with check ended the game.

Position four: move 31, the finish

White gave me a second chance. 29.Kc2 was marked as a blunder (+0.92 to -2.43), and after 29...Rc8+ 30.Kd2, Stockfish again saw a forced mate for me. I played 30...Qf2+ (the engine's choice), and after 31.Kd3 I took the knight on a2.

. . r k . r . .
. p . . . . . R
. . . p . b Q .
. . . . p P . .
. . . . P . . .
p P . K . . . .
N . . . . q P .
. . . R . . . .
Game 1313, Black to move on move 31
Queen takes the knight on a2 and attacks the pawn on b3 Queen to d4 with check keeps a forced mate

My move was not the fastest: the engine had mate in five starting with 31...Qd4+, and my capture left a still winning -6.54. White resigned right after. It's a small echo of move 26. I took material instead of checking, and this time it didn't matter.

What this milestone teaches me

Three boards in this game are about the same thing: when I had a direct way at White's king, I either took it (move 22) or chose something slower (moves 17, 26 and 31). The move 26 miss is the costliest one in the whole game, and it came with plenty of time on my clock.

So my takeaway is a checklist order, not a slogan. Checks first, then captures, then threats, and only then defensive moves. If you want to know what the colour of the arrows and the plus and minus signs mean in a review like this, the guide to reading Stockfish analysis explains it.

I also want to remember that both players blundered here. White's error count was higher than mine (nine blunders to my five). At this level, a game is often decided by who makes the last mistake, not by who makes none.

What happened after the crossing

The next game was a loss to vp2play (1403), which left my rating at exactly 1300. Then I won four of the next five games and reached 1328 in game 1319. My rating stayed at 1300 or above for 31 games after this one and peaked at 1334 in game 1329. It first dropped below the line in game 1345, during a run of seven straight losses.

So this crossing was more stable than my first crossing of 1100, which fell back below the line within three games. It was not permanent. The complete journey tells what came next, and you can replay the original game on Chess.com to see the actual moves around these boards. To review your own finished games the same way, you can use Chess Coach in Claude or ChatGPT.

Frequently asked questions

How many games did reaching 1300 take me?

My recorded rapid history first reached 1300 in game 1313, on January 15, 2025, when my rating read 1306.

Was game 1313 a clean win?

No. Stockfish gave my play with Black 62.1% accuracy, with five blunders, one mistake and seven inaccuracies, including a missed mate in two on move 26.

Did I stay above 1300 afterwards?

For a while. My recorded rating stayed at 1300 or higher for the next 31 games, peaking at 1334 in game 1329, and first fell below the line in game 1345.