Advertisement
UK markets closed
  • FTSE 100

    7,529.35
    +75.60 (+1.01%)
     
  • FTSE 250

    18,408.65
    +175.18 (+0.96%)
     
  • AIM

    716.29
    +2.51 (+0.35%)
     
  • GBP/EUR

    1.1673
    +0.0083 (+0.72%)
     
  • GBP/USD

    1.2714
    +0.0086 (+0.68%)
     
  • Bitcoin GBP

    30,536.13
    +519.30 (+1.73%)
     
  • CMC Crypto 200

    802.76
    +11.20 (+1.41%)
     
  • S&P 500

    4,594.63
    +26.83 (+0.59%)
     
  • DOW

    36,245.50
    +294.61 (+0.82%)
     
  • CRUDE OIL

    74.38
    -1.58 (-2.08%)
     
  • GOLD FUTURES

    2,091.70
    +34.50 (+1.68%)
     
  • NIKKEI 225

    33,431.51
    -55.38 (-0.17%)
     
  • HANG SENG

    16,830.30
    -212.58 (-1.25%)
     
  • DAX

    16,397.52
    +182.09 (+1.12%)
     
  • CAC 40

    7,346.15
    +35.38 (+0.48%)
     

Swans cause disruption for south-west London commuters for second day in a row

Swans have been causing a mischief  (ES)
Swans have been causing a mischief (ES)

Train passengers have been disrupted by a swan on the line for a second day in a row.

South Western Railway said “a swan on the line” is affecting services in south-west London between Clapham Junction and Wimbledon.

This issue caused a number of services to be cancelled and delayed on Thursday morning.

One of the affected passengers was reportedly a judge who was late for a hearing at Guildford Crown Court.

It comes a day after South Western Railway was disrupted by a swan on the line between Kingston and Hampton Wick, also in south-west London.

Asked on social media platform X - formerly known as Twitter - if the same swan was responsible for both incidents, the operator replied: “no I don’t think so”.

In June, a major section of the £19 billion Elizabeth line between Heathrow Airport in west London and Abbey Wood in south-east London was blocked because of a swan.

Reports of animals on train tracks usually lead to services being stopped or running at reduced speeds.

South Western Railway services were also disrupted on Thursday by a points failure at Woking, Surrey and a signalling fault between Bournemouth, Dorset and Brockenhurst, Hampshire.