Every open model in our directory, ranked by how well it runs on GMKtec EVO-X2 (Ryzen AI Max+ 395 128GB) (96GB) at 4-bit. Grades weigh whether the model fits in memory and how fast it should run.
GMKtec EVO-X2 (Ryzen AI Max+ 395 128GB) has 96 GB of VRAM, enough to run 145 of the 169 open models we track at 4-bit. The largest that still fits well is Kimi K2 Instruct (1000B), and the top-rated is Qwen3-30B-A3B at about 38 tok/s.
145 of 169 models run comfortably on GMKtec EVO-X2 (Ryzen AI Max+ 395 128GB).
See full GMKtec EVO-X2 (Ryzen AI Max+ 395 128GB) specs and pricingThe top models this device can run at 4-bit, ranked by fit and speed.
| Model | Grade | Speed | VRAM |
|---|---|---|---|
| Qwen3-30B-A3BAlibaba | AA | 38.3 tok/s | 5.4 GB |
| LFM2.5-8B-A1BLiquid AI | AA | 70.9 tok/s | 2.9 GB |
| Llama 3 8B InstructMeta | AA | 36.4 tok/s | 5.7 GB |
| PersonaPlex 7BNVIDIA | AA | 43.0 tok/s | 4.8 GB |
| Llama 2 7B ChatMeta |
Qwen3-30B-A3B is the highest-rated model that runs on GMKtec EVO-X2 (Ryzen AI Max+ 395 128GB) at 4-bit, at about 38 tok/s. In total, GMKtec EVO-X2 (Ryzen AI Max+ 395 128GB) can run 145 of the 169 open models we track.
We size each model at 4-bit (Q4_K_M), add the KV cache for its context length and a fixed runtime overhead, then compare that to this device VRAM. Each model is graded on how comfortably it fits and how fast it should run on this card.
It is an estimate of decode speed in tokens per second at 4-bit, based on this device memory bandwidth and each model size. Real speed depends on your runtime, batch size, and context length, so use it to compare models, not as a hard promise.
Lower-bit quantization shrinks a model so more of them fit. These grades already assume 4-bit, which is the common local default. Going below 4-bit can squeeze a larger model in at some quality cost; going above needs more VRAM and may not fit.
| AA |
| 43.0 tok/s |
| 4.8 GB |
| Carnice-9b for Hermes agentkai-os | AA | 34.3 tok/s | 6.0 GB |
| VibeThinker-3BWeiboAI | AA | 54.0 tok/s | 3.8 GB |
| Gemma 4 E2B ITGoogle | AA | 55.6 tok/s | 3.7 GB |
| North Mini CodeCohere | AA | 24.6 tok/s | 8.4 GB |
| Nemotron 3 Nano OmniNVIDIA | AA | 24.2 tok/s | 8.5 GB |
| Qwen3.6 35B-A3BAlibaba | AA | 24.2 tok/s | 8.5 GB |
| Qwen3.5-35B-A3BAlibaba | AA | 24.2 tok/s | 8.5 GB |
Qwen3-30B-A3BAlibaba | 30B(3B active) | AA | 38.3 tok/s | 5.4 GB | |
LFM2.5-8B-A1BLiquid AI | 8.3B(1.5B active) | AA | 70.9 tok/s | 2.9 GB | |
| 8B | AA | 36.4 tok/s | 5.7 GB | ||
PersonaPlex 7BNVIDIA | 7B | AA | 43.0 tok/s | 4.8 GB | |
Llama 2 7B ChatMeta | 7B | AA | 43.0 tok/s | 4.8 GB | |
| 9B | AA | 34.3 tok/s | 6.0 GB | ||
VibeThinker-3BWeiboAI | 3B | AA | 54.0 tok/s | 3.8 GB | |
Gemma 4 E2B ITGoogle | 2B | AA | 55.6 tok/s | 3.7 GB | |
| Ad | |||||
North Mini CodeCohere | 30B(3B active) | AA | 24.6 tok/s | 8.4 GB | |
Nemotron 3 Nano OmniNVIDIA | 30B(3B active) | AA | 24.2 tok/s | 8.5 GB | |
Qwen3.6 35B-A3BAlibaba | 35B(3B active) | AA | 24.2 tok/s | 8.5 GB | |
Qwen3.5-35B-A3BAlibaba | 35B(3B active) | AA | 24.2 tok/s | 8.5 GB | |
Mistral 7B InstructMistral AI | 7B | AA | 32.2 tok/s | 6.4 GB | |
Llama 2 13B ChatMeta | 13B | AA | 24.3 tok/s | 8.5 GB | |
Gemma 4 E4B ITGoogle | 4B | BB | 29.8 tok/s | 6.9 GB | |
Gemma 3 4B ITGoogle | 4B | BB | 29.8 tok/s | 6.9 GB | |
| Ad | |||||
Mixtral 8x7B InstructMistral AI | 46.7B(12.9B active) | BB | 18.1 tok/s | 11.4 GB | |
DiffusionGemma 26B-A4BGoogle | 25.2B(3.8B active) | BB | 19.7 tok/s | 10.5 GB | |
Gemma 4 26B-A4B ITGoogle | 26B(4B active) | BB | 18.7 tok/s | 11.0 GB | |
GLM-4.5Z.ai | 355B(32B active) | BB | 4.0 tok/s | 51.8 GB | |
Kimi K2 InstructMoonshot AI | 1000B(32B active) | BB | 4.0 tok/s | 51.8 GB | |
| 70B | BB | 4.5 tok/s | 45.7 GB | ||
GLM-4.7Z.ai | 358B(32B active) | BB | 3.9 tok/s | 52.6 GB | |
Qwen3.5-397B-A17BAlibaba | 397B(17B active) | BB | 4.5 tok/s | 46.0 GB | |
| Ad | |||||
Qwen 3.5 OmniAlibaba | 397B(17B active) | BB | 4.6 tok/s | 45.2 GB | |

Model Compatibility
Use the calculator to weigh this device against any other, model by model, with speed and fit scores.
Mixture-of-experts models only activate a fraction of their parameters at a time, so their runtime memory is closer to the active size than the headline size. We score fit on the active parameters, which is why some very large models still fit.