Menu

Gillingham vs Yeovil Town

16 August 2014 at 15:00MEMS Priestfield Stadium, Gillingham, Kent

Match Summary

Gillingham defeated Yeovil Town 2:0. The match was played in League One 2014.

Rivalry since 2014

Gillingham vs Yeovil Town Head to Head Results· 2

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

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

Recent Meetings

21/02/15League One
Match Details
12/08/14League Cup
Match Details
Highest-scoring game: 22 v 2015

Recent Form

WWonDDrawnLLost

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

W 185D 163L 239
Over 2.550
Goals scored704

Away Record: Yeovil Town

Data: football-data.co.uk

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

API data: 14 May 2026