Linux Chess Engine Ratings as of 22 October 2019
The table below is shown in ratings order based on the
ratings list as of 19 October 2019 of all chess engines stronger than the current
human live blitz ratings leader as of
21 October 2019. It will be updated automatically within 8 hours of the
CCRL or human blitz ratings changing or a new Stockfish development
being made available.
Before you ask, yes, you can download the table as a CSV.
What's New (6 Oct 2019)
- Allie got a GPU upgrade to an RTX 2080 this week, which vaulted it above
Stockfish for the first time. I've got to question whether CCRL using such
expensive GPU hardware is making it a fair comparison against CPU-based engines.
Shouldn't CPU-based engines be tested with more than 4 cores now? Heck, the
12-core Ryzen 9 3900X (when you can get it!) still costs a lot less than an RTX 2080...
- Stockfish's version, rating and source/binary URLs are all for the
latest development version, rather than the annual major release that CCRL
usually test that can, of course, be up to a year out of date.
The rating is calculated as follows:
A = The CCRL rating for the latest major Stockfish version (2019-10-09) they've tested = 3625
B = The CCRL rating difference between the last two major versions of Stockfish ( and 2019-10-09) they've tested =
C = The Fishtest regression tests rating difference between the last two major Stockfish versions ( and 2019-10-09) that
CCRL have tested = 54
D = The Fishtest regression tests rating difference between the latest development version that has been regression tested and the latest major version (2019-10-09) of Stockfish that CCRL have tested = 44
Development version rating = (int)(A+D*B/C) =
The reason it's calculated
this way is that the Fishtest regression tests involve self-play, which gives
inflated ELO differences compared to CCRL's methodology of playing against
many foreign engines.
- The links to Gull are actually to a Linux-compatible fork called LazyGull.
- Sadly, the author of Equinox, Giancarlo Delli Colli, has
- Use of Wine
to run a Windows engine binary in Linux must be extremely simple to qualify
i.e. chmod u+x on the Windows binary and run it (assuming Wine is installed and
is used as the execution wrapper for Windows executables). Use of anything extra disqualifies it
e.g. winetricks, wine staging, environmental variables, extra wine parameters etc.
Please note that some engines (e.g. Hannibal and maybe others) may require the very
latest Wine development release to run.
- Engines that have neither source code nor any binaries available are therefore
closed source commercial engines that aren't freely downloadable.
Prices for these haven't been included because they
can vary depending on currency, taxes, versions etc.
- Engine binaries listed as "Compile" must be compiled on Linux using the source code.
Yes, some engines are open source, compile with gcc/g++ on Linux fine and even
provide Windows and/or Android binaries, but
not Linux binaries!
- Engine binaries listed as "Windows" means not only that they won't work
with Wine, but any optional source code won't compile and run on Linux either.
- I don't have some of the commercial engines,
so I can't comment if their binaries work in Linux or not.
- Failures on Linux are as follows:
Booot and Naum both start up with Wine OK,
but keyboard input fails (I usually like
to run "go infinite", but no keystrokes appeared in the console). The Booot
source code is written in Pascal on Windows and Naum has no source code
supplied, so there's no chance of compiling either of them in Linux.
Schooner's default setup crashes quickly in Wine with a page fault.
To fix this, remove the "book 0" line from sc.ini.
ChessBrainVB is one of the very few engines only available as a
32-bit Windows executable and my Wine is set up to run 64-bit Windows binaries only.
Although source code is supplied, it's written in Visual Basic (!) and
therefore can't be built on Linux. Spike is similarly unrunnable in my setup
thanks to a 32-bit only executable and no source code supplied.
DisasterArea crashes immediately with Wine, while Atlas core dumps on
a "go infinite" on Linux.
- If you're after weaker engines not listed in the table above, there's a
very good download resource for these - the
Chess Engine List
at the Computer Chess Wiki.
- I recommend Scid vs. PC
if you need a decent GUI in Linux to front-end the engines.
- Please don't ask for links to non-Linux binaries - that's not the purpose
of this page, which is intended for Linux chess fans. If you do spot
a problem with the information or links on this page, please e-mail me,
Richard K. Lloyd, at firstname.lastname@example.org
and I'll see if I can fix the problem.