Reaching 1100 in rapid: my game 656
Reaching 1100 in rapid took me 656 games in this recorded Chess.com history. On July 4, 2024, I beat wahoo82 (1082) with Black in a Scotch Game, and my recorded rating moved from 1096 to 1104. Stockfish gave my play 94.1% accuracy, with one mistake and no blunders.
That is a useful milestone because the game contains both sides of the story. I missed a better developing move early, then found a necessary capture and later won a rook. Crossing the rating line did not require a flawless game. It did require playing the position in front of me well enough after the first mistake.
Reaching 1100 in rapid, in context
My first recorded rapid game was on January 10, 2024, at 631. The first 656 games contain 289 wins, 348 losses and 19 draws. Those totals matter alongside the milestone: this was not an uninterrupted run of victories. The earlier first crossing of 1000 came in game 232. Another 424 games separated the two thresholds.
Immediately before this game, the sequence was more positive. Game 651 had ended in a loss at 1063. I then won games 652 through 656, reaching 1072, 1080, 1088, 1096 and 1104. This was the fifth consecutive win in that stretch. The weekly diary places those games alongside the other results from the same week.
| Game detail | Recorded fact |
|---|---|
| Date | July 4, 2024 |
| Opponent | wahoo82, 1082 |
| My colour | Black |
| Recorded rating | 1096 before this result, 1104 after |
| Time control | 10 minutes, no increment |
| Opening | Scotch Game, C45 |
| Result | Win by resignation after my 18th move |
| Engine accuracy | Black 94.1%, White 78.3% |
The rating numbers here are the values recorded across consecutive games. I use them to describe this history, not to predict how many games another player should need. The position lessons are more transferable than the timetable.
Position one: a developing move with a threat
On my fourth move, White already had a knight on g5. I moved my own knight from g8 to h6. The saved analysis calls this a mistake: the evaluation changed from -1.81 to -0.20. These numbers are from White's perspective, so the negative sign favours my side, Black. My move reduced a clear advantage to something much closer to equality.
Stockfish preferred moving the bishop from f8 to e7. The verified description is particularly simple: it attacks the knight on g5. That gives me a concrete reason for developing the bishop. I can compare two moves by asking what each one does immediately, rather than remembering a slogan about where knights belong.
The saved engine continuation brings White's knight back, develops Black's other knight and then prepares castling. That is an analysis line, not a claim about the moves we actually played. Its value is to show a coherent alternative: get a piece out while making the advanced white knight respond.
My review note from this position is a question: can I develop something and attack something at the same time? The bishop move answers both parts. My knight move was legal and the game continued, but the engine gives me a more purposeful candidate to examine next time this exact shape appears.
Position two: take the knight that came forward
By move seven, White's knight had arrived on f7. I captured it with my knight from h6. This time the move I played and the engine's recommendation agree. The stored evaluation was -6.33 before the capture and -6.33 afterwards.
There is no need to describe this as a mysterious combination. The first action is a knight taking another knight. The engine line then shows White's bishop capturing on f7 with check and my king taking that bishop. A check is an attack on the king that must be answered; the capture shown in the continuation is the engine's answer here.
For my review, the important contrast with move four is specificity. Earlier I missed a developing move that attacked a knight. Here I correctly removed a knight that had reached my side of the board. I want to preserve that successful decision as well as catalogue the mistake. A review made entirely of red marks would miss what kept this game under control.
This board also stops me making an inaccurate general rule from the result. The knight on h6 participated in a good capture later, but that does not make the fourth move best retroactively. Each decision has its own alternatives and its own evaluation.
Position three: the queen takes a rook
On move sixteen I captured White's rook on a1 with my queen. The engine again agrees with the move. The saved evaluation changes from -8.36 to -8.53, preserving a decisive advantage for Black.
The position checker identifies more than the rook capture. From a1, my queen attacks the bishop on c1, with the other rook behind it on f1, and also attacks the undefended pawn on a2. Those are concrete targets visible in the verified board. They help explain why the capture is useful beyond simply adding up the material taken.
The actual game continued with White moving a knight to f3, my queen taking the a2 pawn, White developing the bishop to d2 and my a8 rook moving to b8. White then resigned. I do not need to append an imagined checkmate. The recorded finish is resignation with a large engine advantage and more than seven minutes left on my clock after the final move.
What this milestone teaches me
The most useful lesson is to keep a successful result separate from an assessment of every move. My fourth move lost much of an opening advantage. My seventh and sixteenth moves matched the engine's choices. All three facts belong in the same account. The high accuracy number describes the game overall; it does not erase the one moment that deserves work.
I can turn the three boards into a short review exercise. At the first, compare development with a direct threat. At the second, name the piece that can be captured and inspect the check in the reply. At the third, list what the queen attacks after taking the rook. That sequence makes the review about decisions I can actually recognise, not about celebrating a number on a profile.
For a fuller explanation of the evaluation signs, I use the Stockfish analysis guide. It helps keep a minus score from being mistaken for bad news when I am playing Black.
What happened after the crossing
I won game 657 and reached 1112. The next two results were losses, leaving me at 1105 and then 1098. Game 660 was a win at 1106. So this first crossing was followed almost immediately by another trip below the line. The data supports that fluctuation; it does not support a story that I had permanently solved this rating range.
I keep game 656 as a record of a good performance with a specific early correction attached. The complete journey contains the less tidy results around it. You can also replay the original game on Chess.com and compare the actual continuation with the alternatives on these boards.
Frequently asked questions
How many games did reaching 1100 take me?
My recorded history first reached 1100 after game 656, when my rating read 1104 on July 4, 2024.
Was game 656 flawless?
No. Stockfish recorded one mistake, no blunders and 94.1% accuracy for my play with Black.
Did I remain above 1100 immediately?
No. I reached 1112 in the next game, then fell to 1105 and 1098 in two losses.