Menu

VfB Stuttgart vs TSV 1860 Munich

21 October 2016 at 17:30Mercedes-Benz Arena, Stuttgart
Referee: Arne Aarnink

Match Summary

VfB Stuttgart defeated TSV 1860 Munich 2:1. The match was played in 2. Bundesliga 2016.

Rivalry since 2017

VfB Stuttgart vs TSV 1860 Munich Head to Head Results· 2

VfB Stuttgart and TSV 1860 Munich have met 2 times — VfB Stuttgart won 1, TSV 1860 Munich won 0, with 1 draws. Their rivalry dates back to 2017. VfB Stuttgart leads the head-to-head with 1 victory from 2 meetings. A combined 4 goals have been scored across these fixtures, averaging 2.00 per match (3 for the home side, 1 for the visitors). Both teams scored in 1 match (50%). Over 2.5 goals landed in 0 games (0%), making it a fixture that tends to produce goals. The highest-scoring encounter finished 0–2 in 2023.

Total goals
4 · 2.0/match
Both scored
1/2 · 50%
Over 2.5
0/2 · 0%

Recent Meetings

29/07/23Friendlies Clubs
Match Details
Highest-scoring game: 02 v 2023

Recent Form

WWonDDrawnLLost

In their last 6 matches, VfB Stuttgart have recorded 2 wins, 3 draws and 1 defeat. TSV 1860 Munich show 1 win, 3 draws and 2 losses from their last 6 outings.

Betting Odds & Historical Data

Opening pre-match odds recorded for this fixture at the time it was played. These are historical figures for analytical reference only and do not reflect any current market.

Historical data only — not for betting

This data is sourced from football-data.co.uk and covers historical match results and pre-match odds. These figures do not represent current or live odds and cannot be used for placing bets. Betting is not possible on this website. Provided for analytical and research purposes only.

Home Record / Away Record

Aggregated season statistics from all available historical data. Use these to assess each team's overall form, scoring frequency, and tendency for high-scoring matches.

Home Record: VfB Stuttgart

W 38D 13L 17
Over 2.560
Goals scored125

Away Record: TSV 1860 Munich

Data: football-data.co.uk

Statistics are for informational purposes only. Past performance does not guarantee future results.

API data: 14 May 2026