Tiel Coder 35B A3B APEX I MiniPlus V2.1 needs about 16.4 GB of memory at its main file (a 15.2 GB file) with an 8K context window, so it fits on a 24 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 2.8 GB.
Tiel Coder 35B A3B APEX I MiniPlus V2.1 – a 35 B MoE model with 256K context
Tiel Coder 35B A3B APEX I MiniPlus V2.1 is a 35 B parameter mixture‑of‑experts model based on qwen35moe. It supports coding, reasoning and vision. The model is released under the MIT license and is available as a single GGUF file.
Good at
- Coding tasks
- Reasoning with long context
- Vision inference
Limits
- Requires 256K context support
- Large VRAM/CPU memory for full model
- No dedicated vision token support in quantized form
Best for
- Local code generation
- Long‑form reasoning
- Vision‑enabled applications
Who it’s for. Developers and researchers who need a large MoE model that can run locally with full 256K context. The model is suitable for users with high‑end GPUs or large RAM setups.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 15.2 GB | 16.4 GB | Too big | Get file → |
The only available quant is unknown, 15.23 GB on disk and about 16.4 GB RAM at 8 K context. For 8 GB VRAM use a lower‑rank quant if available; otherwise the model will not fit. For 16 GB VRAM the unknown quant can be loaded with offload to RAM.
What GPU do you need for Tiel Coder 35B A3B APEX I MiniPlus V2.1?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: the best quant that fits is the main file (15.2 GB file, about 16.4 GB in use).
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Tiel Coder 35B A3B APEX I MiniPlus V2.1
How much VRAM does Tiel Coder 35B A3B APEX I MiniPlus V2.1 need?
About 16.4 GB at its main file with an 8K context window. That is the 15.2 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run Tiel Coder 35B A3B APEX I MiniPlus V2.1 on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 16.4 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Tiel Coder 35B A3B APEX I MiniPlus V2.1 GGUF?
It depends on the quant: file is 15.2 GB.
What context length does Tiel Coder 35B A3B APEX I MiniPlus V2.1 support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.7 GB at 8K and 2.8 GB at 32K.
Where can I download Tiel Coder 35B A3B APEX I MiniPlus V2.1 GGUF?
The files are on Hugging Face in the IsValorum/Tiel-Coder-35B-A3B-APEX-I-MiniPlus-V2.1-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Tiel Coder 35B A3B APEX I MiniPlus V2.1 use?
Hugging Face lists the license as mit. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8 GB VRAM?
No, the unknown quant requires about 16.4 GB RAM at 8 K context, so 8 GB VRAM is insufficient.
What license does the model use?
The model is released under the MIT license.
Does the model support vision?
Yes, vision is listed as a detected ability, but the quantized file does not specify separate vision tokens.