Menu

Yeovil Town vs Nottingham Forest

26 October 2013 at 15:00Huish Park Stadium, Yeovil, Somerset

Match Summary

Yeovil Town defeated Nottingham Forest 3:1. The match was played in Championship 2013.

Rivalry since 2014

Yeovil Town vs Nottingham Forest Head to Head Results· 1

Yeovil Town and Nottingham Forest have met 1 times — Yeovil Town won 0, Nottingham Forest won 1, with 0 draws. Their rivalry dates back to 2014. Nottingham Forest leads the head-to-head with 1 victory from 1 meeting. A combined 4 goals have been scored across these fixtures, averaging 4.00 per match (1 for the home side, 3 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 3–1 in 2014.

Total goals
4 · 4.0/match
Both scored
1/1 · 100%
Over 2.5
1/1 · 100%

Recent Meetings

02/02/14Championship
Match Details
Highest-scoring game: 31 v 2014

Recent Form

WWonDDrawnLLost

In their last 6 matches, Yeovil Town have recorded 1 win, 1 draw and 4 defeats. Nottingham Forest show 2 wins, 2 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: Yeovil Town

Away Record: Nottingham Forest

W 238D 205L 247
Over 2.545
Goals scored860

Data: football-data.co.uk

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

API data: 14 May 2026