What's costing ▚▚▙♥︎╱╯ games

100 rapid games on chess.com · Mar 16, 2026 to Nov 7, 2026 · average rating 1750 vs opponents 1736
An example report: everyone in it goes by a made-up name, the same one for the same player all through, and the games aren't linked to chess.com.
64-30-6
won / lost / drawn
81%
average accuracy
2.2
serious mistakes per game
1.1
of which blunders
34%
of ▚▚▙♥︎╱╯'s mistakes went unpunished

The short version

▚▚▙♥︎╱╯'s pre-move check

Not a calculation routine. These are the few questions that would have caught most of ▚▚▙♥︎╱╯'s costly mistakes, built from ▚▚▙♥︎╱╯'s own games.

  1. After each opponent move, also scan what they just left loose: the checks and captures on offer, and their unguarded pieces.
  2. Before letting go of a piece: is it protected where it lands, and what was it guarding where it stood?
  3. When something is free, spend ten seconds on why. Look at their best reply to taking it.
  4. Before trading, ask whose piece is better and which endgame the trade heads into. Trade freely when ahead, carefully when not.

What separates ▚▚▙♥︎╱╯ from the next level

Stockfish says what was best. It can't say what a stronger person would have done, and most of the best moves it finds aren't ones people at any club level find. Maia-2, a model of how people move at each rating, can. Here each of ▚▚▙♥︎╱╯'s mistakes is set against how likely a player about 300 points stronger would have been to make it, in the same position.

Of what ▚▚▙♥︎╱╯'s mistakes cost, a player about 300 points stronger would have avoided about 22%, and one about 500 stronger 31%. Most of these mistakes are ones stronger players make too, in the same positions. What they've learnt is narrower, and it's where to start:

Blind spotMistakesAvoided 300 points up
Pawn moves that weakened the position28 34%
Trades that helped the opponent19 32%
Not answering what their last move threatened17 24%
Letting winning positions go38 24%
Passive or misplaced piece moves50 20%
Endgame technique31 20%
Taking material that was bait15 19%
Not punishing the opponent's mistakes47 15%

Near the bottom: not punishing the opponent's mistakes. Stronger players still make these nearly as often, so they're the slower ones to improve.

Which level ▚▚▙♥︎╱╯'s moves look like

▚▚▙♥︎╱╯'s moves are most like those of a player rated about 1,430 on chess.com, against the 1,750 ▚▚▙♥︎╱╯ was rated on average in these games. That's which moves are chosen, not how well: a player's moves can be ahead of their results, or behind them.

Maia-2's ratings are lichess's. They're put on chess.com's scale by ▚▚▙♥︎╱╯'s opponents: the level their moves look like, against the ratings they had.

~1,590
in the opening
~1,470
in the middlegame
~1,530
in the endgame

The opening is clearly ahead of the middlegame: the middlegame is where ▚▚▙♥︎╱╯'s play looks most like a lower-rated player's.

Where the next level would have played differently

Mistakes that are common at ▚▚▙♥︎╱╯'s level and much rarer 300 points up.

10.Qxf6 vs ○▞▜♥︎▌▐ (1709) · Jul 10, 2026 · took 8 s
▚▚▙♥︎╱╯ played Qxf6; Qg3 was better.
Their best reply: 10...Nxf6 11.f4 Bb4 12.e5 Nfd7 13.Ne2. They found it.

Nothing tactical, but Qg3 kept a much better position. ▚▚▙♥︎╱╯'s win chance went from 55% to 39%.

A player about 300 points stronger would most often have played Qg3 (40% of the time). Qxf6 is a 40% choice at ▚▚▙♥︎╱╯'s level, and 15% for them.

16.Nf7+ vs π╯▄◢╲▛ (1807) · Oct 8, 2026 · took 4 s
▚▚▙♥︎╱╯ played Nf7+; Qh4# was better.
Their best reply: 16...Kh7 17.Qd3 Qh4 18.bxc3 Ne5 19.Ng5+. They found it.

Qh4# was available (16.Qh4#), and was missed. ▚▚▙♥︎╱╯'s win chance went from 100% to 84%.

A player about 300 points stronger would most often have played Qh4# (71% of the time). Nf7+ is a 31% choice at ▚▚▙♥︎╱╯'s level, and 23% for them.

17.Nxf6+ vs ▚▐▝▒○╮ (1788) · Sep 28, 2026 · took 6 s
▚▚▙♥︎╱╯ played Nxf6+; Bc5 was better.
Their best reply: 17...Qxf6 18.Bd4 Qxf4+ 19.Kb1 Rae8 20.Rhe1.

17...Qxf6 recaptures, and the exchange loses material: the knight on f6 wasn't safe there. ▚▚▙♥︎╱╯'s win chance went from 74% to 49%.

A player about 300 points stronger would most often have played Bc5 (57% of the time). Nxf6+ is a 33% choice at ▚▚▙♥︎╱╯'s level, and 23% for them.

▚▚▙♥︎╱╯'s 100 games from Mar 16, 2026 to Nov 7, 2026, oldest on the left. Single games swing a lot, so each chart compares the earlier 50 games with the latest 50, and only calls it a change when the gap is bigger than game-to-game luck would explain.

average of the last 10 gamesearlier and latest halfopponentsone game (hover for details, click to step through)

Accuracy by phase of the game

Each game is split into the opening (the first 10 moves), the middlegame, and the endgame, once most of the pieces are off. Accuracy isn't comparable from one phase to the next: openings are mostly familiar moves, and many endgames are already won or lost, where few moves change the result. So the fair test is ▚▚▙♥︎╱╯'s accuracy against the opponents' in the same games. A game counts toward a phase once both sides had made 3 moves in it, in proportion to how many moves ▚▚▙♥︎╱╯ made there.

PhaseGames▚▚▙♥︎╱╯OpponentsDifference
Opening10083.7%83.5%+0.2within luck
Middlegame9476.6%73.9%+2.7could be luck, 1 in 6
Endgame3187.1%87.0%+0.2within luck

In every phase ▚▚▙♥︎╱╯ plays about as accurately as the opponents in the same games, so no one phase stands out: the mistakes are spread through the game.

average of the last 10 gamesearlier and latest halfopponents

Does the time of day matter?

▚▚▙♥︎╱╯'s games split by when they started, in the time zone this report was made for (America/Toronto). Games before 4am count as the night before. Accuracy is the steadiest guide: results and rating also depend on who ▚▚▙♥︎╱╯ was paired with.

Later in the day, ▚▚▙♥︎╱╯'s accuracy rises from about 80% in games around 6am to 81% around 3pm. That's well within luck: no real difference.

Game after game, ▚▚▙♥︎╱╯'s accuracy drops from about 84% in the first game of the day to 74% by the 5th. Luck alone would make a change that big less than 1 time in 20, so it's real.

GamesAccuracyVs other gamesScoreRating
Time of day
Morning (4am to noon)7881%+1.065%+194
Afternoon (noon to 5pm)1376%−4.773%+52
Late (9pm to 4am)985%+4.478%+50
Day of the week
Monday1177%−4.264%+22
Tuesday1380%−0.265%+41
Wednesday1372%−9.377%+67
Thursday2086%+6.672%+89
Friday2280%−0.368%+68
Saturday1382%+1.458%+1
Sunday885%+4.356%+8
Games into the day
First game of the day4883%+4.970%+156
2nd or 3rd3381%+1.374%+143
4th to 6th1473%−8.536%−27
7th to 10th571%too few games80%+24
accuracy there, against the other gameshow far luck alone could move it. A row in bold is clearly different; rows under 8 games aren't judged. Score counts a win as 1 and a draw as ½; rating is the points won or lost over those games.

Tactical blind spots: one move that turns the game

Recurring kinds of tactical mistakes, ranked by what they cost in practice: the score they took off ▚▚▙♥︎╱╯, against opponents of the level ▚▚▙♥︎╱╯ meets, who don't see everything (1.0 ≈ one game's worth). The engine's count, as if every mistake were punished, is beside it. A mistake can appear under more than one heading.

On the boards:the move played (the deeper the red, the worse)a better movetheir best reply

Not punishing the opponent's mistakes

47 times in 34 games · cost ≈ 5.2 games' worth in practice (10.3 by the engine's count)

The opponent left something hanging or allowed a tactic, and the next move played on without taking it.

The 2-second check: After each opponent move, also scan what they just left loose: the checks and captures on offer, and their unguarded pieces.

Practise on lichess: Seize the advantage Hanging pieces

18...Nd4 vs ▛╳▒▞♣︎▟ (1889) · Oct 14, 2026 · took 16 s
▚▚▙♥︎╱╯ played Nd4; Rxd2 (or Qxd2) was better.
Their best reply: 19.Bd3 Nxc2 20.Qxh5 Be6 21.Bxc2 Rxd2.

