Danish Geodata Agency bathymetry, measured-only fishing spots, DTU Øresund-region fish evidence, seasonal forage and public shore-use leads for Køge Bay.
2 live sections1 on quality hold2 survey-backed depth maps8 cataloged target species12 official access records
Built for useful map scale
Why Køge Bay is split up
Three latitudinal children keep the 500-square-kilometre bay below the page-scale gate and preserve the weaker source mix at Stevns as a transparent hold.
86,356-acre Køge Bay — North Denmark saltwater fishing map with official Danish Geodata Agency 50 m bathymetry, measured-only fishing spots, DTU-supported fish targets, seasonal forage guidance and public shore-access context. Northern Køge Bay from the Copenhagen approaches toward the middle bay, with sand bars, harbor edges and Oresund exchange.
Recorded max
52 ft
Species
Sea Trout, Atlantic Herring, European Flounder, Garfish
51,893-acre Køge Bay — Middle Denmark saltwater fishing map with official Danish Geodata Agency 50 m bathymetry, measured-only fishing spots, DTU-supported fish targets, seasonal forage guidance and public shore-access context. Middle Køge Bay around Køge, with measured sand-bottom contours, harbor approaches and current-facing points.
Recorded max
81 ft
Species
Sea Trout, Atlantic Herring, European Flounder, Garfish
These named sections are part of Køge Bay but did not pass the release gate, so they have no public map yet.
Stevns — The official Denmark Depth Model is 44.72% directly source-backed in this water-only child, below the fixed 60% release floor; provider interpolation remains identified and no coverage waiver is applied.
Choose with the evidence visible
How to compare Køge Bay sections
The released set contains 2 survey-backed sections and 0 modeled sections. Their published maximum depths run from 52 to 81 ft, with a median of 81 ft. Those numbers make scale differences visible, but they do not make sections interchangeable: contour provenance, access, species evidence and local structure remain specific to each child map.
Start with the section closest to the water you actually plan to fish. Then compare its depth-data label and species roster with an adjacent section before treating a pattern as system-wide. A survey-backed child is the stronger choice for precise breakline planning; a modeled child is broader reconnaissance and should be checked against sonar and conditions on the water. Return to this overview whenever you cross into another mapped reach, pool or coastal section.
Same child-page contract
What every section keeps separate
Depth provenance: each child discloses whether its contours are survey-backed or modeled; a family card never upgrades that label.
Fishing spots: structure and seasonal recommendations are calculated inside the child boundary so distant reaches are not mixed together.
Fish species: each page keeps its own supported roster rather than inheriting every species found anywhere in the parent system.
Local context: hatch guidance, access, hazards, catches and nearby-water links continue to resolve for the individual child where data is available.
Planning questions
Frequently asked questions
Why is Køge Bay divided into separate fishing maps?
Three latitudinal children keep the 500-square-kilometre bay below the page-scale gate and preserve the weaker source mix at Stevns as a transparent hold.
Are these depth maps survey-backed?
2 released maps use surveyed or official agency bathymetry. Each child keeps its own provider, product, datum and not-for-navigation disclosure.
Do fish and access records apply everywhere?
No. Species, forage, access and fishing spots remain scoped to each child map and retain their evidence labels.
