bitterandblue.sbnation.com

Manchester City v Brighton: Gut Feelings

Manchester City entertain Brighton as they attempt to secure a Champions League spot for next season.

The Blues are one point ahead of the visitors and victory for Brighton at the Etihad Stadium will see the Seagulls leapfrog City into fifth place. In fact, if results go against them, Pep Guardiola’s side could find themselves in 8th place by the end of the weekend.

It’s a nightmare scenario that none of the Faithful could have predicted at the start of the season and there is the hope that the Blues can turn it around as they head towards the season’s end.

As usual, our team are here to give us their views and predictions on how the match will go. Here’s what we think this week.

Saul

Tough matchup. At home vs an in form club, that is roaring as we head to the end of the season. Slight City win here, with Haaland getting back in the scoring sheet. 2-1.

City 2-1 Brighton

Will

Why have City become so difficult to predict? They could win 4-0, they could lose 4-0. That’s not an overstatement.

As I tend to, I’ll go somewhere in the middle. A City win, but not without vulnerabilities.

City 3-1 Brighton

Thomas

City host Brighton in a ln important match for European places. City at home are always a good bet, and I back them to handle the Seagulls.

City 2-0 Brighton

Pete

A few years ago I would have gone for a 4-0 win at least in this fixture but now, I’m not so sure. Brighton are an excellent side and will cause City problems. There may be some goals in this match but not all to the Blues.

City 3-2 Brighton

What Happened Against Forest

City slumped to a ninth league defeat of the season, an unprecedented total for a Guardiola side.

Only Saul picked up any points from last Saturday when he correctly predicted the goal difference, so he gets two points. All the rest of us should have seen it coming but we live in hope that we were wrong. And, as usual with City right now, it’s the hope that kills you.

Here’s the table:

Read full news in source page