Menu

Yeovil Town vs AFC Wimbledon

12 September 2015 at 15:00Huish Park Stadium, Yeovil, Somerset

Match Summary

Yeovil Town and AFC Wimbledon drew 1:1. The match was played in League Two 2015.

Rivalry since 2016

Yeovil Town vs AFC Wimbledon Head to Head Results· 2

Yeovil Town and AFC Wimbledon have met 2 times — Yeovil Town won 2, AFC Wimbledon won 0, with 0 draws. Their rivalry dates back to 2016. Yeovil Town leads the head-to-head with 2 victories from 2 meetings. A combined 7 goals have been scored across these fixtures, averaging 3.50 per match (5 for the home side, 2 for the visitors). Both teams scored in 1 match (50%). Over 2.5 goals landed in 1 game (50%), making it a fixture that tends to produce goals. The highest-scoring encounter finished 2–3 in 2016.

Drawn
0
·
Total goals
7 · 3.5/match
Both scored
1/2 · 50%
Over 2.5
1/2 · 50%

Recent Meetings

05/12/17EFL Trophy
Match Details
30/01/16League Two
Match Details
Highest-scoring game: 23 v 2016

Recent Form

WWonDDrawnLLost

In their last 6 matches, Yeovil Town have recorded 1 win, 1 draw and 4 defeats. AFC Wimbledon show 1 win, 0 draws and 5 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: Yeovil Town

Away Record: AFC Wimbledon

W 126D 104L 138
Over 2.544
Goals scored451

Data: football-data.co.uk

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

API data: 14 May 2026