Alteration: 10:49 from Bristol Temple Meads.
10:49 Bristol Temple Meads to Westbury due 11:42 will be started from Great Malvern and terminated at Bristol Temple Meads.
It will no longer call at Keynsham, Oldfield Park, Bath Spa, Freshford, Avoncliff, Bradford-On-Avon, Trowbridge and Westbury but will call additionally at Malvern Link, Worcester Foregate Street, Worcester Shrub Hill, Ashchurch-for-Tewkesbury, Cheltenham Spa, Gloucester, Cam & Dursley, Yate, Bristol Parkway, Filton Abbey Wood, Stapleton Road and Lawrence Hill.
This is due to engineering works not being finished on time.
How can it be an "alteration" - isn't it a different train?
Well, there is a Great Malvern-Westbury train in the normal timetable (2F97), though recently the work at Bath (which isn't in the Thames Valley, is it?) has led to it being changed and part-cancelled. Today's has now been reinstated as per the normal working, but JourneyCheck reads:
Alteration: 10:49 from Bristol Temple Meads.
10:49 Bristol Temple Meads to Westbury due 11:42 will be started from Great Malvern.
It will call additionally at Malvern Link, Worcester Foregate Street, Worcester Shrub Hill, Ashchurch-for-Tewkesbury, Cheltenham Spa, Gloucester, Cam & Dursley, Yate, Bristol Parkway, Filton Abbey Wood, Stapleton Road and Lawrence Hill.
This is due to a problem currently under investigation.
However, it has vanished from Realtime Trains, at least in Bristol.
I guess the software (probably "assisted" by some soft but also warm and sqidgy ware) has tried to match the new service to one in the current timetable (whatever that means) and got confused by the way it has been messed about.