Every open model in our directory, ranked by how well it runs on NVIDIA B200 GPU (192GB) at 4-bit. Grades weigh whether the model fits in memory and how fast it should run.
NVIDIA B200 GPU has 192 GB of VRAM, enough to run 159 of the 169 open models we track at 4-bit. The largest that still fits well is Kimi K2.7 Code (1000B), and the top-rated is Llama 3.1 70B Instruct at about 57 tok/s.
159 of 169 models run comfortably on NVIDIA B200 GPU.
See full NVIDIA B200 GPU specs and pricingThe top models this device can run at 4-bit, ranked by fit and speed.
| Model | Grade | Speed | VRAM |
|---|---|---|---|
| Llama 3.1 70B InstructMeta | SS | 57.1 tok/s | 112.8 GB |
| Llama 3.3 70B InstructMeta | SS | 57.1 tok/s | 112.8 GB |
| Nvidia Nemotron 3 SuperNVIDIA | SS | 62.2 tok/s | 103.5 GB |
| DeepSeek-V4-FlashDeepSeek | SS | 57.5 tok/s | 112.0 GB |
| Llama 4 Maverick |
Llama 3.1 70B Instruct is the highest-rated model that runs on NVIDIA B200 GPU at 4-bit, at about 57 tok/s. In total, NVIDIA B200 GPU can run 159 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.
| SS |
| 44.0 tok/s |
| 146.4 GB |
| GLM-5Z.ai | SS | 73.4 tok/s | 87.7 GB |
| GLM-5.1Z.ai | SS | 73.4 tok/s | 87.7 GB |
| Kimi K2.7 CodeMoonshot AI | SS | 74.7 tok/s | 86.2 GB |
| Kimi K2.6Moonshot AI | SS | 74.7 tok/s | 86.2 GB |
| Kimi K2 Instruct 0905Moonshot AI | SS | 76.1 tok/s | 84.6 GB |
| Kimi K2 ThinkingMoonshot AI | SS | 76.1 tok/s | 84.6 GB |
| Kimi K2.5Moonshot AI | SS | 76.1 tok/s | 84.6 GB |
| 70B | SS | 57.1 tok/s | 112.8 GB | ||
| 70B | SS | 57.1 tok/s | 112.8 GB | ||
Nvidia Nemotron 3 SuperNVIDIA | 120B(12B active) | SS | 62.2 tok/s | 103.5 GB | |
DeepSeek-V4-FlashDeepSeek | 284B(13B active) | SS | 57.5 tok/s | 112.0 GB | |
Llama 4 MaverickMeta | 400B(17B active) | SS | 44.0 tok/s | 146.4 GB | |
GLM-5Z.ai | 744B(40B active) | SS | 73.4 tok/s | 87.7 GB | |
GLM-5.1Z.ai | 744B(40B active) | SS | 73.4 tok/s | 87.7 GB | |
Kimi K2.7 CodeMoonshot AI | 1000B(32B active) | SS | 74.7 tok/s | 86.2 GB | |
| Ad | |||||
Kimi K2.6Moonshot AI | 1000B(32B active) | SS | 74.7 tok/s | 86.2 GB | |
Kimi K2 Instruct 0905Moonshot AI | 1000B(32B active) | SS | 76.1 tok/s | 84.6 GB | |
Kimi K2 ThinkingMoonshot AI | 1000B(32B active) | SS | 76.1 tok/s | 84.6 GB | |
Kimi K2.5Moonshot AI | 1000B(32B active) | SS | 76.1 tok/s | 84.6 GB | |
Falcon 180BTechnology Innovation Institute | 180B | SS | 59.7 tok/s | 107.8 GB | |
GLM-4.6Z.ai | 355B(32B active) | SS | 91.7 tok/s | 70.3 GB | |
Gemma 4 31B ITGoogle | 31B | SS | 78.6 tok/s | 82.0 GB | |
Mistral Large 3 675BMistral AI | 675B(41B active) | SS | 97.2 tok/s | 66.3 GB | |
| Ad | |||||
Carnice-V2-27bkai-os | 27B | SS | 88.5 tok/s | 72.8 GB | |
Qwen3.6-27BAlibaba | 27B | SS | 88.5 tok/s | 72.8 GB | |
Qwen3.5-27BAlibaba | 27B | SS | 88.5 tok/s | 72.8 GB | |
DeepSeek-V3DeepSeek | 671B(37B active) | SS | 107.6 tok/s | 59.8 GB | |
DeepSeek-R1DeepSeek | 671B(37B active) | SS | 107.6 tok/s | 59.8 GB | |
DeepSeek-V3.1DeepSeek | 671B(37B active) | SS | 107.6 tok/s | 59.8 GB | |
DeepSeek-V3.2DeepSeek | 685B(37B active) | SS | 107.6 tok/s | 59.8 GB | |
Hy3Tencent | 295B(21B active) | SS | 115.6 tok/s | 55.7 GB | |
| Ad | |||||
GLM-4.7Z.ai | 358B(32B active) | SS | 122.4 tok/s | 52.6 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.