Rxd2 was available (18...Rxd2 19.Bc4 Rxd1 20.Bxf7+ Kg7 21.Raxd1), and was missed. ▚▚▙♥︎╱╯'s win chance went from 93% to 13%.

18...Qf6 vs ◣♠︎▘▛◤╭ (1686) · Mar 19, 2026 · took 24 s
▚▚▙♥︎╱╯ played Qf6; Nxg2 (or Nd3) was better.
Their best reply: 19.d4 Bd6. They found it.

Nxg2 was available (18...Nxg2 19.d4 exd3 20.Kh1 Rg6 21.Qf5), and was missed. ▚▚▙♥︎╱╯'s win chance went from 95% to 38%.

8...O-O vs ▌▌╲▟♠︎▟ (1738) · Sep 23, 2026 · took 5 s
▚▚▙♥︎╱╯ played O-O; Qxd5 was better.
Their best reply: 9.Nxf6+ gxf6.

Qxd5 was available (8...Qxd5 9.Qxd5 Nxd5 10.O-O-O Nc7 11.Bh4), and was missed. ▚▚▙♥︎╱╯'s win chance went from 89% to 42%.

Leaving pieces unprotected

12 times in 12 games · cost ≈ 3.1 games' worth in practice (6.6 by the engine's count)

A move put a piece on a square it couldn't hold, walked away from a piece it was guarding, or opened a line, and the opponent simply took material.

Piece moved: knight 50%, bishop 25%, queen 8%.

The 2-second check: Before letting go of a piece: is it protected where it lands, and what was it guarding where it stood?

Practise on lichess: Hanging pieces

19...Qc4 vs ♠︎▄╱♣︎╲╰ (1890) · Oct 16, 2026 · took 8 s
▚▚▙♥︎╱╯ played Qc4; Qc6 (or Qf5) was better.
Their best reply: 20.Qxc4 g5 21.Bg3 Kg7 22.Be5 Bd6. They found it.

20.Qxc4 wins the queen on c4: it moved to a square it couldn't hold. ▚▚▙♥︎╱╯'s win chance went from 92% to 4%.

20.Ne7+ vs ▞♣︎▒╯╳π (1942) · Nov 7, 2026 · took 5 s
▚▚▙♥︎╱╯ played Ne7+; Nf6+ was better.
Their best reply: 20...Bxe7 21.Qxc8 Raxc8 22.Re1 Bc5+ 23.Kf1. They found it.

20...Bxe7 wins the knight on e7: it moved to a square it couldn't hold. ▚▚▙♥︎╱╯'s win chance went from 74% to 9%.

9...Nxe4 vs ◣▐▄♦︎◤▚ (1660) · Mar 17, 2026 · took 14 s
▚▚▙♥︎╱╯ played Nxe4; exd4 (or Qa5) was better.
Their best reply: 10.Bxd8 Rxd8 11.Bb3 Nb6 12.Nd2 a5. They found it.

The move opened the line for 10.Bxd8, which wins the queen on d8. ▚▚▙♥︎╱╯'s win chance went from 65% to 6%.

Taking material that was bait

15 times in 15 games · cost ≈ 2.9 games' worth in practice (4.8 by the engine's count)

Something that looked free was captured, and the capture walked into a tactic.

The 2-second check: When something is free, spend ten seconds on why. Look at their best reply to taking it.

Practise on lichess: Deflection Attraction

9...Nxe4 vs ◣▐▄♦︎◤▚ (1660) · Mar 17, 2026 · took 14 s
▚▚▙♥︎╱╯ played Nxe4; exd4 (or Qa5) was better.
Their best reply: 10.Bxd8 Rxd8 11.Bb3 Nb6 12.Nd2 a5. They found it.

The move opened the line for 10.Bxd8, which wins the queen on d8. ▚▚▙♥︎╱╯'s win chance went from 65% to 6%.

8.Bxb5 vs ♣︎▝╲▞◥▝ (1630) · Mar 20, 2026 · took 4 s
▚▚▙♥︎╱╯ played Bxb5; h4 (or Bd3) was better.
Their best reply: 8...Qa5+ 9.c3 Qxb5 10.a4 Qc4 11.h4. They found it.

8...Qa5+ forks the king and bishop. ▚▚▙♥︎╱╯'s win chance went from 62% to 13%.

17.Bxd4 vs ▀╯◢▟▞♥︎ (1632) · Mar 17, 2026 · took 2 s
▚▚▙♥︎╱╯ played Bxd4; Qxd4 was better.
Their best reply: 17...Rd8 18.h4 c5 19.Nb5 Qb6 20.Bf2. They found it.

17...Rd8 pins the bishop to the queen. ▚▚▙♥︎╱╯'s win chance went from 60% to 14%.

Forks: one piece hitting two at once

13 times in 13 games · cost ≈ 2.3 games' worth in practice (5.5 by the engine's count)

The punishment was a double attack, most often a knight or queen landing on a square that hits two pieces at once (or the king and a piece).

Punishing moves included 5 knight moves, 3 long-diagonal moves, 2 backward moves.

The 2-second check: Glance at the squares their knights and queen can reach next move. If one of them would hit two pieces at once, or the king and a piece, deal with it now.

Practise on lichess: Forks

17.Nh4 vs ◥♥︎●▛◢▐ (1751) · Sep 25, 2026 · took 16 s
▚▚▙♥︎╱╯ played Nh4; Rg2 (or Qe2) was better.
Their best reply: 17...Qxf2#.

17...Qxf2# forks the king, rook and knight. ▚▚▙♥︎╱╯'s win chance went from 84% to 0%.

8.Bxb5 vs ♣︎▝╲▞◥▝ (1630) · Mar 20, 2026 · took 4 s
▚▚▙♥︎╱╯ played Bxb5; h4 (or Bd3) was better.
Their best reply: 8...Qa5+ 9.c3 Qxb5 10.a4 Qc4 11.h4. They found it.

8...Qa5+ forks the king and bishop. ▚▚▙♥︎╱╯'s win chance went from 62% to 13%.

15.Kh3 vs ♣︎▖◢▜♠︎╯ (1692) · Mar 22, 2026 · took 2 s
▚▚▙♥︎╱╯ played Kh3; Kg3 was better.
Their best reply: 15...Nxf2+ 16.Kg3 Nxd3 17.cxd3 Kg8 18.Rf1. They found it.

15...Nxf2+ forks the king and queen. ▚▚▙♥︎╱╯'s win chance went from 52% to 4%.

Also seen

PatternTimesGamesCost in practiceEngine's count
Not answering what their last move threatened
The opponent's previous move set up a threat (to win material or to mate), and the reply didn't deal with it. That isn't being out-calculated: the threat was already on the board.
17152.25.9
Recapturing on autopilot
After a capture, the piece was taken back automatically, when an in-between move, a different recapture or a bigger capture was much better, or the recapture itself walked into trouble.
11112.03.0
Quiet moves not seen coming
The move that punished it was not a check or capture. It was a quiet move that set up an unstoppable threat. These are the hardest to see because nothing looks forcing.
11110.74.1
Walking into attacks on the king
The move allowed a forced mate or a mating attack.
220.51.4
Pins, skewers and discovered attacks
Pieces were lined up on a file, rank or diagonal with an enemy rook, bishop or queen behind or in front, and the opponent used the line.
440.41.4
Pieces getting trapped
A piece ended up with no safe squares and was rounded up.
22-0.00.6

Positional habits: the slow-burn kind

Mistakes where nothing hangs, but the position turns. These build the 'no-win situation' that only shows once it's too late.

On the boards:the move played (the deeper the red, the worse)a better movetheir best reply

Letting winning positions go

38 times in 29 games · cost ≈ 9.1 games' worth in practice (17.1 by the engine's count)

The position was clearly winning (75%+), and a single move gave a big part of it back.

Piece moved: bishop 21%, knight 21%, pawn 18%.

The 2-second check: When winning, switch to safety mode: check their checks, captures and threats before every move, trade pieces, and don't hurry.
28.Rd6 vs ▟╭▜▙╲◣ (1926) · Oct 14, 2026 · took 3 s
▚▚▙♥︎╱╯ played Rd6; Rxd8 was better.
Their best reply: 28...Qc5+ 29.Kf1 Qxd6 30.Qe4+ f5 31.Qe7+. They found it.

28...Qc5+ 29.Kf1 Qxd6 30.Qe4+ f5 31.Qe7+ wins material. ▚▚▙♥︎╱╯'s win chance went from 97% to 6%.

19...Qc4 vs ♠︎▄╱♣︎╲╰ (1890) · Oct 16, 2026 · took 8 s
▚▚▙♥︎╱╯ played Qc4; Qc6 (or Qf5) was better.
Their best reply: 20.Qxc4 g5 21.Bg3 Kg7 22.Be5 Bd6. They found it.

