Every rated game played on lichess and chess.com, pulled at build time and taken apart — the rating arc, where the games actually end, what the repertoire drifted into, and a bot tuned to play like its owner.
19,000 rated and casual games across two platforms, pulled from both public APIs at build time and analysed before anything on this page was written. The finding was not flattering: 41.5% of my decided games ended on a clock, not on a board — 49.8% of every loss was a timeout, against 33.0% of wins won on the opponent's. I don't lose positions nearly as often as I lose time.
| Progress | Wins | Losses | Gap |
|---|---|---|---|
| 0–10% | 99.0% | 98.7% | +0.3% |
| 10–20% | 95.1% | 93.4% | +1.7% |
| 20–30% | 89.2% | 85.8% | +3.4% |
| 30–40% | 82.1% | 76.8% | +5.3% |
| 40–50% | 74.5% | 67.7% | +6.8% |
| 50–60% | 67.0% | 59.2% | +7.8% |
| 60–70% | 58.7% | 50.1% | +8.6% |
| 70–80% | 50.7% | 42.1% | +8.6% |
| 80–90% | 43.8% | 35.6% | +8.2% |
| 90–100% | 36.8% | 28.6% | +8.2% |
Corpus
19,000
games, 2019-02-09 → 2026-09-06. 9,246W / 9,278L / 476D — a losing record by 32.
Time at the board
1,055 h
763 h self-reported by lichess, plus 291 h derived from the wall clock in 4,577 chess.com PGNs — chess.com publishes no play-time figure, so this is two measurements added together, not one metric.
Showing up
83.1%
of days played — 2,300 of 2,767 days in the span, longest unbroken run 298 days. Longest loss streak 14 beats the longest win streak 12.
Repertoire as Black
I opened 2019 with the Scandinavian — at least 36.3% of my games as Black that year. By 2020 it was displaced by the Modern Defense (35.8%), and by 2022 it had dropped out of the top five entirely. It is my most-played reply again today: 33.8% of Black games in 2026.
Both halves are real, but they are two within-platform observations rather than one continuous line. The abandonment happened on lichess and the return happened on chess.com, with the 2023 handoff sitting between them — so “I came back to my first opening” cannot be cleanly separated from “I started fresh on a new site.” It is a handoff, not two accounts running side by side: lichess’s last flicker is 3 games in 2025, which is the only reason its rating history reaches that far. Game counts say when someone was actually playing; rating-history dates do not.
| Year | lichess | chess.com | Most-played reply | Scandinavian (top 5) |
|---|---|---|---|---|
| 2019 | 2,480 | 0 | Scandinavian Defense Mieses Kotrc Variation 26.3% | 36.3% |
| 2020 | 3,262 | 0 | Modern Defense 35.8% | 12.5% |
| 2021 | 4,672 | 19 | Modern Defense 54.5% | — |
| 2022 | 3,365 | 0 | Modern Defense 51.2% | — |
| 2023handoff | 337 | 2,017 | Modern Defense 21.1% | 20.5% |
| 2024 | 0 | 1,043 | Scandinavian Defense Mieses Kotrc Variation 17.2% | 21.3% |
| 2025 | 3 | 590 | Scandinavian Defense Mieses Kotrc Variation 14.5% | 17.9% |
| 2026 | 0 | 1,212 | Scandinavian Defense Mieses Kotrc Variation 26.9% | 33.8% |
14,119 games · joined 2019-02-06 · last game 2025-01-16
Every format on this account reads provisional — rating deviation grew while it sat idle after 2025-01-16, so what it shows is a last rating, not current form.
4,881 games · joined 2021-01-22 · last game 2026-09-06
Over in the Loopdown I give recurring production bugs names and personalities, because a bug you can name is a bug you can hunt. The same three keep turning up over the board — and unlike the ones at work, these came with their own receipts.
49.8%
of every loss, decided by the clock rather than the board. Not an opponent — a deadline.
34.8%
win rate by game nine of one sitting, against 48.5% on game one. He should have stopped at eight.
69 games — a thin tail, shown with its n
26.9%
of games as Black are the Scandinavian again in 2026, after it was displaced almost entirely on the other account. First loves are a repertoire choice.
Generated 2026-09-06 from the lichess and chess.com public APIs by scripts/gen-chess-stats.mjs — every number on this page is build output, not prose. Re-run it and the figures move.
Second pass — four fields the first analysis never read
More clock does not help me
Ten times the thinking time moves the win rate by half a point. Whatever decides these games, it is not how long I get to look at them.
I leave theory on move one
median book exit: ply 2
In the 109 games where I stayed in a named opening to ply 8 or deeper, I won 54.1% — against 48.9% across the 12,990 where I was out by ply 4. The sample is small and I have never acted on it.
Where the game came from
Matchmaking is a coin flip. Arena is a bloodbath. The gap is twenty-one points and the arena sample is small enough to stay a hypothesis.
How they actually end
Across every game, not just decided ones: the clock ends more of them than checkmate and resignation combined.
14,119 lichess games · scripts/gen-chess-deep.mjs
frequently asked
SDE-2, Android & Product Owner at Dice.tech (June 2023 - Present), platform owner of the app behind 50k+ monthly active users (22k+ daily, platform owner at Dice.tech). See the source.
Took GPS accuracy to 95%: up from 50%, by predictive dead reckoning. See the source.
80% crash reduction: Crashlytics + structured concurrency fixes. See the source.
~87% of the UI layer: 455k of 523k UI-layer LOC, verified screen by screen against the legacy XML. See the source.
B.Tech, Computer Science & Engineering, NIT Bhopal (MANIT) (2017 - 2021). See the source.
Consulting Engineer, Platform & AI at Neev Consulting (April 2026 - Present). Built the LLM assistant layer of an ERPNext/Frappe consulting ERP: business-context resolution, capability discovery, and an AI capability gate that defaults OFF with a test proving it. Models client to project to PO to milestone to GST invoice to payment end to end. See the source.
Doori: Offline-first mileage, travel & expense tracker on one Kotlin codebase across Android, iOS, Wear OS, watchOS & Desktop. See the source.
Gaddi: A Hinglish social-deduction bluffing game of power, satire & second chances. Gaddi ke liye kuch bhi karega. See the source.
PaymentsLab-KMP: An Integration Lab for the Android payments ecosystem: every gateway behind one abstraction, with a live look at what actually happens on each transaction. See the source.
Candidai: A native, multiplatform AI career-intelligence engine, and the open-source project it's built on. See the source.
Yes: The Loopdown, his field-notes writing hub, where the recurring bug characters are named after real production incidents. See the source.
Answered by his own teammates, not by him: see the EB Profiles, one question per member, in their own words. See the source.
Open to remote (worldwide / India) and hybrid in Pune / Bengaluru. Email siddharthpandalai990@gmail.com. See the source.
Shared Kotlin Multiplatform libraries used across his own apps, plus merged upstream pull requests on career-ops: see the repos and the running count. See the source.
Yes: see the Play Store shelf for the apps that are actually live and installable, not just source. See the source.
Every route on the site, as a tile you can open: 3D builds, labs and canvases, not screenshots. See the source.