PoliceCensus

Home / States / Connecticut / Seymour Police Department

Seymour Police Department

City agency in Naugatuck Valley Planning Region, Connecticut, United States. Reports crime data to the FBI, and has done since 2009.

ORI
CT0012400
Type
City
County
Naugatuck Valley Planning Region
State
Connecticut (CT)
FBI reporting
Reporting since 2009-01-01
Location
41.3975, -73.0727

Workforce

As reported to the FBI for 2025, covering a population of 17,248.

41Sworn officers
1Civilian staff
2.44Employees per 1,000 people
17,248Population served
YearOfficersCiviliansPopulation servedPer 1,000
202541117,2482.44
202440217,0342.47
202341216,8462.55
202238216,6342.40
202137216,3062.39
202040316,4262.62
201941216,5052.61
201837216,5892.35
201739216,5552.48
201641216,4622.61
201543216,5372.72
201440216,5792.53

Officer and civilian counts are full-time employees as filed by the agency in its annual return. A dash means the agency did not report that figure for that year — it does not mean zero.

Deaths during encounters with this agency

3 people have died during an encounter with Seymour Police Department between 2004 and 2012, according to Mapping Police Violence.

3Deaths recorded
17.39Per 100,000 people policed
2004–2012Period covered
Recorded causeDeaths
Gunshot2
Vehicle1

What this figure is and is not. It counts deaths recorded as occurring during an encounter with this agency. It is not a finding of wrongdoing, and a death being recorded here says nothing about whether it was lawful. Many involve armed confrontations; some involve none. Police Census publishes counts only and does not name the people who died.

These records are compiled from news reports and public records by Mapping Police Violence, an independent research organisation — they are not official statistics, and no federal database records this comprehensively. Used with permission.

Assaults on officers

Officers of Seymour Police Department assaulted in the line of duty, by the weapon reported, between 1995 and 2023. These are the FBI’s own weapon categories.

Weapon reportedOfficers assaulted
Firearm0
Knife or other cutting instrument0
Hands, fists or feet27
Other weapon3
YearFirearmKnifeHands, fists, feetOther
19950001
19960030
19970020
19990010
20000020
20010010
20020010
20030011
20040011
20080010
20110060
20140010
20150010
20160020
20170030
20230010

Why there is no single total here. The FBI publishes two breakdowns of the same assaults — by weapon, and by how the officer was deployed — and nationally they do not agree: the assignment columns sum to 1,869,337 and the weapon columns to 1,744,852, and the two match on only 84% of rows. Police Census publishes the weapon breakdown as the FBI states it rather than picking one basis and calling it ‘the total’. The file’s ‘cleared’ column is not shown either: it sums higher than the assaults themselves, so it is not a subset of what is above and we have not established what it counts.

This comes from the FBI’s Law Enforcement Officers Killed and Assaulted programme. Despite the name, the file carries no officers-killed data at all — those columns are empty for every agency and every year, so this page reports assaults only and says nothing about officers killed.

LEOKA identifies agencies by name, not by the ORI used elsewhere on this site. A row was attached only where exactly one agency in that state reduces to the same base name; 78.7% of rows matched nationwide. An agency with nothing here may have reported no assaults, or may be one of the names that did not match — Police Census does not guess which.

Also policing Naugatuck Valley Planning Region

Jurisdictions overlap. These agencies are also recorded against the same county, so a single address may be covered by more than one of them.

Source

Agency identity, type, jurisdiction, coordinates and reporting status are as published by the FBI Crime Data Explorer, agency record CT0012400. Police Census reproduces these values without adjustment. Where the FBI publishes nothing, this page says so rather than estimating.

Believe something on this page is wrong? Tell us — every correction is published on Corrections.