20.Qxc4 wins the queen on c4: it moved to a square it couldn't hold. ▚▚▙♥︎╱╯'s win chance went from 92% to 4%.

17.Nh4 vs ◥♥︎●▛◢▐ (1751) · Sep 25, 2026 · took 16 s
▚▚▙♥︎╱╯ played Nh4; Rg2 (or Qe2) was better.
Their best reply: 17...Qxf2#.

17...Qxf2# forks the king, rook and knight. ▚▚▙♥︎╱╯'s win chance went from 84% to 0%.

Endgame technique

31 times in 14 games · cost ≈ 3.7 games' worth in practice (7.9 by the engine's count)

Serious mistakes once most pieces were traded.

The 2-second check: In endgames, activate the king and push passed pawns. Calculate pawn races to the end.

Practise on lichess: Endgames Rook endgames

44.Be4 vs ▟◥●▀▝╰ (1691) · Mar 20, 2026 · took 6 s
▚▚▙♥︎╱╯ played Be4; Bd3+ was better.
Their best reply: 44...Rxd6 45.Bh7 Kb5 46.Kg3 Kxb4 47.h4. They found it.

The bishop on d6 was already under attack; 44...Rxd6 takes it. The threat already on the board was Rxd6. ▚▚▙♥︎╱╯'s win chance went from 86% to 14%.

34...Be2+ vs ╳╱▛▝▘▄ (1879) · Oct 31, 2026 · took 30 s
▚▚▙♥︎╱╯ played Be2+; Rh2 (or Rc2) was better.
Their best reply: 35.Kxg2 Kg7 36.b3 Bd3 37.e4 Bb1. They found it.

The bishop on f3 was guarding the rook on g2; once it moved, 35.Kxg2 took it. ▚▚▙♥︎╱╯'s win chance went from 96% to 50%.

37.Ke3 vs ▘♠︎◥▞▙◢ (1655) · Mar 16, 2026 · took 0 s
▚▚▙♥︎╱╯ played Ke3; Kf3 (or Ke2) was better.
Their best reply: 37...Ke5 38.Kf2 Kd4 39.Ke2 Kc3 40.Ke3. They found it.

Nothing tactical, but Kf3 kept a much better position. ▚▚▙♥︎╱╯'s win chance went from 50% to 7%.

Passive or misplaced piece moves

50 times in 42 games · cost ≈ 2.3 games' worth in practice (9.3 by the engine's count)

Knight, bishop, rook and king moves that didn't hang anything but handed over the initiative: retreats to passive squares, a piece wandering away from the action, the king stepping into the open.

Piece moved: bishop 34%, knight 30%, rook 22%. 6 were retreats.

The 2-second check: When nothing tactical is happening, find the worst-placed piece and improve it. And before choosing, ask what the opponent wants to do next.
37.Ke3 vs ▘♠︎◥▞▙◢ (1655) · Mar 16, 2026 · took 0 s
▚▚▙♥︎╱╯ played Ke3; Kf3 (or Ke2) was better.
Their best reply: 37...Ke5 38.Kf2 Kd4 39.Ke2 Kc3 40.Ke3. They found it.

Nothing tactical, but Kf3 kept a much better position. ▚▚▙♥︎╱╯'s win chance went from 50% to 7%.

32.Kf1 vs ♥︎▟╲♦︎◣▄ (1675) · Mar 19, 2026 · took 2 s
▚▚▙♥︎╱╯ played Kf1; Kh1 was better.
Their best reply: 32...Rbf2+ 33.Ke1 Rh2 34.Rcc6 Rb2 35.Rxf6+. They found it.

Nothing tactical, but Kh1 kept a much better position. ▚▚▙♥︎╱╯'s win chance went from 50% to 14%.

55.Kg4 vs ♦︎▛▖π♠︎▚ (1708) · Jul 18, 2026 · took 7 s
▚▚▙♥︎╱╯ played Kg4; Rd5+ was better.
Their best reply: 55...Rc3 56.Rf5 Rxc2 57.Rxf6+ Ke5 58.Rxf4. They found it.

Nothing tactical, but Rd5+ kept a much better position. ▚▚▙♥︎╱╯'s win chance went from 50% to 19%.

Trades that helped the opponent

19 times in 19 games · cost ≈ 2.2 games' worth in practice (4.2 by the engine's count)

Exchanges started or offered that made things worse: a good piece swapped for the opponent's bad one, a trade into a lost endgame, or lines opened toward one's own king.

The 2-second check: Before trading, ask whose piece is better and which endgame the trade heads into. Trade freely when ahead, carefully when not.
21...Bxc3 vs ╳▜▟▄●▙ (1953) · Nov 7, 2026 · took 13 s
▚▚▙♥︎╱╯ played Bxc3; Rd8 (or Rb8) was better.
Their best reply: 22.Qxc3 Qxc3+. They found it.

Nothing tactical, but Rd8 kept a much better position. ▚▚▙♥︎╱╯'s win chance went from 97% to 31%.

17...Bxh3 vs ▚○◣▗╯▐ (1919) · Nov 7, 2026 · took 15 s
▚▚▙♥︎╱╯ played Bxh3; exd3 was better.
Their best reply: 18.gxh3 Qxh3 19.c4 Bxb2 20.Rxb2 b6. They found it.

Nothing tactical, but exd3 kept a much better position. ▚▚▙♥︎╱╯'s win chance went from 68% to 25%.

11.Bh6 vs ╮▖▜◢╳╮ (1819) · Oct 4, 2026 · took 36 s
▚▚▙♥︎╱╯ played Bh6; O-O-O (or g4) was better.
Their best reply: 11...Bxh6 12.Qxh6.

Nothing tactical, but O-O-O kept a much better position. ▚▚▙♥︎╱╯'s win chance went from 85% to 58%.

Also seen

PatternTimesGamesCost in practiceEngine's count
Pawn moves that weakened the position
Pawn moves that lost nothing right away but left holes behind, loosened the king's cover or fixed the pawn structure badly. Pawns can't move back, so the damage stays.
28221.85.4
Queen adventures
Queen moves that didn't hang anything but cost ground: the queen leaving the defence, going pawn-hunting, or landing where the opponent's pieces could chase her and develop with gain of time.
11111.02.6

Missed mates

Every time either side had a forced checkmate in 5 moves or fewer, and whether it was seen through. A mate played out move by move counts once, and as missed if it was let go at any step. The opponents play at ▚▚▙♥︎╱╯'s level, so their misses show which mates are easy to overlook: the ones to look for in ▚▚▙♥︎╱╯'s own games.

30 of 36
of ▚▚▙♥︎╱╯'s forced mates seen through
1 of 7
mates in 1 ▚▚▙♥︎╱╯ missed
2 of 8
mates opponents missed against ▚▚▙♥︎╱╯
5 s
▚▚▙♥︎╱╯'s median time on a move that missed a mate (6 s when one was found)

How often each side missed

Mate in▚▚▙♥︎╱╯ missedOpponents missed
11 of 7 (14%)1 of 3 (33%)
21 of 7 (14%)0 of 2 (0%)
32 of 4 (50%)–
41 of 4 (25%)1 of 2 (50%)
51 of 14 (7%)0 of 1 (0%)
Any6 of 36 (17%)2 of 8 (25%)

▚▚▙♥︎╱╯ and the opponents miss mates about as often as each other (within luck).

Which mates get missed

By how the mate starts, both sides together: one side alone has too few to tell. Checks are the moves everyone looks at first.

Starts withTimesMissedOther mates▚▚▙♥︎╱╯Opponents
a check3421%10%5 of 262 of 8
a capture20%19%0 of 20 of 0
a quiet move812%19%1 of 80 of 0

Bold rows are clear patterns, not noise.

Played instead of the mate: by ▚▚▙♥︎╱╯, a capture 2 times, a different check 1 time and something else 3 times; by the opponents, a capture 1 time and a different check 1 time.

▚▚▙♥︎╱╯'s missed mates

Of these 6, ▚▚▙♥︎╱╯ went on to lose 0 and still won 6. A game with two missed mates counts twice.

