Paedophile with 88 offences breaches harm prevention order
Summarised from 2 outlets · Updated 18 Nov, 18:38 · Archive
Richard Smith, 33, admitted breaching a sexual harm prevention order by using secret online accounts and aliases.
Richard Smith, 33, admitted breaching a sexual harm prevention order (SHPO) after using secret online accounts and aliases to access chat rooms. The Norwich resident, on the sex offenders' register, failed to notify police that he had used a Motorola phone to access EhChat, a messaging service, and posed under the assumed profile name 'Kelsey' on Telegram.
An unannounced police inspection at his home address in May 2025 led to him disclosing the smartphone. Analysis of his search history showed he had accessed chat rooms. Prosecutor Sally Harris told Norwich Magistrates' Court that the recent history of similar offences meant the case fell outside the court's sentencing powers.
Smith pleaded guilty to breach of the SHPO and failing to comply with notification requirements. He has previously been convicted of child sex offences in 2019, 2021 and 2023, the last conviction resulting in more than three years in jail for possession of extreme abuse images and videos. Magistrates committed him to be sentenced at Norwich Crown Court on 15 January.
How it is being reported
- Paedophile with record of 88 offences is caught againNorwich paedophile Richard Smith, with 88 previous offences, admitted breaching a sexual harm prevention order after using secret online accounts and aliases.Norwich Evening News · 18 Nov, 18:00
- Paedophile with record of 88 offences is caught againNorwich paedophile Richard Smith, with 88 previous offences, admitted breaching a sexual harm prevention order after using secret online accounts and aliases.Eastern Daily Press · 18 Nov, 18:00
In this story: Richard Smith · Norwich Magistrates' Court · Norwich Crown Court · Norwich
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)