68/100

Moderate evidence

GainPublished recordBusinessGood Space

AI helps UK economy grow at fastest pace for more than two years

Truvace record
TRV-2026-2633raw data (JSON)
Version
v1Published
First published
Evidence type
Official statistics
Sources
1 sourceJournalism
sha256
83203de8c0f1…check it

The UK economy grew by 0.7% in the third quarter, its fastest expansion in two and a half years, as the rollout of AI services increased activity. The Office for National Statistics reported that the economy “grew robustly” in the July to September quarter, almost entirely due to strong and widespread growth in the services sector, led by the IT sector. The quarterly growth rate matched economists’ expectations, and was the fastest recorded since the first three months of 2024, when GDP also rose by 0.7%. In a b…

The gain

The ONS reported UK GDP grew 0.7% in July to September 2026, the fastest in two and a half years, with the IT sector growing 2.1% and AI and cloud businesses reporting the largest turnover increases.

What this doesn’t fix

Economists cautioned that growth may not last: the Resolution Foundation said resilience will be severely tested by rising inflation and interest rates, and ING noted IT output actually fell through August and September.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-12

Cite this record

v1

Truvace Impact Record TRV-2026-2633, v1: “AI helps UK economy grow at fastest pace for more than two years.” Truvace, 2026-11-12. /record/TRV-2026-2633 (accessed on the day you copy it). sha256 83203de8c0f1b8e0…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv183203de8c0f1…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2633 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.