2. Bundesliga· Season 2021
Match Summary
Coburg 2000 defeated Ludwigshafen 32:31. The match was played in 2. Bundesliga 2021. League standings: Coburg 2000 #11, Ludwigshafen #13.
Rivalry since 2015
Coburg 2000 vs Ludwigshafen Head to Head Results· 12
Coburg 2000 and Ludwigshafen have met 12 times — Coburg 2000 won 6, Ludwigshafen won 5, with 1 draws. Their rivalry dates back to 2015. Coburg 2000 leads the head-to-head with 6 victories from 12 meetings. A combined 727 goals have been scored across these fixtures, averaging 60.58 per match (368 for the home side, 359 for the visitors). Both teams scored in 12 matches (100%). Over 2.5 goals landed in 12 games (100%), making it a fixture that tends to produce goals. The highest-scoring encounter finished 40–28 in 2025.
Recent Meetings
Standings
Coburg 2000 sit #11 and Ludwigshafen are #13 in the 2. Bundesliga table heading into this match.
Regular Season
| # | GP | Won | Lost | Pts | |
|---|---|---|---|---|---|
| #1 | Gummersbach | GP38 | Won31 | Lost7 | Pts62 |
| #2 | Hamm-Westfalen | GP38 | Won22 | Lost11 | Pts49 |
| #3 | Eisenach | GP38 | Won23 | Lost14 | Pts47 |
| #4 | Huttenberg | GP38 | Won21 | Lost13 | Pts46 |
| #5 | Nordhorn-Lingen | GP38 | Won23 | Lost15 | Pts46 |
| #6 | Bietigheim-Metterzimmern | GP38 | Won19 | Lost16 | Pts41 |
| #7 | Hagen | GP38 | Won18 | Lost15 | Pts41 |
| #8 | Essen | GP38 | Won19 | Lost16 | Pts41 |
| #9 | Elbflorenz | GP38 | Won18 | Lost15 | Pts41 |
| #10 | Lubeck-Schwartau | GP38 | Won17 | Lost19 | Pts36 |
| #11 | Coburg 2000 | GP38 | Won16 | Lost19 | Pts35 |
| #12 | Dessauer | GP38 | Won15 | Lost18 | Pts35 |
| #13 | Ludwigshafen | GP38 | Won14 | Lost18 | Pts34 |
| #14 | Rimpar | GP38 | Won17 | Lost21 | Pts34 |
| #15 | Rostock | GP38 | Won14 | Lost20 | Pts32 |
| #16 | Dormagen | GP38 | Won13 | Lost20 | Pts31 |
| #17 | Grosswallstadt | GP38 | Won13 | Lost21 | Pts30 |
| #18 | Ferndorf | GP38 | Won13 | Lost21 | Pts30 |
| #19 | Aue | GP38 | Won10 | Lost22 | Pts26 |
| #20 | Emsdetten | GP38 | Won9 | Lost24 | Pts23 |
Statistics are for informational purposes only. Past performance does not guarantee future results.
API data: 11 May 2026