Sunday 7 August 2011

MTU Vs Bangkok Glass preview



Games between heavyweights MTU and BG are usually fought out to a good standard and have produced very mixed results over the last three seasons. In the 2009 season, BG looked to be heading for the TPL title until a late surge by The Quilins - including a win over the 'Glass Rabbits' at home - saw it snatched away.

Since then, BG have never really fulfilled their potential despite an early season 1-0 win at home to Muangthong in 2010, though that was avenged in a 2-0 home win for the champs later on. This season MTU forced a draw at the LEO Stadium.

How have things been since then? Well Glass' very own superhero BG Man told me:


For Bangkok Glass, it's been a similar season in many respects as MTU's. A very poor start and some shock losses have been decently overcome to reach the midway point in a fairly respectable position. Performances have ranged from the sublime to the ridiculous and until a season long consistency is found, BG wont be challenging for any trophies. However, the signs are finally there that things seem to be heading in the right direction both on and off the pitch.


MTU still have selection problems. Captain  Nattaporn is very likely to be absent again following his mystery health problem last week. Datsakorn will most likely take the armband again in Oat's absence. Panupong is in with a chance of a return, though Diarra held his own against Thai Port last Saturday. Christian looks to be returning to fitness too, as his goal at Port showed.

Muangthong are still defending an undefeated home league streak that threatens to span over two full seasons. The well supported, well-financed BG will be one of the bigger threats to that potential achievement.

2 comments:

  1. Howdy. The OS has the game set for 18:00 and 19:30. The TPL site says 19:30. Any guesses?

    ReplyDelete
  2. Hi Ben, you never can be sure of course but our midweek games are usually 1930/1945 affairs. The game was originally scheduled for a weekend match, which would be a 1800 kick off. Perhaps someone forgot to edit the time on the OS.

    ReplyDelete