Model comparison
Sakana Fugu-Ultra v1.1 vs Sarvam 105B
Head-to-head evidence from 0 shared benchmark results across 0 categories. Overall scores shown here use the public BenchAlign v5 ranking lane.
Public leaderboard positions: Sakana Fugu-Ultra v1.1 unranked (Not scored); Sarvam 105B #165 (Estimated). Intervals and evidence labels describe ranking uncertainty, not a guarantee for a specific workload.
Evidence parity. Sakana Fugu-Ultra v1.1 and Sarvam 105B share 0 comparable benchmark results. 0 of 8 categories are comparable. 0 results are unique to Sakana Fugu-Ultra v1.1; 11 to Sarvam 105B.
Updated July 24, 2026- Shared results
- 0
- Sakana Fugu-Ultra v1.1 only
- 0
- Sarvam 105B only
- 11
- Comparable categories
- 0 / 8
Benchmark data for Sakana Fugu-Ultra v1.1 and Sarvam 105B is coming soon on BenchLM.
Confidence note. This is a partial-evidence comparison with 0 shared benchmark results across 0 evidence categories; 0 of 8 categories currently have scoreable aggregates for both models. Treat the verdict as directional until coverage is more balanced.
Why this result
BenchLM does not have sourced benchmark coverage for Sakana Fugu-Ultra v1.1 yet. This comparison is currently limited to metadata such as context window, reasoning mode, and pricing where available.
Sakana Fugu-Ultra v1.1 is priced at $5.00 input / $30.00 output per 1M tokens, versus $0.00 input / $0.00 output per 1M tokens for Sarvam 105B. Sakana Fugu-Ultra v1.1 has the larger context window at 1M, compared with 128K for Sarvam 105B.
Operational comparison
Runtime and commercial metrics are compared only when both models have a complete sourced value.
| Metric | Sakana Fugu-Ultra v1.1 | Sarvam 105B | Comparison |
|---|---|---|---|
| Input / output priceUSD per 1M tokens | Sakana Fugu-Ultra v1.1$5 input / $30 output | Sarvam 105B$0 input / $0 output | Sarvam 105B has the lower combined listed price. |
| Generation speedtokens per second | Sakana Fugu-Ultra v1.1Not available | Sarvam 105BNot available | A complete speed comparison is not available. |
| First-answer latencyseconds to first token | Sakana Fugu-Ultra v1.1Not available | Sarvam 105BNot available | A complete latency comparison is not available. |
| Context windowmaximum listed tokens | Sakana Fugu-Ultra v1.11M | Sarvam 105B128K | Sakana Fugu-Ultra v1.1 lists the larger context window. |
Benchmark Deep Dive
Agentic1 benchmarks
| Benchmark | Sakana Fugu-Ultra v1.1 | Sarvam 105B | Result |
|---|---|---|---|
| τ²-bench resultsSource | — | 46.8% | Not comparable |
Coding1 benchmarks
| Benchmark | Sakana Fugu-Ultra v1.1 | Sarvam 105B | Result |
|---|---|---|---|
| AA-SciCodeSource | — | 26.4% | Not comparable |
Reasoning2 benchmarks
Knowledge6 benchmarks
| Benchmark | Sakana Fugu-Ultra v1.1 | Sarvam 105B | Result |
|---|---|---|---|
| Artificial Analysis Intelligence IndexSource | — | 11.9% | Not comparable |
| AA-GPQA DiamondSource | — | 73.8% | Not comparable |
| AA-HLESource | — | 10.1% | Not comparable |
| AA-Omniscience IndexSource | — | -59.5% | Not comparable |
| AA-Omniscience AccuracySource | — | 17.6% | Not comparable |
| AA-Omniscience Hallucination RateSource | — | 93.5% | Not comparable |
Inst. Following1 benchmarks
| Benchmark | Sakana Fugu-Ultra v1.1 | Sarvam 105B | Result |
|---|---|---|---|
| AA-IFBenchSource | — | 34.4% | Not comparable |
Frequently Asked Questions (3)
Can I compare Sakana Fugu-Ultra v1.1 and Sarvam 105B on BenchLM yet?
Not fully yet. BenchLM is tracking both models, but the sourced benchmark breakdown for this comparison is still coming soon.
Why does this comparison show “coming soon”?
BenchLM only shows category winners and benchmark-level calls when we have sourced results that can be compared fairly. For these models, the public benchmark coverage is not complete enough yet.
What data is available for Sakana Fugu-Ultra v1.1 and Sarvam 105B today?
Sakana Fugu-Ultra v1.1: $5.00 input / $30.00 output per 1M tokens Sarvam 105B: $0.00 input / $0.00 output per 1M tokens Both model pages still include creator, context window, reasoning mode, and other metadata while benchmark coverage fills in.