Birmingham City v Stockport County team news: Davies and Challinor name line-ups in EFL League One
and on Freeview 262 or Freely 565
Chris Davies has made 10 changes from the 2-1 win against Blackpool on Sunday. Krystian Bielik is the only player that keeps his place in the side.
From the team named, it looks like it will be a 4-2-3-1. Ben Davies and Christoph Klarer will be the two centre-backs and then Bielik and Alex Cochrane will play at full-back. Tomoki Iwata and Paik Seung-ho will play alongside each other in midfield with Keshi Anderson, Willum Willumsson and Jay Stansfield playing just behind the striker Alfie May.
Advertisement
Hide AdAdvertisement
Hide AdChairman of the Board Tom Wagner is in attendance along with Chief Executive Officer Garry Cook. A big crowd is expected at St. Andrew's @ Knighthead Park, with the Fan Park opened to supporters before the game.
As for the opposition they make just one change from their last league outing. Ibou Touray comes in for the suspended Fraser Horsfall. Sam Hughes is not among the substitutes, but Jack Diamond is back in after missing the last three matches.
Stockport have Louis Barry in their starting XI, and he is on loan from Birmingham’s fiercest rivals Aston Villa. Barry leads the scoring charts in the division with 13 goals in 17 games, but there are rumours that he could be recalled in January.
Birmingham City vs Stockport County team news
Birmingham City XI: Allsop, Bielik, Klarer, Davies, Cochrane, Paik, Iwata, Anderson, Willumsson, Stansfield, and May.
Advertisement
Hide AdAdvertisement
Hide AdBirmingham City subs: Peacock-Farrell, Laird, Gardner-Hickman, Leonard, Harris, Dykes, and Jutkiewicz.
Stockport County XI: Hinchcliffe, Touray, Bate (C), Southam-Hales, Collar, Pye, Connolly, Wootton, Barry, Rydel, and Norwood.
Stockport County subs: Addai, Hughes, Diamond, Camps, Olaofe, Bailey, and Adaramola.
Comment Guidelines
National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.