Cliftonville reach County Antrim Shield final with 3-0 win
Summarised from 2 outlets · 5 reports · Updated 4 Nov, 16:20 · Archive
Cliftonville beat Bangor 3-0 in the County Antrim Shield semi-final, with three first-half goals.
Cliftonville beat Bangor 3-0 in the County Antrim Shield semi-final, with a dominant first-half performance that saw them score three goals. The Reds' display was described as a 'football lesson' and a 'fantastic' performance by manager Jim Magilton as they reached their fifth final under his tenure.
The News Letter reports that Cliftonville assistant manager Gerard Lyttle was pleased with striker Brian Healy's continued form. Healy scored in the match and Lyttle described him as 'a talented boy' deserving the rewards for his commitment and hard work.
How it is being reported
- 'He's a talented boy': Cliftonville coach delight as star striker gets deserved goal rewards for hard yardsCliftonville assistant manager Gerard Lyttle insists star striker Brian Healy is now getting the rewards his hard work deserves after continuing a purple patch of form by scoring to help the Reds reach another Co Antrim Senior Shield final.News Letter · 4 Nov, 15:23
- Clinical Cliftonville cruise into County Antrim Shield final: ‘It was a football lesson’Belfast Telegraph · 4 Nov, 11:03
- Cliftonville blitz Bangor with three first-half goals to reach fifth final under Jim Magilton: ‘Tonight was fantastic’Cliftonville 3 Bangor 0Belfast Telegraph · 3 Nov, 22:54
- First-half whirlwind sees Cliftonville storm in County Antrim Shield Final at Bangor’s expenseCliftonville 3 Bangor 0Belfast Telegraph · 3 Nov, 21:58
- ‘It sets it up perfectly’: Cliftonville boss believes winning weekends have laid platform for tasty semi-final showdown with BangorBelfast Telegraph · 2 Nov, 21:00
In this story: Cliftonville · Bangor · Jim Magilton · Gerard Lyttle · Brian Healy · County Antrim
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)