Data as of October 13, 2026 · How the score is built
Nemotron 3.5 Bolt 74B-A9B
Decision readingNemotron 3.5 Bolt 74B-A9B is tracked, but not publicly ranked yet. The profile exposes 0 sourced benchmark rows and leaves unsupported fields blank until a published record exists.
Nemotron 3.5 Bolt 74B-A9B will be repriced, updated or retired. Get each notice with its source and date. Follow model changes
Lineage
The sequence follows explicit supersedes links. Each score is estimated for that model; a relative can inform a sparse estimate but never sets a floor, so a newer release can score below an earlier one. Scores and prices remain blank when the corresponding public row or first-party rate is unavailable.
Release date not sourced · you are here
Nemotron 3.5 Bolt 74B-A9BNot publicly ranked · Price not listed
Base entry
Spec sheet
Each documented value carries its source. Missing fields stay visible as not sourced or not published, rather than disappearing from the page.
- API model ID
- Not publishedNVIDIA RTX Spark launch announcement
- Context window
- Not published
- Maximum output
- Not sourced yet
- Knowledge cutoff
- Not sourced yet
- Input modalities
- Not sourced yet
- Output modalities
- Not sourced yet
- Parameters
- Not sourced yet
- Availability
- Coming soon. NVIDIA announced availability for October 15, 2026; release availability has not yet been verified.
- Cloud regions
- Not tracked yet
- Lifecycle
- Coming Soon
- API capabilities
- Tool calling, structured outputs, and batch support are not tracked yet
- Prompt caching
- Not documented in the pricing recordNVIDIA RTX Spark launch announcement
- Self-host
- Weight availability is pending
- Rate limits
- Not tracked yet
How to read this profile
The visual layer above carries the decisions. These notes preserve the model, ranking, coverage, and family context behind the numbers.
We track Nemotron 3.5 Bolt 74B-A9B, but no weighted text-model benchmark result is published on the site yet. This page shows the metadata and separate protocol evidence we can verify now; a BenchLM score will appear only if compatible public evaluations land.
Nemotron 3.5 Bolt 74B-A9B has no verified publication yet for weight access. Its context length is not documented in the current profile. The profile records its reasoning mode as pending.
Coming soon. NVIDIA announced availability for October 15, 2026; release availability has not yet been verified.
NVIDIA announced Nemotron 3.5 Bolt 74B-A9B for October 15, 2026. It describes a mixture-of-experts language model with 74 billion total parameters and 9 billion active parameters, using 2-bit quantization to fit in 24GB for local agents on RTX Spark. NVIDIA plans to release training data, weights, and recipes, with support in llama.cpp, vLLM, Ollama, Unsloth, and LM Studio. The announcement does not publish a context limit, API identifier, token price, or benchmark table. This coming-soon entry remains unranked.
The profile has no source-displayable benchmark row yet.
Last updated October 13, 2026. Runtime fields remain blank until a sourced snapshot exists.
Questions
How does Nemotron 3.5 Bolt 74B-A9B perform overall in AI benchmarks?
Nemotron 3.5 Bolt 74B-A9B does not have any source-displayable benchmark rows yet, so this profile does not assign a public score or rank. Documented specifications remain visible, while score-led charts and claims stay unavailable until a published evaluation can be attached to the exact model.
Does Nemotron 3.5 Bolt 74B-A9B have full benchmark coverage on BenchLM?
No. Nemotron 3.5 Bolt 74B-A9B currently has 0 source-displayable rows across 670 tracked benchmark slots. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.
What is the context window size of Nemotron 3.5 Bolt 74B-A9B?
Nemotron 3.5 Bolt 74B-A9B's context window is not documented in a source tied to this exact model yet. The profile leaves the value unavailable instead of borrowing a limit from an earlier family member or an unverified route. Maximum output length remains a separate field.