You know how it is. You’re sitting there, watching the news, and some pundit is blabbing about who’s gonna win the next big match. And you think, man, this guy just uses his gut feeling. I figured I could build something better, something based on cold, hard history.
/https%3A%2F%2Fsportsmole-media-prod.s3.gra.io.cloud.ovh.net%2F24%2F46%2Frebin-sulaka.jpeg)
The whole thing started last month. My cousin, Ali, always acts like he’s got the inside scoop on Gulf football. He kept swearing that this specific Kuwait vs Iraq match was a done deal for Iraq, just because of some recent friendly result. I told him to shut up. Recent friendlies mean jack squat. I decided I was going to engineer the truth.
The Data Gathering: The Nightmare Before the Numbers
My first step? Gathering the statistics. I didn’t want the last five games; I wanted everything. Every damn match they played against each other since the 90s. This wasn’t easy. You’d think FIFA or some national league site would have a clean sheet ready to go. Nope. I spent three full evenings just digging around on various sketchy Arabic sports forums and historical archives.
What I gathered was messy, man. Really messy. I needed to nail down a few key variables for my spreadsheet:
- Head-to-Head (H2H) results: Wins, Losses, Draws.
- Average goals scored and conceded in the last 10 official competitive matches (ignoring friendlies, because they’re useless).
- Home/Away split bias (which team performs better when technically playing ‘at home’ in neutral venues).
- Discipline index (how many yellow and red cards they pick up—a high number means instability under pressure).
I manually entered maybe 80 data points into Excel. My fingers were cramping up. It felt like I was back in college doing some dumb project, but this time, the stakes were bragging rights, which are way more important than a degree.
Building the Black Box: My “Expert Analysis” System
I tossed out the idea of using some fancy Python library. Too much hassle, too many dependencies. I just needed a reliable weighting system. So I built a simple logic tree in Excel, assigning specific weights to the stats that I personally believed mattered most.

This is where the “expert analysis” part comes in.
I weighted the H2H results at 40%. Because history tends to repeat itself, right? If one team consistently owns the other, that’s a big deal. Then I put 30% on recent scoring form (the last 10 competitive matches). The remaining 30% I split between the discipline index and the venue bias.
I created a scoring system. Every time Kuwait scored higher than Iraq in a weighted category, they got a point for that category. Then I normalized the final scores to give me a single predicted victory probability percentage for each side.
I started pumping the numbers through. The initial results were all over the place. I realized my discipline index was too harsh. It was penalizing teams too much for stupid fouls in dead matches. I went back and tweaked the weights.
I reduced the weight of the Discipline Index from 15% down to 5%, and moved those 10 percentage points over to the H2H record, making history now 50% of the prediction. My reasoning? Teams get carded frequently in high-stakes matches anyway; it cancels out. Long-term dominance is what truly matters.

The Prediction and the Real-World Slap
Once the system was tuned, I ran the final simulation. The output was clear, spitting out the result in ugly, slightly green text on my screen.
Prediction: Kuwait 58% probability of victory. Iraq 42% probability.
I felt like a genius. I immediately texted Ali the final score before the game even started: “Kuwait by a clear margin. History dictates it.” I felt smug. I had spent countless hours crunching numbers, building my own statistical framework, proving that my brain was better than his gut.
Then the game happened.
I watched the first half. Kuwait looked sluggish. Iraq looked hungry. The Discipline Index? Iraq was fouling everyone, but they were also generating incredible chances. My system, focused on historical dominance and conservative scoring rates, completely missed the current dynamic energy and motivation of the team on the rise.

Final score: Iraq won 2-1.
Ali didn’t even need to text me back. He just sent a screenshot of the final score, followed by a crying-laughing emoji.
What did I learn? That numbers don’t always capture sheer momentum or the tactical genius of a new coach. I built a perfect historical predictor, but I forgot that football is played by human beings right now, not by spreadsheets. My system was robust, meticulously built, and absolutely wrong. But hey, the process was damn fun. And now I know exactly which variables I need to start tracking for the next prediction model—variables like ‘recent coaching changes’ and ‘stomach bug reports’. Because apparently, those matter more than 30 years of history.
