M25 Traffic Chaos: Multi-Vehicle Collision Causes Long Delays
A severe multi-vehicle collision on the M25 has caused lengthy delays and congestion, with travel time estimates exceeding 40 minutes. The incident occurred on the anti-clockwise carriageway between junctions 16 and 15, with all lanes temporarily closed. National Highways traffic officers have been deployed to the scene, and the incident has resulted in approximately 6 miles of congestion. As of 7:47am, the average speed was reported to be only 10 mph, with severe delays of 53 minutes and increasing.
Key Takeaways:
- A multi-vehicle collision occurred on the M25 anti-clockwise carriageway between junctions 16 and 15, causing lane closures and extended delays.
- National Highways traffic officers were dispatched to the scene to manage the incident and restore traffic flow.
- As of 7:47am, the average speed on the affected section of the M25 was approximately 10 mph, with severe delays of 53 minutes and increasing.
- The incident caused approximately 6 miles of congestion, with travel time estimates exceeding 40 minutes.
- Police have confirmed that all lanes have been reopened, but delays of 45 minutes remain, making it necessary for drivers to allow extra time for their journeys.
- The South Central Ambulance Service, Thames Valley Police, and RBFRS were contacted in response to the incident.
Statistics:
- All lanes on the M25 anti-clockwise carriageway between junctions 16 and 15 were temporarily closed due to the multi-vehicle collision.
- The incident resulted in approximately 6 miles of congestion.
- As of 7:47am, the average speed on the affected section of the M25 was approximately 10 mph.
- Travel time estimates exceeded 40 minutes.
- Delays were reported to be 40 minutes and afterward increased to 45 minutes.
- The collision was a multi-vehicle incident.
Sources:
- National Highways: East (@HighwaysEAST) tweet on July 1, 2025 at 8:13am
- National Highways: East (@HighwaysEAST) tweet on July 1, 2025 at 8:44am
- National Highways: East (@HighwaysEAST) tweet on July 1, 2025 at 7:44am