llmrun

llmrun Composite Score · Coding

The best open LLMs for coding, ranked on SWE-bench, LiveCodeBench, Aider and other coding boards. The score shown is the overall llmrun Composite Score; the highlighted column is the coding skill score used for the order.

45 benchmarks4 sourcesUpdated 17 Oct 2026Reference scale 2026-Q4How the Composite Score is built

Coding score vs VRAM needed

This chart doesn't show proprietary models.

Models ranked by coding llmrun Composite Score
# (open / overall)Modelllmrun Composite ScoreCodingAgentsMathScienceReasoningBenchmarksVRAM
1 / 42Qwen3.8 27B17.9 GB · 15 benchmarks1201231181121241517.9 GB
2 / 67Gemma 4 31B IT21.7 GB · 13 benchmarks108––1051101321.7 GB
3 / 74Qwen3.6 35B A3B22.0 GB · 11 benchmarks105–1091101041122.0 GB
4 / 76Gemma 4 26B A4B IT16.5 GB · 8 benchmarks104––102102816.5 GB
5 / 85Qwen3.6 27B17.9 GB · 11 benchmarks102–1141111051117.9 GB
6 / 94GPT OSS 20B13.1 GB · 10 benchmarks101––92911013.1 GB
7 / 105Qwen3.5 27B17.9 GB · 6 benchmarks98–––111617.9 GB
8 / 112Qwen3 Coder Next48.3 GB · 3 benchmarks—95––91–348.3 GB
9 / 113Qwen3 32B22.6 GB · 8 benchmarks93––9692822.6 GB
10 / 121Llama 3.3 70B Instruct51.3 GB · 12 benchmarks76––81821251.3 GB
11 / 123Gemma 3 27B IT21.7 GB · 9 benchmarks70––8174921.7 GB
12 / 125Llama 3.1 8B Instruct7.9 GB · 9 benchmarks56––566997.9 GB

The range after each score is a 90% interval: given the boards a model has results on, its true score is very likely inside it. Short ranges mean many agreeing results; long ranges mean few or conflicting ones.

Why some models are missing. A model receives a score only if it has results on at least 4 benchmarks across at least 2 categories, with one being reasoning or coding, or on 3 benchmarks that narrow its 90% range to at most 15.6 points. The results must come from at least two different benchmarks: categories of one benchmark, such as LiveBench, count once. Skill scores require at least 2 benchmarks for that skill; otherwise they display as –.

VRAM is llmrun's estimate at Q4_K_M (or the smallest quantization we track) for the weights plus room for a 16K-token context. Longer contexts need more memory. Proprietary models can't run locally, so the VRAM filter hides them.

How the llmrun Composite Score is built · llmrun doesn't run these benchmarks; scores come from public sources.