Home/ Michigan/ Kent County/ Long Lake
Stocked last season

Long Lake Fish Stocking

Kent County, Michigan · 1987 to 2005 on record

According to MDNR records, Long Lake has 9 stocking records on file across 1 species. The most recent stocking season represented is 2005.

Long Lake stocking
Long Lake photo
replace with photo
9
Stocking records
36,659
Fish reported stocked
1
Species
2005
Latest season

Stocking activity by season

9 seasons on record, most in the 2005 (1 records). Click a bar to jump to that season below.

1 records
2005 · 5,388 fish
1987
1990
1994
1995
1996
1998
2000
2003
2005

Stocking records per season (labelled by the season's end year). Michigan's source reports by season, so records aren't broken out by month.

Most-stocked species

Walleye 9 records

Location

Exact coordinates not yet available · Kent County

Map not available yet
We don't have coordinates for this water on file.

Stocking history

Values shown exactly as the agency reported them; species names are normalized for search.

SpeciesFish stockedSizePhase
Walleye 5,388 1.08" avg · Muskegon strain —

A stocking record does not guarantee fish remain present or may legally be harvested. Check current Michigan fishing regulations →

Quick facts

Latest season 2005
Most stocked Walleye
Species Walleye
County Kent
Seasons on record 1987 – 2005
Fish reported 36,659
Coordinates —

Data source

Compiled from public records published by the Michigan Department of Natural Resources. StockedSpots is independent and not affiliated with or endorsed by MDNR.

Source: Michigan Department of Natural Resources (MDNR). Data last checked September 1, 2026.
View MDNR source →

Frequently asked questions

MDNR records show Long Lake stocked with Walleye.

See something that looks off?

Every stocking record on StockedSpots is pulled directly from official state wildlife agency sources — you can see exactly where each state's data comes from on our data sources page. If a record looks wrong, or you'd like a page reviewed or removed, let us know and we'll look into it.

Report an issue →