2. Bundesliga· Season 2025
Match Summary
Lubeck-Schwartau defeated Oppenweiler/Backnang 37:18. The match was played in 2. Bundesliga 2025. League standings: Lubeck-Schwartau #8, Oppenweiler/Backnang #18.
Rivalry since 2025
Lubeck-Schwartau vs Oppenweiler/Backnang Head to Head Results· 1
Lubeck-Schwartau and Oppenweiler/Backnang have met 1 times — Lubeck-Schwartau won 1, Oppenweiler/Backnang won 0, with 0 draws. Their rivalry dates back to 2025. Lubeck-Schwartau leads the head-to-head with 1 victory from 1 meeting. A combined 62 goals have been scored across these fixtures, averaging 62.00 per match (35 for the home side, 27 for the visitors). Both teams scored in 1 match (100%). Over 2.5 goals landed in 1 game (100%), making it a fixture that tends to produce goals. The highest-scoring encounter finished 27–35 in 2025.
Recent Meetings
Standings
Lubeck-Schwartau sit #8 and Oppenweiler/Backnang are #18 in the 2. Bundesliga table heading into this match.
2. Bundesliga - Regular Season
| # | GP | Won | Lost | Pts | |
|---|---|---|---|---|---|
| #1 | Bietigheim-Metterzimmern | GP31 | Won25 | Lost3 | Pts53 |
| #2 | HBW Balingen-Weilstetten | GP31 | Won25 | Lost5 | Pts51 |
| #3 | Elbflorenz | GP31 | Won21 | Lost8 | Pts44 |
| #4 | Potsdam | GP31 | Won19 | Lost7 | Pts43 |
| #5 | Nordhorn-Lingen | GP32 | Won20 | Lost10 | Pts42 |
| #6 | Hagen | GP31 | Won20 | Lost10 | Pts41 |
| #7 | Dessauer | GP31 | Won16 | Lost13 | Pts34 |
| #8 | Lubeck-Schwartau | GP31 | Won14 | Lost12 | Pts33 |
| #9 | N-Lubbecke | GP31 | Won13 | Lost13 | Pts31 |
| #10 | Coburg 2000 | GP31 | Won14 | Lost15 | Pts30 |
| #11 | Huttenberg | GP32 | Won13 | Lost16 | Pts29 |
| #12 | Dormagen | GP31 | Won9 | Lost17 | Pts23 |
| #13 | Grosswallstadt | GP31 | Won10 | Lost18 | Pts23 |
| #14 | Ferndorf | GP31 | Won9 | Lost18 | Pts22 |
| #15 | Ludwigshafen | GP31 | Won10 | Lost19 | Pts22 |
| #16 | Essen | GP31 | Won7 | Lost19 | Pts19 |
| #17 | Krefeld | GP31 | Won6 | Lost19 | Pts18 |
| #18 | Oppenweiler/Backnang | GP31 | Won0 | Lost29 | Pts2 |
Statistics are for informational purposes only. Past performance does not guarantee future results.
API data: 23 May 2026