On the boards:the move playedthe mate ▚▚▙♥︎╱╯ had, and how it ends
16.Nf7+ vs π╯▄◢╲▛ (1807) · Oct 8, 2026 · took 4 s
▚▚▙♥︎╱╯ had mate in 1: 16.Qh4#. ▚▚▙♥︎╱╯ played 16.Nf7+, and still won.
The mate played out.
40...Rxd7+ vs ▀▒▌◢♠︎◤ (1831) · Oct 1, 2026 · took 5 s
▚▚▙♥︎╱╯ had mate in 5: 40...Qc5+ 41.Kd8 Re3 42.Rxg7+ Kxg7 43.f6+ Kf7 44.Kd7 Rd3#. ▚▚▙♥︎╱╯ played 40...Rxd7+, and still won.
The mate played out.
20.Be4 vs ▚▛╯▟◤▞ (475) · Sep 5, 2026 · took 6 s
▚▚▙♥︎╱╯ had mate in 2: 20.Nh5+ Kf8 21.Qxf7#. ▚▚▙♥︎╱╯ played 20.Be4, and still won.
The mate played out.
27.Rxh7 vs ♣︎▝╲▞◥▝ (1630) · Mar 20, 2026 · took 15 s
▚▚▙♥︎╱╯ had mate in 4: 27.Qb4+ d6 28.Qxd6+ Ke8 29.Rg8+ Qf8 30.Rxf8#. ▚▚▙♥︎╱╯ played 27.Rxh7, and still won.
The mate played out.
2 more
Mar 17, 2026 vs ◤▘▀◤╱▒
Mate in 5: 19.Ne4 Rg8 20.Nxf6+ Kd8 21.Nxg8 Ke8 22.Rh8 f5 23.Nh6#; ▚▚▙♥︎╱╯ played 19.Rde1, and still won
Mar 17, 2026 vs ◤▘▀◤╱▒
Mate in 3: 24.Rh8+ Ne8 25.Nd5 f5 26.Bc7#; ▚▚▙♥︎╱╯ played 24.Re1, and still won

Mates opponents missed against ▚▚▙♥︎╱╯

Of these 2, they went on to lose 1 and still won 1. A game with two missed mates counts twice.

On the boards:the move playedthe mate they had, and how it ends
41...Rd4+ vs ♥︎▟◥▘▌▟ (1901) · Oct 9, 2026 · took 11 s
♥︎▟◥▘▌▟ had mate in 5: 41...Qd4+ 42.Kc2 Rf2+ 43.Rd2 Rxd2+ 44.Kb3 Rxb2+ 45.Ka3 Qb4#. ♥︎▟◥▘▌▟ played 41...Rd4+, and still won.
The mate played out.
17...Qxh4 vs ◥♥︎●▛◢▐ (1751) · Sep 25, 2026 · took 8 s
◥♥︎●▛◢▐ had mate in 1: 17...Qxf2#. ◥♥︎●▛◢▐ played 17...Qxh4, and went on to lose.
The mate played out.

Sharp positions: where ▚▚▙♥︎╱╯'s mistakes are

A position is sharp when most moves in it lose: fewer than a quarter of the legal moves keep it (within 5 points of win chance of the best). Every position ▚▚▙♥︎╱╯ moved in after the opening, with the game still open, was searched move by move to tell. Mistakes aren't spread evenly: they come where there are few ways to get it right.

58%
of the positions were sharp
88%
of the mistakes came in them
15%
of moves there were mistakes
3%
of moves elsewhere

▚▚▙♥︎╱╯ took a median of 8 s on a sharp position, about the same as the 7 s on the others. That's where extra time would pay: nearly all the mistakes are there, and the rest of the moves could go quicker to make room for it.

▚▚▙♥︎╱╯ found one of the safe moves in 78% of the sharp positions. By Maia-2, a typical player at ▚▚▙♥︎╱╯'s level finds one about 56% of the time, and one about 300 points stronger 59%.

How to tell

The signs, visible at a glance, that most often went with a sharp position in ▚▚▙♥︎╱╯'s games:

SignPositionsSharp when it's thereOf all sharp positions
When the opponent's last move attacked one of ▚▚▙♥︎╱╯'s pieces27879%22%
When lots of pieces are attacking each other65075%47%

Between them, these flag 55% of ▚▚▙♥︎╱╯'s sharp positions, and a position with one of them is sharp 75% of the time, against 58% overall. When one is there, check each candidate move against the opponent's best reply before playing it.

When to slow down

Each row compares ▚▚▙♥︎╱╯'s mistake rate in a situation with the rate everywhere else. Bold rows are clear patterns, not noise. There's no need to calculate every move, only these. A high rate alone mostly says the situation is hard, for anyone. The last column takes that out: ▚▚▙♥︎╱╯'s mistakes there against those a player of the same level would be expected to make in the very same positions. Above 1× is worse than the level, below is better, and it's in bold when it's clear.

SituationMovesMistake rateOtherwiseRiskTime spentAgainst the level
When the opponent has a threat that isn't a direct attack on a piece15919%7% 2.7×6 s1.15×
When only one move holds the position25313%7% 1.8×4 s0.82×
When ▚▚▙♥︎╱╯'s king is still in the centre after move 1210313%8% 1.7×10 s1.21×
When lots of pieces are attacking each other81410%7% 1.4×9 s0.92×
When clearly winning71710%7% 1.4×7 s0.91×
When the opponent's last move attacked one of ▚▚▙♥︎╱╯'s pieces39110%7% 1.3×7 s1.02×
When two or more of ▚▚▙♥︎╱╯'s pieces are undefended15377%8% 0.9×4 s1.02×
Right after the opponent captures something6747%8% 0.9×4 s0.96×
With under a minute on the clock307%8% 0.9×4 s-
When three or more of the opponent's pieces aim at the area around ▚▚▙♥︎╱╯'s king166%8% 0.8×8 s-
When ahead in material3406%8% 0.8×8 s1.14×
In the endgame5216%8% 0.7×6 s0.86×
In the opening (moves 1-10)9896%9% 0.6×3 s1.12×
When behind in material4523%9% 0.4×5 s0.57×
When in check1222%8% 0.3×5 s0.51×

