Ontologia

Ruisseau

Tegeler Fließ

Crosses 3 administrative regions : Barnim, Berlin, Oberhavel

ruisseau

Total length

26km

Max discharge

0,3m³/s

Max Strahler

2

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080363370388 km²

3 administrative regions crossed (GADM L2)

  • Oberhavel
    Brandenburg · Germany
    4.3 km
    in this dpt
  • Berlin
    Berlin · Germany
    1.1 km
    in this dpt
  • Barnim
    Brandenburg · Germany
    0.2 km
    in this dpt

13 intersecting protected areas

4 more protected areas

1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.

Species present

1 746 distinct species · 11 762 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Tegeler Fließ : 36 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 85 interactions GloBI sur 6 types (connectance 9.4%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
85
Connectance
0.094
Patrimoniales
1
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

26km

Max discharge

0,3m³/s

Max Strahler

2

Segments matched

1

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.