Rivière· 3 segments
Ammerbach
Crosses 3 administrative regions : Amberg, Amberg-Sulzbach, Dingolfing-Landau
Total length
31km
Max discharge
166,4m³/s
Max Strahler
5
Segments matched
3
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- Amberg-SulzbachBayern · Germany7.9 kmin this dpt
- AmbergBayern · Germany6.1 kmin this dpt
- Dingolfing-LandauBayern · Germany2.7 kmin this dpt
6 intersecting protected areas
Untere Isar zwischen Landau und Plattling
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Landscape Protection Area
Vils von Vilseck bis zur Mündung in die Naab
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Unteres Isartal zwischen Niederviehbach und Landau
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Ammerbachtal
IUCN VLandscape Protection Area
Ammerthal
IUCN VLandscape Protection Area
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
912 distinct species · 4 972 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 28 species (selected proportionally per kingdom among those with at least one documented interaction here) to keep the graph readable. Hover for details, click to explore the full ecosystem of a species.
ℹ️ The territory contains many more species than displayed and all their documented interactions: the graph is intentionally the structural skeleton (top-N species by composite local score, edges filtered by Serrano 2009 disparity filter α=0.2).
Indicateurs du tissu écologique
Tissu écologique de Ammerbach : 21 espèces reliées par 35 interactions GloBI sur 5 types (connectance 8.6%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
31km
Max discharge
166,4m³/s
Max Strahler
5
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.