In the riskiest situation (when the opponent has a threat that isn't a direct attack on a piece), ▚▚▙♥︎╱╯ spends a median of 6 s per move, about the same as the 5 s spent otherwise.

Against players of the same level

The same comparison by the kind of move ▚▚▙♥︎╱╯ made and how long it took: in 1,772 positions searched move by move, ▚▚▙♥︎╱╯'s mistakes against those a typical player of the same level (by Maia-2) would make in them. Bold rows are clearly different from the level.

MovesMistake rateExpected at this levelAgainst the level
Kind of move
Moving a pawn40010%10%1.06×
Moving a knight28311%11%1.02×
Moving a bishop30814%11%1.27×
Moving a rook3645%8%0.66×
Moving the queen22610%11%0.95×
Moving the king1917%7%0.97×
Capturing3738%10%0.85×
Giving check1816%10%0.59×
Moving a piece back2409%9%1.01×
Time taken
Under 3 s2988%9%0.91×
3-10 s7769%9%1.02×
10-30 s55712%10%1.12×
30 s or more1417%11%0.62×

However long ▚▚▙♥︎╱╯ took, the mistakes came about as often as the positions would lead one to expect: longer thinks went to harder positions, and did about as well there as a typical player would.

How ▚▚▙♥︎╱╯'s games are lost

For every loss: the last moment the position was fine, the move that did the most damage after it, and whether the game went in one move or slipped away.

Kind of lossGamesWhat it means
One-move oversight9a single move lost the game, and their very next move took the material or mated
One move turned it, and it wasn't obvious16a single move swung the game, but the punishment took a combination or a quiet move to find
Several mistakes added up4no single move decided it: the position got worse over several moves until it was lost
Flagged in a playable position1ran out of time with the game still going

In the 20 losses that weren't simple oversights, the decisive position was an only-move situation 5 times, and the opponent already had a threat on the board 7 times. ▚▚▙♥︎╱╯ spent a median of 6 s on the move that decided it. These are the positions that felt normal but weren't.

Games where ▚▚▙♥︎╱╯ reached a winning position (80%+) and didn't win: 16.

Each loss

GameWin chanceKindDecisive move
vs ╳▜▟▄●▙ (1953)
Nov 7, 2026 · Indian Game · was winning
One move turned it, and it wasn't obvious21...Bxc3 97%→31% · 13 s
Better was Rd8.
vs ╳╱▛▝▘▄ (1879)
Oct 31, 2026 · Indian Game · was winning
One move turned it, and it wasn't obvious58...Bd7 49%→5% · 12 s
59.Re7+ forks the king and bishop.
vs ♠︎▄╱♣︎╲╰ (1890)
Oct 16, 2026 · French Defense · was winning
One-move oversight19...Qc4 92%→4% · 8 s
20.Qxc4 wins the queen on c4: it moved to a square it couldn't hold.
vs ◤◢▝○╲▘ (1907)
Oct 15, 2026 · Closed Sicilian Defense · was winning
Flagged in a playable position35.Qb8+ 86%→84% · 4 s
Better was Qd5.
vs ▟╭▜▙╲◣ (1926)
Oct 14, 2026 · Sicilian Defense · was winning
One move turned it, and it wasn't obvious28.Rd6 97%→6% · 3 s
28...Qc5+ 29.Kf1 Qxd6 30.Qe4+ f5 31.Qe7+ wins material.
vs ♥︎▟◥▘▌▟ (1901)
Oct 9, 2026 · Caro Kann Defense · was winning
One move turned it, and it wasn't obvious36.Qc6 56%→12% · 40 s
Better was Qb7+.
vs ▖╳╰╳▒▐ (1828)
Oct 2, 2026 · Birds Opening · was winning
One move turned it, and it wasn't obvious26...dxe4 63%→11% · 0 s
Better was Bxe4.
vs ▌●▐╭▟♦︎ (1878)
Sep 25, 2026 · French Defense
One move turned it, and it wasn't obvious13...Qa5 73%→16% · 4 s
14.Nb3 Bxf2+ 15.Rxf2 Qb4 16.Nc5 Bc8 wins material.
vs ▄▜╯▌◥╳ (1728)
Sep 20, 2026 · Vienna Game · was winning
Several mistakes added up18...Bd8 87%→78% · 34 s
Better was Be6.
It went over 1 moves: 18...Bd8 (−8)
vs ▄╭▌╲◢♣︎ (1742)
Sep 3, 2026 · Sicilian Defense
One-move oversight11.Be5 62%→5% · 6 s
11...Bxe5 wins the bishop on e5: it moved to a square it couldn't hold.
vs ▟▄╮π▖╳ (1755)
Sep 3, 2026 · Alapin Sicilian Defense
One-move oversight7...Ne4 49%→4% · 3 s
The move opened the line for 8.Bxd8, which wins the queen on d8.
vs ▒╰╭▖○╯ (1724)
Aug 22, 2026 · Alapin Sicilian Defense
One-move oversight14...Nh5 54%→9% · 17 s
The move opened the line for 15.Bxe7, which wins the bishop on e7.
vs ▄◤▀▒♣︎π (1760)
Aug 8, 2026 · Sicilian Defense
Several mistakes added up3...e6 46%→31% · 2 s
Better was cxd4.
It went over 4 moves: 3...e6 (−15), 4...exd5 (−5), 10...Nh5 (−5), 11...Bd7 (−13)
vs ○▛▜▖╯╰ (1769)
Aug 1, 2026 · Three Knights Opening · was winning
Several mistakes added up20.Rxa7 90%→89% · 2 s
Better was Qe4.
It went over 0 moves:
vs ╯▟╭▙▘▘ (1723)
Jul 21, 2026 · French Defense
One move turned it, and it wasn't obvious6...Qxd5 41%→22% · 3 s
Better was Qe7+.
vs ♦︎▛▖π♠︎▚ (1708)
Jul 18, 2026 · Caro Kann Defense · was winning
One move turned it, and it wasn't obvious55.Kg4 50%→19% · 7 s
Better was Rd5+.
vs ○▞▜♥︎▌▐ (1709)
Jul 10, 2026 · Caro Kann Defense
One-move oversight15.Bg5 38%→7% · 7 s
The bishop on e3 was guarding the knight on c5; once it moved, 15...Bxc5 took it.
vs ▟●♥︎♣︎◣▀ (1722)
Apr 5, 2026 · Pirc Defense
One move turned it, and it wasn't obvious19...Bc6 47%→5% · 12 s
20.e4 traps the queen on d5.
vs ╲▗◣●▜▘ (1693)
Mar 23, 2026 · Sicilian Defense
One move turned it, and it wasn't obvious18.g4 55%→24% · 8 s
Better was Re1.
vs ♣︎▖◢▜♠︎╯ (1692)
Mar 22, 2026 · Caro Kann Defense
One move turned it, and it wasn't obvious15.Kh3 52%→4% · 2 s
15...Nxf2+ forks the king and queen.
vs ▟◥●▀▝╰ (1691)
Mar 20, 2026 · Philidor Defense · was winning
One-move oversight44.Be4 86%→14% · 6 s
The bishop on d6 was already under attack; 44...Rxd6 takes it.
vs ◣♠︎▘▛◤╭ (1686)
Mar 19, 2026 · Italian Game · was winning
One move turned it, and it wasn't obvious18...Qf6 95%→38% · 24 s
Better was Nxg2.
vs ♥︎▒╱▒╳▐ (1672)
Mar 18, 2026 · Van t Kruijs Opening
One-move oversight4...Nf6 56%→0% · 2 s
5.Qxf7# is checkmate.
vs ▐▛╯▜▄◥ (1719)
Mar 18, 2026 · Giuoco Piano Game
One move turned it, and it wasn't obvious11.Bxf7+ 35%→8% · 14 s
11...Rxf7 recaptures, and the exchange loses material: the bishop on f7 wasn't safe there.
vs π●▚╳▘◢ (1666)
Mar 17, 2026 · Reti Opening
Several mistakes added up12.Ne2 30%→4% · 3 s
The knight on g5 was already under attack; 12...Qxg5 takes it.
It went over 4 moves: 4.O-O (−9), 6.b3 (−8), 10.Ng5 (−8), 12.Ne2 (−26)
vs ▝◤▞▛╯π (1683)
Mar 17, 2026 · Kings Gambit
One move turned it, and it wasn't obvious14...Bb6 39%→16% · 8 s
Better was Rad8.
vs ◣▐▄♦︎◤▚ (1660)
Mar 17, 2026 · Pirc Defense
One-move oversight9...Nxe4 65%→6% · 14 s
The move opened the line for 10.Bxd8, which wins the queen on d8.
vs ▘♠︎◥▞▙◢ (1655)
Mar 16, 2026 · Vienna Game
One move turned it, and it wasn't obvious37.Ke3 50%→7% · 0 s
Better was Kf3.
vs ▟▖♠︎╳♣︎╲ (1661)
Mar 16, 2026 · Vienna Game · was winning
One-move oversight12.Kg1 77%→23% · 1 s
12...gxf3 wins the knight on f3, which the move left without enough protection.
vs ▜◣▌╰╰○ (1705)
Mar 16, 2026 · French Defense · was winning
One move turned it, and it wasn't obvious14.Rfe1 59%→11% · 6 s
14...Bxf2+ forks the king and rook.

Did ▚▚▙♥︎╱╯'s opponents use an engine?

Two kinds of evidence. First, whether chess.com has closed the opponent's account for fair-play violations. Second, how often they played Stockfish's first choice in positions that were still undecided. High accuracy on its own means little: once one side has blundered, almost any move wins for the other, so those moves aren't counted.

1
opponent closed for fair play
0
games with engine-like play
54 of 100
games long enough to judge (15+ undecided moves)
36%
how often ▚▚▙♥︎╱╯'s opponents play the top move

Games to skip

GameEvidenceTop moveTheir mistakes
vs ╲▖▝▟▀▒ (1721)
Mar 16, 2026 · ▚▚▙♥︎╱╯ won
Account closed for fair-play violations. In this game they played the top move 53% of the time (34% typical)53% of 363

▚▚▙♥︎╱╯'s most engine-like opponents

For comparison: the unflagged games where the opponent played the top move most often, against what a typical opponent of ▚▚▙♥︎╱╯'s would have managed in the same positions.

GameTypicalTop moveTheir mistakes
vs ♦︎▛▖π♠︎▚ (1708)
Jul 18, 2026 · ▚▚▙♥︎╱╯ lost
34%50% of 482
vs ▟╭▜▙╲◣ (1926)
Oct 14, 2026 · ▚▚▙♥︎╱╯ lost
37%59% of 222
vs ○▐♥︎▜╱╮ (1681)
Jul 21, 2026 · ▚▚▙♥︎╱╯ won
34%52% of 231
vs ▟╭π▗╭▌ (1667)
Mar 18, 2026 · ▚▚▙♥︎╱╯ won
35%50% of 202
vs ▟◥●▀▝╰ (1691)
Mar 20, 2026 · ▚▚▙♥︎╱╯ lost
35%45% of 316

▚▚▙♥︎╱╯'s most engine-like games

The same test on ▚▚▙♥︎╱╯'s own moves: the games where ▚▚▙♥︎╱╯ played the top move most often, against the same typical opponent in the same positions. How far these games stray from typical shows how far an opponent's can without an engine.

GameTypicalTop moveMistakes
vs ▙◥╱♣︎╯▗ (1722) would be flagged
Sep 22, 2026 · ▚▚▙♥︎╱╯ won
37%71% of 514
vs ▟╱▒◣╮▟ (1821) would be flagged
Oct 4, 2026 · ▚▚▙♥︎╱╯ won
42%94% of 160
vs ▛◣▌◤▖▙ (1695) would be flagged
Jul 23, 2026 · ▚▚▙♥︎╱╯ won
38%72% of 291
vs ▝▀▘▞○╲ (1701) would be flagged
Jul 24, 2026 · ▚▚▙♥︎╱╯ won
36%80% of 150
vs ╳╱▛▝▘▄ (1879)
Oct 31, 2026 · ▚▚▙♥︎╱╯ lost
34%60% of 423

By the same test, 5 of ▚▚▙♥︎╱╯'s 55 games long enough to judge would be flagged too. ▚▚▙♥︎╱╯'s most engine-like opponent who wasn't flagged, ♦︎▛▖π♠︎▚ (50% of 48), would rank 17th among them.

Players at ▚▚▙♥︎╱╯'s level pick the engine's first choice about 36% of the time in undecided positions. ▚▚▙♥︎╱╯ plays it 52% of the time. Someone copying an engine agrees with it 55–77% of the time, depending on how strong an engine they use. A game is flagged when the opponent reaches 60% over 15+ moves and that is far beyond chance. Someone who only uses an engine for a few key moves won't show up in a single game. If you're suspicious, report them on chess.com: its fair-play team looks at all of a player's games. Accounts are often closed weeks later, so each run checks them again.

▚▚▙♥︎╱╯'s clock

Playing fast is fine. The problem is spending the same few seconds on a sharp position as on a quiet one.

6 s
median time per move
6 s
on sharp moves (threat or only-move)
6 s
on calm moves
7:49
on the clock when a lost game turned
3
losses on time
Time on the moveShare of movesMistake rateIn a sharp position
under 3 s23%7%30%
3-10 s43%9%22%
10-30 s27%11%26%
30 s or more7%7%27%

Sharp: they had a threat on the board, or only one move held. ▚▚▙♥︎╱╯'s long moves are in sharp positions no more often than the quick ones (26% of the moves over 10 s, against 24% of quicker ones), so the extra time isn't following the position. Long moves like that are often time away from the board rather than thinking, so more mistakes on slow moves doesn't mean thinking hurts. The risky move is the one made on coming back, before the opponent's last move has sunk in: look at it before playing.

How hard were the tactics that hurt ▚▚▙♥︎╱╯?

For each of ▚▚▙♥︎╱╯'s 65 tactical mistakes: how many moves the opponent needed before the material was gone or the mate landed.

Their very next move
Material was simply taken, or it was mate in one. A quick safety glance before moving catches these.
3655%
Two moves deep
A threat, then the capture: a fork, a pin, a trapped piece, mate in two. Pattern practice makes these jump out.
2031%
Three or more moves
A real combination. Even strong players miss these, so they're the least worrying kind.
914%

Which threats ▚▚▙♥︎╱╯ misses

Every time the opponent already had a real threat on the board (to win material or mate), did ▚▚▙♥︎╱╯ deal with it? Here that's split by the shape of the threat. If one shape gets missed far more often than the rest, that's a blind spot in how ▚▚▙♥︎╱╯ scans the board.

Kind of threatTimesMissedOther threatsRatio
Long-diagonal threats (bishop or queen from 3+ squares away)3017%3% 5.8×
Quiet threats (the threatened move isn't a capture or check)303%4% 0.9×
Knight threats852%4% 0.6×
Threats from a backward move430%4% 0.0×

Bold rows are clear patterns, not noise: bigger than game-to-game luck would explain, allowing for how many shapes are compared.

Knights or bishops

Trading a knight for a bishop, or a bishop for a knight, comes up in most games. Which of ▚▚▙♥︎╱╯'s does more, and which of the opponents' does more damage?

KnightsBishops
▚▚▙♥︎╱╯'s knights and bishops
Mistakes per 100 moves with itEvery real decision made moving one.8.5566 moves10.7457 moves
Winning shots it had, and ▚▚▙♥︎╱╯ tookAfter the opponent's mistake, the best move won material or mated, with this piece doing it.9 of 1182%10 of 10100%
The opponents'
Times theirs won material from ▚▚▙♥︎╱╯Per 100 moves ▚▚▙♥︎╱╯ made facing one.0.511 times0.716 times
Their threats with it that ▚▚▙♥︎╱╯ missedThreats to win material or mate.2 of 852%5 of 658%
Trades
Trades ▚▚▙♥︎╱╯ started giving it up, that were mistakesA knight for their bishop, or a bishop for their knight. ▚▚▙♥︎╱╯'s other moves: 8%.0 of 160%1 of 254%
With it against their other one, ▚▚▙♥︎╱╯'s scoreGames where that lasted 6 or more of ▚▚▙♥︎╱╯'s moves, against the win chance when it began.92% from 70%6 games48% from 55%26 games

Bold rows are clear differences between knights and bishops, not noise, and a bold trade goes wrong clearly more often than ▚▚▙♥︎╱╯'s other moves. A shot, or material lost, is put down to the piece that makes the fork, pin, skewer or discovered attack, or else takes the material.

Openings

▚▚▙♥︎╱╯'s score in each opening, counting a win as 1 and a draw as ½, and the average win chance after move 10. Below about 40% after move 10 means leaving the opening worse off than at the start.

By name

The name the site gave each game. It follows the line the game turned into, so games that began the same way can end up under different names.

OpeningColourGamesScoreWin chance after move 10
French DefenseBlack1373%59%
Sicilian DefenseWhite1373%64%
Sicilian DefenseBlack786%47%
Caro Kann DefenseWhite633%46%
Indian GameBlack658%52%
Vienna GameWhite667%62%
French DefenseWhite475%58%
Pirc DefenseWhite488%38%
English OpeningBlack383%40%
Kings GambitBlack367%49%
Kings Pawn OpeningWhite3100%61%
Alapin Sicilian DefenseBlack20%17%
Four Knights GameWhite2100%57%
Giuoco Piano GameWhite250%49%
Kings Indian DefenseBlack2100%56%

By first moves

The same games by the moves they began with, each side's first three, however they were named later. Each row is the games that went that way, under the row they branched from; moves all of them went on to play are folded in. Lines with fewer than 3 games are left out.

As whiteGamesScoreWin chance after move 10
5370%56%
1971%57%
1267%59%
667%56%
367%71%
570%63%
350%58%
1570%62%
1373%63%
658%58%
350%61%
580%60%
475%62%
633%46%
540%47%
475%58%
4100%51%
3100%57%
As blackGamesScoreWin chance after move 10
2861%50%
1373%59%
560%51%
367%29%
475%64%
367%55%
1055%41%
540%28%
333%29%
540%45%
367%49%
1065%48%
3100%53%

As the line narrows

Habits

Castled by move 10
Most coaches aim for nearly always.
69%
Never castled (games of 15+ moves)
A king left in the middle is a target once lines open.
8%
Queen moved in the first 6 moves
Early queen trips usually cost time as she gets chased.
4%
Two or more minor pieces undeveloped at move 12
Get the knights and bishops out before going on adventures.
9%
PhaseMistakes per 100 moves
Opening (989 moves)5.6
Middlegame (1267 moves)10.3
Endgame (521 moves)6.0

Every game

Newest first. Open a game for its serious mistakes (10%+ win chance) on boards or step through the whole game move by move, with the engine's view of every position.

Download all 100 games as PGN, or , to open in another chess program, with the engine's evaluation and the clock after every move.

Nov 7, 2026 · vs ▚○◣▗╯▐ (1919) · Won by resignationwon by resignation · 76% accuracy (vs 70%) · 4 mistakes
Nov 7, 2026 · vs ●π▟╭◥▗ (1912) · Won by resignationwon by resignation · 99% accuracy (vs 82%) · 0 mistakes
Nov 7, 2026 · vs ╳▜▟▄●▙ (1953) · Lost by resignationlost by resignation · 63% accuracy (vs 87%) · 2 mistakes
Nov 7, 2026 · vs ▞♣︎▒╯╳π (1942) · Won by resignationwon by resignation · 70% accuracy (vs 72%) · 4 mistakes
Nov 5, 2026 · vs ♥︎π▜◥▜▝ (1899) · Won by resignationwon by resignation · 97% accuracy (vs 87%) · 0 mistakes
Nov 4, 2026 · vs ▄▞○▀╭π (1865) · Won by resignationwon by resignation · 86% accuracy (vs 71%) · 2 mistakes
Nov 3, 2026 · vs ╲╰▖╱▚▙ (1880) · Won by resignationwon by resignation · 98% accuracy (vs 84%) · 0 mistakes
Oct 31, 2026 · vs ╳♦︎╱▙▘▀ (1877) · Won by resignationwon by resignation · 62% accuracy (vs 55%) · 6 mistakes
Oct 31, 2026 · vs ╳╱▛▝▘▄ (1879) · Lost on timelost on time · 80% accuracy (vs 88%) · 3 mistakes
Oct 31, 2026 · vs ╯π╮╯╳╲ (1963) · Won by resignationwon by resignation · 99% accuracy (vs 83%) · 0 mistakes
Oct 23, 2026 · vs ▒◢◢▝╳◤ (1854) · Won by resignationwon by resignation · 97% accuracy (vs 75%) · 0 mistakes
Oct 16, 2026 · vs ♠︎▄╱♣︎╲╰ (1890) · Lost by resignationlost by resignation · 46% accuracy (vs 83%) · 1 mistake
Oct 15, 2026 · vs ◤◢▝○╲▘ (1907) · Lost on timelost on time · 95% accuracy (vs 89%) · 1 mistake
Oct 14, 2026 · vs ▟╭▜▙╲◣ (1926) · Lost by resignationlost by resignation · 53% accuracy (vs 83%) · 3 mistakes
Oct 14, 2026 · vs ▛╳▒▞♣︎▟ (1889) · Won by checkmatewon by checkmate · 52% accuracy (vs 67%) · 3 mistakes
Oct 13, 2026 · vs ▙▟▐▙╱▗ (1879) · Won by checkmatewon by checkmate · 70% accuracy (vs 62%) · 1 mistake
Oct 12, 2026 · vs ♠︎╯π▗▜╰ (1847) · Won by resignationwon by resignation · 92% accuracy (vs 80%) · 2 mistakes
Oct 9, 2026 · vs ♥︎▟◥▘▌▟ (1901) · Lost by resignationlost by resignation · 86% accuracy (vs 94%) · 2 mistakes
Oct 9, 2026 · vs ▄π▞▗◣▀ (1852) · Won by checkmatewon by checkmate · 97% accuracy (vs 85%) · 0 mistakes
Oct 9, 2026 · vs ◥╮●◥▐╮ (1866) · Drew by agreementdrew by agreement · 75% accuracy (vs 77%) · 4 mistakes
Oct 9, 2026 · vs ╱○╲♣︎╭╮ (1866) · Won by checkmatewon by checkmate · 79% accuracy (vs 71%) · 4 mistakes
Oct 9, 2026 · vs ▌▙╱▘♦︎▟ (1869) · Won by resignationwon by resignation · 96% accuracy (vs 90%) · 0 mistakes
Oct 8, 2026 · vs π╯▄◢╲▛ (1807) · Won by resignationwon by resignation · 74% accuracy (vs 53%) · 6 mistakes
Oct 8, 2026 · vs ▄╭▙♦︎╳◣ (1850) · Won by resignationwon by resignation · 98% accuracy (vs 88%) · 0 mistakes
Oct 4, 2026 · vs ▟╱▒◣╮▟ (1821) · Won by resignationwon by resignation · 98% accuracy (vs 86%) · 0 mistakes
Oct 4, 2026 · vs ╳▀▙◢▗π (1805) · Won by resignationwon by resignation · 93% accuracy (vs 67%) · 0 mistakes
Oct 4, 2026 · vs ╮▖▜◢╳╮ (1819) · Won by resignationwon by resignation · 72% accuracy (vs 66%) · 3 mistakes
Oct 2, 2026 · vs ▖╳╰╳▒▐ (1828) · Lost by resignationlost by resignation · 70% accuracy (vs 84%) · 4 mistakes
Oct 1, 2026 · vs ▀▒▌◢♠︎◤ (1831) · Won by resignationwon by resignation · 96% accuracy (vs 88%) · 1 mistake
Sep 28, 2026 · vs ▚▐▝▒○╮ (1788) · Won by checkmatewon by checkmate · 83% accuracy (vs 78%) · 3 mistakes
Sep 25, 2026 · vs ▌●▐╭▟♦︎ (1878) · Lost by resignationlost by resignation · 58% accuracy (vs 91%) · 1 mistake
Sep 25, 2026 · vs ▌▛╳●◣◥ (1774) · Won by checkmatewon by checkmate · 83% accuracy (vs 79%) · 7 mistakes
Sep 25, 2026 · vs ╰♥︎◣▚▖▙ (1753) · Won by checkmatewon by checkmate · 100% accuracy (vs 54%) · 0 mistakes
Sep 25, 2026 · vs ◥♥︎●▛◢▐ (1751) · Won by resignationwon by resignation · 53% accuracy (vs 69%) · 3 mistakes
Sep 25, 2026 · vs ○●♦︎♦︎▒▐ (1746) · Won by resignationwon by resignation · 97% accuracy (vs 71%) · 0 mistakes
Sep 25, 2026 · vs ▛╲╭◢♥︎○ (1765) · Won by resignationwon by resignation · 99% accuracy (vs 78%) · 0 mistakes
Sep 23, 2026 · vs ▌▌╲▟♠︎▟ (1738) · Won by resignationwon by resignation · 54% accuracy (vs 32%) · 4 mistakes
Sep 23, 2026 · vs ◢◢╱▝▌▟ (1709) · Won by resignationwon by resignation · 83% accuracy (vs 79%) · 2 mistakes
Sep 22, 2026 · vs ▙◥╱♣︎╯▗ (1722) · Won by resignationwon by resignation · 85% accuracy (vs 84%) · 4 mistakes
Sep 20, 2026 · vs ▄▜╯▌◥╳ (1728) · Lost by resignationlost by resignation · 84% accuracy (vs 75%) · 2 mistakes
Sep 20, 2026 · vs ╭▝▗▞╲▖ (1683) · Won by resignationwon by resignation · 90% accuracy (vs 81%) · 1 mistake
Sep 5, 2026 · vs ▚▛╯▟◤▞ (475) · Won by checkmatewon by checkmate · 98% accuracy (vs 78%) · 0 mistakes
Sep 3, 2026 · vs ▄╭▌╲◢♣︎ (1742) · Lost on timelost on time · 69% accuracy (vs 83%) · 2 mistakes
Sep 3, 2026 · vs ▘▛▟▗▌▖ (1724) · Won by resignationwon by resignation · 83% accuracy (vs 71%) · 2 mistakes
Sep 3, 2026 · vs ▟▄╮π▖╳ (1755) · Lost by resignationlost by resignation · 55% accuracy (vs 99%) · 1 mistake
Aug 25, 2026 · vs ▒▚▚▄▗▜ (1716) · Won by resignationwon by resignation · 94% accuracy (vs 79%) · 0 mistakes
Aug 22, 2026 · vs ▒╰╭▖○╯ (1724) · Lost by resignationlost by resignation · 71% accuracy (vs 89%) · 2 mistakes
Aug 8, 2026 · vs ▄◤▀▒♣︎π (1760) · Lost by resignationlost by resignation · 76% accuracy (vs 87%) · 2 mistakes
Aug 1, 2026 · vs ♦︎▌▐╳╲▚ (1708) · Won by resignationwon by resignation · 87% accuracy (vs 77%) · 2 mistakes
Aug 1, 2026 · vs ○▛▜▖╯╰ (1769) · Lost by abandonmentlost by abandonment · 96% accuracy (vs 83%) · 0 mistakes
Jul 24, 2026 · vs ▝▀▘▞○╲ (1701) · Won by checkmatewon by checkmate · 96% accuracy (vs 89%) · 0 mistakes
Jul 24, 2026 · vs ♦︎▖π◥●▒ (1689) · Won by resignationwon by resignation · 86% accuracy (vs 80%) · 3 mistakes
Jul 23, 2026 · vs ▛◣▌◤▖▙ (1695) · Won by checkmatewon by checkmate · 85% accuracy (vs 83%) · 1 mistake
Jul 22, 2026 · vs ╱╯▒▘▛▞ (1705) · Won by checkmatewon by checkmate · 98% accuracy (vs 92%) · 0 mistakes
Jul 21, 2026 · vs ○▐♥︎▜╱╮ (1681) · Won on timewon on time · 91% accuracy (vs 85%) · 1 mistake
Jul 21, 2026 · vs ╯▟╭▙▘▘ (1723) · Lost by resignationlost by resignation · 84% accuracy (vs 99%) · 3 mistakes
Jul 18, 2026 · vs ♦︎▛▖π♠︎▚ (1708) · Lost by resignationlost by resignation · 84% accuracy (vs 91%) · 3 mistakes
Jul 10, 2026 · vs ○▞▜♥︎▌▐ (1709) · Lost by resignationlost by resignation · 79% accuracy (vs 96%) · 2 mistakes
Jul 9, 2026 · vs ╯▟▘╯▛▛ (1696) · Won by resignationwon by resignation · 95% accuracy (vs 53%) · 0 mistakes
Apr 5, 2026 · vs ▟●♥︎♣︎◣▀ (1722) · Lost by checkmatelost by checkmate · 83% accuracy (vs 91%) · 4 mistakes
Apr 4, 2026 · vs ▟▞♠︎▘◣♥︎ (1702) · Drew by repetitiondrew by repetition · 81% accuracy (vs 82%) · 6 mistakes
Apr 4, 2026 · vs ╳▝╭▗π▟ (1680) · Won by checkmatewon by checkmate · 93% accuracy (vs 83%) · 1 mistake
Apr 3, 2026 · vs ╱▛▗▜▌▙ (1688) · Won by resignationwon by resignation · 84% accuracy (vs 76%) · 4 mistakes
Apr 3, 2026 · vs ○◥╭▖○╲ (1692) · Won by checkmatewon by checkmate · 68% accuracy (vs 57%) · 2 mistakes
Mar 23, 2026 · vs ╲▗◣●▜▘ (1693) · Lost by resignationlost by resignation · 83% accuracy (vs 92%) · 2 mistakes
Mar 22, 2026 · vs ▀♦︎▄▗╰▒ (1676) · Won by checkmatewon by checkmate · 90% accuracy (vs 77%) · 3 mistakes
Mar 22, 2026 · vs ♣︎▖◢▜♠︎╯ (1692) · Lost by resignationlost by resignation · 58% accuracy (vs 74%) · 3 mistakes
Mar 22, 2026 · vs ▐♦︎╮▐♣︎▀ (1679) · Drew by repetitiondrew by repetition · 80% accuracy (vs 84%) · 2 mistakes
Mar 20, 2026 · vs ♣︎▝╲▞◥▝ (1630) · Won by resignationwon by resignation · 77% accuracy (vs 76%) · 2 mistakes
Mar 20, 2026 · vs ▘▐▙♥︎▀▌ (1685) · Drew by agreementdrew by agreement · 95% accuracy (vs 95%) · 0 mistakes
Mar 20, 2026 · vs ╰○♦︎╰●○ (1683) · Won by abandonmentwon by abandonment · 94% accuracy (vs 69%) · 0 mistakes
Mar 20, 2026 · vs ▚▐╲●╲▌ (1668) · Won by resignationwon by resignation · 90% accuracy (vs 75%) · 1 mistake
Mar 20, 2026 · vs ▟◥●▀▝╰ (1691) · Lost by resignationlost by resignation · 62% accuracy (vs 77%) · 7 mistakes
Mar 19, 2026 · vs ╲◥♠︎▄○▄ (1710) · Drew by repetitiondrew by repetition · 92% accuracy (vs 91%) · 3 mistakes
Mar 19, 2026 · vs ╰╳◤▟♣︎▛ (1675) · Won by resignationwon by resignation · 96% accuracy (vs 84%) · 0 mistakes
Mar 19, 2026 · vs ♥︎▟╲♦︎◣▄ (1675) · Won by resignationwon by resignation · 82% accuracy (vs 77%) · 6 mistakes
Mar 19, 2026 · vs ◣♠︎▘▛◤╭ (1686) · Lost by resignationlost by resignation · 70% accuracy (vs 87%) · 3 mistakes
Mar 19, 2026 · vs ╲♣︎▚▐♦︎◢ (1672) · Won by checkmatewon by checkmate · 86% accuracy (vs 80%) · 4 mistakes
Mar 18, 2026 · vs ●▖╭▚♦︎▖ (1666) · Won by checkmatewon by checkmate · 85% accuracy (vs 73%) · 2 mistakes
Mar 18, 2026 · vs ♥︎▒╱▒╳▐ (1672) · Lost by checkmatelost by checkmate · 24% accuracy (vs 85%) · 1 mistake
Mar 18, 2026 · vs ▟╭π▗╭▌ (1667) · Won on timewon on time · 81% accuracy (vs 91%) · 3 mistakes
Mar 18, 2026 · vs ▐▛╯▜▄◥ (1719) · Lost by resignationlost by resignation · 69% accuracy (vs 96%) · 2 mistakes
Mar 18, 2026 · vs ╭▟◢╯╱♠︎ (1633) · Won by checkmatewon by checkmate · 77% accuracy (vs 68%) · 5 mistakes
Mar 18, 2026 · vs ╲▒▗○▐╱ (1630) · Won by checkmatewon by checkmate · 89% accuracy (vs 73%) · 2 mistakes
Mar 18, 2026 · vs π▚▖●▚╱ (1604) · Won by resignationwon by resignation · 92% accuracy (vs 76%) · 2 mistakes
Mar 17, 2026 · vs ♠︎╲◥π╮π (1622) · Won by checkmatewon by checkmate · 46% accuracy (vs 40%) · 3 mistakes
Mar 17, 2026 · vs ▀╯◢▟▞♥︎ (1632) · Drew by repetitiondrew by repetition · 84% accuracy (vs 88%) · 4 mistakes
Mar 17, 2026 · vs π●▚╳▘◢ (1666) · Lost by resignationlost by resignation · 67% accuracy (vs 91%) · 1 mistake
Mar 17, 2026 · vs ▝◤▞▛╯π (1683) · Lost by resignationlost by resignation · 76% accuracy (vs 86%) · 3 mistakes
Mar 17, 2026 · vs ◣▐▄♦︎◤▚ (1660) · Lost by checkmatelost by checkmate · 70% accuracy (vs 91%) · 1 mistake
Mar 17, 2026 · vs ◤▘▀◤╱▒ (1665) · Won by resignationwon by resignation · 92% accuracy (vs 90%) · 1 mistake
Mar 17, 2026 · vs ▌●▝▘○▜ (1652) · Won by checkmatewon by checkmate · 85% accuracy (vs 66%) · 1 mistake
Mar 16, 2026 · vs ▘♠︎◥▞▙◢ (1655) · Lost by resignationlost by resignation · 59% accuracy (vs 68%) · 6 mistakes
Mar 16, 2026 · vs ▝◥▒◢◣╰ (1650) · Won by checkmatewon by checkmate · 76% accuracy (vs 67%) · 3 mistakes
Mar 16, 2026 · vs ▟▖♠︎╳♣︎╲ (1661) · Lost by checkmatelost by checkmate · 60% accuracy (vs 75%) · 5 mistakes
Mar 16, 2026 · vs ╲▖▝▟▀▒ (1721) · Won on timewon on time · 91% accuracy (vs 85%) · 3 mistakesaccount closed for fair play
Mar 16, 2026 · vs ♦︎▌╲╭▜♣︎ (1652) · Won by resignationwon by resignation · 79% accuracy (vs 70%) · 2 mistakes
Mar 16, 2026 · vs ▜◣▌╰╰○ (1705) · Lost by resignationlost by resignation · 57% accuracy (vs 76%) · 4 mistakes
Mar 16, 2026 · vs ╰▛◥●▌╳ (1620) · Won by resignationwon by resignation · 88% accuracy (vs 76%) · 2 mistakes
Mar 16, 2026 · vs ╮╭▘╰▘◣ (1637) · Won by abandonmentwon by abandonment · 78% accuracy (vs 71%) · 4 mistakes

How this was worked out

Every position was searched by Stockfish (150,000 nodes per position, about depth 15-17). Evaluations are converted to win chance on a curve fitted to how often players win from each one. A move that drops the mover's win chance by 10 points or more counts as a mistake, 20 or more as a blunder. Threats are found by letting the opponent move twice (a null move). If that wins material or mates, there was a threat on the board. How hard a tactic was is the number of opponent moves in the engine's line before the side that erred is two pawns or more down for good, or the length of the mate.

Engines are much better at telling that a move was bad than why. The pattern labels (fork, pin, loose piece...) come from rules applied to the engine's line and are usually, but not always, the whole story.

Sharp positions: before each of ▚▚▙♥︎╱╯'s moves after the opening with the game still open, Stockfish searched every legal move at once (200,000 nodes between them). A move within 5 points of win chance of the best was safe; a position with fewer than a quarter of its moves safe was sharp.

The human side comes from Maia-2 (Tang, Jiao, McIlroy-Young, Kleinberg, Sen and Anderson, NeurIPS 2024; CSSLab, University of Toronto; MIT licence), a model trained on lichess games that gives, for players of a rating, the chance of each move and the expected score. Its ratings are lichess's, and are put on the site's scale by fitting the opponents' moves, whose ratings are known. A mistake's cost in practice is the player's expected score after the best move less that after the move played, each averaged over the replies an opponent of their level would likely make. The level a side's moves are most like is the one whose players would most likely have made them.

Against players of the same level: in each position searched move by move, the chance that a player of ▚▚▙♥︎╱╯'s level plays one of the moves that were mistakes there (by Maia-2) is the mistakes expected of the level. They're scaled to match the count of mistakes over all those positions together, so a ratio says where the player differs from one kind of position to another, not overall.

A pattern is called clear when it's bigger than game-to-game luck would explain: a game's moves go well or badly together, so games are counted as the samples, not moves. Where a section compares several things at once, each has to clear a stricter bar, so that one doesn't stand out by chance alone.

↑ Contents

Loading...

move playedbetter wasengine's best now
▚▚▙♥︎╱╯Opponent

Made 18 Nov 2026 · runner 0.1.0-5e42a45 · engine 0.1.0-b15ca3b