Glynde, Firle, Beddingham and Southease vs Imberhorne and Baldwins
Side-by-side crime comparison: safety scores, categories and trends.
Glynde, Firle, Beddingham and Southease vs Imberhorne and Baldwins Results
Key Statistics (last 12 months)
Crime by Category (last 12 months)
Number of crimes per category — lower is better
Safest Nearby Neighbourhoods
Check Also
Frequently Asked Questions
Is Glynde, Firle, Beddingham and Southease safer than Imberhorne and Baldwins?
Glynde, Firle, Beddingham and Southease has a safety score of 75/100 (Safe) and recorded 147 crimes in the last 12 months. Imberhorne and Baldwins has a safety score of 54/100 (Average) with 429 crimes. Glynde, Firle, Beddingham and Southease scores higher on the CrimeRadar safety index.
What is the crime trend in Glynde, Firle, Beddingham and Southease vs Imberhorne and Baldwins?
Glynde, Firle, Beddingham and Southease shows a year-on-year crime trend of -7% — meaning total crimes fell compared to the same period the prior year. Imberhorne and Baldwins shows -18.6% (falling). A downward trend is a positive sign for an area.
What types of crime are most common in Glynde, Firle, Beddingham and Southease and Imberhorne and Baldwins?
In Glynde, Firle, Beddingham and Southease, the most recorded crime category over the last 12 months is Violent Crime (57 incidents). In Imberhorne and Baldwins, it is Violent Crime (121 incidents). The full breakdown by category is shown in the chart above.
How does anti-social behaviour compare between Glynde, Firle, Beddingham and Southease and Imberhorne and Baldwins?
Glynde, Firle, Beddingham and Southease recorded 17 anti-social behaviour incidents in the last 12 months, while Imberhorne and Baldwins recorded 76. Anti-social behaviour includes rowdiness, nuisance and disorder that disrupts daily life but may not result in a criminal charge.
How do violent crime levels compare in Glynde, Firle, Beddingham and Southease vs Imberhorne and Baldwins?
Violent crime in Glynde, Firle, Beddingham and Southease totalled 57 incidents over the last 12 months, compared to 121 in Imberhorne and Baldwins. Violent crime includes assault with and without injury, harassment, and public order offences.
How many crimes were recorded in Glynde, Firle, Beddingham and Southease and Imberhorne and Baldwins in the previous year?
In the 12 months prior to the most recent period, Glynde, Firle, Beddingham and Southease recorded 158 crimes (now 147, a change of -7%). Imberhorne and Baldwins recorded 527 crimes previously (now 429, -18.6%).
What is the resolution rate for crimes in Glynde, Firle, Beddingham and Southease and Imberhorne and Baldwins?
The resolution rate is the percentage of recorded crimes that resulted in a formal outcome — such as a charge, caution, penalty notice, or community resolution. Glynde, Firle, Beddingham and Southease has a resolution rate of 28.6% and Imberhorne and Baldwins has 28.1%. A higher rate indicates police are more frequently resolving reported crimes in that area.
Which police force covers Glynde, Firle, Beddingham and Southease and Imberhorne and Baldwins?
Glynde, Firle, Beddingham and Southease falls within the Sussex Police boundary. Imberhorne and Baldwins is covered by Sussex Police. Each force operates independently and publishes crime data through the national UK Police API.
What data is used to compare Glynde, Firle, Beddingham and Southease and Imberhorne and Baldwins?
CrimeRadar uses 36 months of official recorded crime data from the UK Police API, updated each month. The safety score combines crime volume relative to the force average, year-on-year trend direction, and resolution rate. All figures are based on crimes recorded within each police-defined neighbourhood boundary.
Can I see Glynde, Firle, Beddingham and Southease or Imberhorne and Baldwins on a crime map?
Yes — CrimeRadar has individual crime map pages for both Glynde, Firle, Beddingham and Southease and Imberhorne and Baldwins. You can view interactive maps, monthly trends and hotspot locations by visiting each neighbourhood's full statistics page linked above.