Rust Holds TIOBE Top 10 for Third Straight Month in 2026

What happened

Rust has held its place at No. 10 in the TIOBE Programming Community Index for September 2026, marking a third consecutive month inside the index's top 10 since the language first broke through in July 789. Its rating slipped to 1.34%, down from a stronger reading the prior month, yet that figure is still 0.33 percentage points higher than a year earlier, when Rust sat at No. 18 17. TIOBE's own Rust-specific page confirms that August 2026 marked the language's highest position since tracking began in 2011, underscoring how recent this milestone actually is 10.

The rest of the September top 10 held remarkably steady. Python remains No. 1 despite falling below 18% for the first time in this data, C climbed to No. 2, and C++ slipped to No. 3 while widening its percentage-point lead over fourth-place Java 178. SQL and R both moved up without changing the shape of the top 10, and TIOBE's own editorial commentary spent as much energy on Julia's push back toward the top 20 and the reentry of Ada and Objective-C into the top 20 as it did on Rust 11.

What makes Rust's hold notable is how thin its margin is. Fortran sits directly behind it at No. 11 with a 1.24% rating — just a tenth of a percentage point separating a decades-old scientific-computing language from one of the industry's most talked-about newer entrants 178. Go and Delphi/Object Pascal trail just behind that, meaning a single month of shifting search activity could bump Rust back out of the top 10 as easily as it arrived 7.

Why Rust is climbing at all

TIOBE's CEO, Paul Jansen, attributed Rust's original breakthrough into the top 10 to its dual focus on memory safety and execution speed, framing it as a direct challenger to C and C++ — languages he said continue to struggle with the risks of manual memory management even as their communities work on safety improvements 9. That framing lines up with independent government guidance: a CISA report and a joint NSA/CISA cybersecurity information sheet both describe Rust's ownership and borrow-checker model as a way to catch memory and concurrency bugs at compile time without relying on a garbage collector, and both list Rust among the memory-safe languages organizations are encouraged to adopt for new code 1314.

That guidance also points to concrete precedent: Android's engineering team prioritized Rust and Java for new development after memory-safety bugs were found responsible for the majority of the platform's vulnerabilities in memory-unsafe code 14. That kind of real-world adoption gives Rust's TIOBE placement more substance than a pure popularity contest might otherwise carry.

The enthusiasm-versus-usage gap

Separate developer surveys reinforce that Rust inspires unusual loyalty without yet claiming mainstream market share. Stack Overflow's 2025 developer survey found Rust-adjacent tooling dominating its "admired" rankings, with the Rust-built Python package manager uv topping the list and Rust's own build tool, Cargo, rated the most admired infrastructure tool of the year 1718. The Rust project's own 2025 community survey drew more than 7,000 responses and pointed to steady hiring interest and growing codebases, tempered by respondents' persistent worry that the language is becoming more complex 19. JetBrains' 2025 ecosystem survey adds texture to that picture: 65% of respondents use Rust for hobby projects, 52% are still learning it, and only 26% use it professionally — a mix that signals curiosity and experimentation running well ahead of routine commercial deployment 20.

That gap is exactly what an earlier I-Programmer analysis flagged as a risk. After Rust dropped to No. 16 in an earlier month, Jansen suggested the language's adoption might be plateauing, floating the idea that Rust's difficulty for non-expert programmers could cap its growth even as specialists in performance-critical fields keep investing in it 12. The same piece traces Rust's TIOBE history back to 2020, when it first cracked the top 20, and notes that a top-10 breakthrough was expected within a couple of years — a prediction that took roughly six years to materialize 12.

Where the reporting agrees

Every outlet covering the September index — TechRepublic, InfoWorld, TIOBE itself, and I-Programmer's retrospective — agrees on the core numbers: Rust at No. 10 with a 1.34% rating, Fortran close behind at No. 11 with 1.24%, and a top 10 that is otherwise unchanged from August 1789. There's also consistent agreement on the mechanism behind Rust's appeal: memory safety paired with performance, positioned as a challenge to C and C++'s dominance in systems programming 91314. And the surveys converge on a shared theme even though they measure different things — Stack Overflow, the Rust project, and JetBrains all describe a language that generates outsized enthusiasm and hiring interest relative to how many developers actually use it day to day in production 17181920.

Where it doesn't

The clearest divergence is tonal rather than factual. InfoWorld's coverage of Rust's original July arrival in the top 10 reads as a breakthrough story, leaning on Jansen's quotes about Rust out-competing C and C++ 9. TechRepublic's September piece, by contrast, treats the same top-10 slot as an open question, emphasizing the razor-thin gap to Fortran and describing the position as unsettled rather than secured 8. TIOBE's own monthly write-up barely dwells on Rust at all, spending its editorial attention on Julia's push toward the top 20 and the reappearance of Ada and Objective-C — suggesting that, from TIOBE's own vantage point, Rust holding steady isn't this month's most interesting development 11.

There's also a genuine trend disagreement buried in the timeline. I-Programmer's April-era reporting describes Rust falling to No. 16 with a declining rating and floats the idea that its adoption was plateauing 12. That is difficult to reconcile at first glance with the same language reaching an all-time-high No. 10 just a few months later. The most plausible reading is not that either account is wrong, but that Rust's TIOBE trajectory has been genuinely volatile — dips followed by rapid gains — rather than a smooth, uninterrupted climb. TIOBE's ranking methodology, based on relative search-hit shares across 25 search engines, makes this kind of non-linear movement more likely, since a language's rank can shift even without much change in its own raw numbers, depending on what competitors around it are doing 1516.

The reading the evidence supports

Taken together, the record supports a measured conclusion rather than a triumphant one. Rust has crossed a real and durable-enough threshold — three straight months in TIOBE's top 10 is not a fluke, and it lines up with genuine strategic momentum in security-conscious engineering circles, from Android's internal prioritization of Rust to NSA and CISA's formal endorsement of memory-safe languages 1413. But the margin over Fortran is too thin, and the survey data showing hobbyist and learner majorities too consistent, to call this a mainstream arrival. Rust's position looks less like domination and more like a language that has earned a seat at the table while still working out how to get more of its admirers into production seats.