League Two

Newport County 2–1 Grimsby

Final score · Half-time 0–0 · All of yesterday's results

Our backtest says that, with the sharp market making Grimsby the most likely outcome at 54% (fair odds 1.86), Unibet (SE) offered 1.97, a gap of +5.9% above the fair price (Strong value). This was reconstructed on 26 September 2026, not recorded at the time. Recent form — Newport County: DDLLD; Grimsby: WWDDD.

After the whistle

Match stats

Match statsNewport CountyGrimsby
Possession %3367
Shots1011
Shots on target53
Corners73
Yellow cards22
Red cards00
Fouls149
Offsides27
Goalkeeper saves33

What the market said before kick-off

  • Newport County win 24% happened
  • Draw 25% did not happen
  • Grimsby win 50% did not happen
  • Over 2.5 goals 52% happened
  • Both teams score 55% happened

Pinnacle closing price with the margin removed, next to what happened. It is the market's view, not a tip: an outcome priced at 30% happens about 3 times in 10.

Venue: Rodney Parade, Newport

Next matches

Line-ups, events and match stats: API-Football.

Starting line-ups

Newport County 4-2-3-1

  1. J. Wright GK
  2. C. Norman DF
  3. L. Jenkins DF
  4. K. Cameron DF
  5. M. Jacob DF
  6. M. Dibley-Dias MF
  7. C. Brennan MF
  8. M. Adu-Poku MF
  9. H. Biggins MF
  10. S. Gwengwe MF
  11. C. Doidge FW

Grimsby 4-1-4-1

  1. C. Pym GK
  2. H. Rodgers DF
  3. M. Kacurri DF
  4. C. McJannet DF
  5. J. Sweeney DF
  6. M. Shelton MF
  7. F. Cartwright MF
  8. K. Green MF
  9. J. Walker MF
  10. C. Vernam MF
  11. Iwan Morgan FW

Regular starters not in the XI

  • Géza Dávid Turi — not in the starting XI (started 5 of the last 5)

Not in the XI does not mean injured: it can be rotation, a suspension or a knock. We only compare with the team's last 5 line-ups.

Pinnacle, margin removed (home / draw / away): 23 / 26 / 52% when the line-ups came out, 24 / 25 / 50% at kick-off.

In the big leagues, line-up news is usually already in the price by the time it is official.

The most likely result is not the same as value: value is where a bookmaker pays more than the fair price, and the two can point to different outcomes.

Value opportunity before kick-off Strong value

2 Grimsby @ 1.97
Bookmaker Unibet (SE)
Price observed
Rule would have fired (backtest) @ 1.97 (Unibet (SE)) · backtest — reconstructed afterwards
Market 1X2 (match result)
Availability and exact price varied by country and over time.
Fair price 1.86
Unibet (SE) 1.97
Confidence: High
Value-bet result Lost · 2 -1.00u

Market discrepancy: before kick-off, Grimsby (2) was priced at 1.97 by a soft bookmaker, above the fair price of 1.86 — a +5.9% gap. An observation about the price, not an instruction to bet.

A single result where a bookmaker pays above the fair price — separate from the main prediction below.

Most likely result

2 Away win 58%
1X2
Sharp, recorded19%23%58%
Other estimates
Our model23%24%53%

Sharp, recorded = Pinnacle when we logged the match (it can be days old). Our model = our own estimate, which on average predicts worse than the market.

Fair odds of the pick (as recorded) 1.73
Sharp odds recorded for this prediction (Pinnacle) 4.64 / 3.83 / 1.66
Market Gap +5.9%
Confidence High
Model agreement High

Confidence reflects only the sharp probability of the selection: high from 50%, medium from 40%, low below. It says how likely the result is, not how big the price gap is. Model agreement shows how close our own model is to the sharp market on this selection — when it is Low, the market and our model disagree, so treat the flag with more caution.

Prediction result Lost · 1

Value lifecycle Settled

Would have been flagged (backtest) ·
2 Grimsby · soft 1.97 (Unibet (SE)) · fair 1.86 · edge +5.9%
Opening sharp
1.66
At close
1.99 · CLV -1.1%
Result
Lost -1.00u Backtest

“Detected” is the moment the flag was first shown on the site and written to our ledger (recorded live since 26 September 2026). For earlier matches the flag was reconstructed afterwards from the prices we had stored, and the time shown is when the rule would have fired: a backtest, not a live record. When the gap closes, we say so instead of pretending the value is still there.

Match context

The last 4 head-to-head meetings we tracked split 0–2–2 (Newport County wins – draws – Grimsby wins).

Newport County scored 0.8 and conceded 1.2 across their last 5 matches in our results database; Grimsby scored 2 and conceded 1.2 in 5.

Since opening around 1.66, the sharp market price on Grimsby has drifted to 1.99 — the market has moved against this outcome.

These figures come from our own tracked results and odds snapshots for this fixture — not from a generic stats feed.

Market-relevant trends

Newport County is winless in its last 5 matches.
No value Already reflected in the fair price — no value on Newport County here.
Grimsby has won its last 2 matches.
✓ And the market hasn't fully priced it in: value flagged on Grimsby at +5.9% above fair.

We show the trend and whether it is already in the price. Most sites show the streak and let you assume you should bet it.

Why this price?

Newport County
D D L L D
avg 0.8 scored · 1.2 conceded (last 5)
Grimsby
W W D D D
avg 2 scored · 1.2 conceded (last 5)
Recent head-to-head
07 Feb 2026 Newport County 0–0 Grimsby
16 Aug 2025 Grimsby 2–1 Newport County
22 Mar 2025 Grimsby 1–0 Newport County
16 Nov 2024 Newport County 0–0 Grimsby

Recent form and head-to-head from our settled results — context behind the fair price. The price itself comes from the sharp market, not from these alone.

Public, timestamped record

Logged before kick-off
Prediction record
Pick 2 · Away win
Odds recorded for the prediction 1.66
Closing odds 1.93
Prediction CLV -14.0%
Result Lost
Value-bet record

Backtest: reconstructed on 26 September 2026 by applying today’s rule to the prices stored before kick-off. It was not shown in this form at the time; its seal was created at the reconstruction, which for matches already played was after the match.

Value selection 2 · Grimsby
Odds when the rule would have fired (reconstructed) 1.97
Fair odds 1.86
Closing odds 1.99
Value CLV -1.1%
Profit (units) -1.00
Result Lost
Prediction hash — integrity fingerprint 99ff44789d86b9b6

This hash fingerprints the prediction as recorded: teams, kick-off time, our model probabilities, the Pinnacle prices recorded for it (at logging or, if there were none, the first quoted after logging and before kick-off, which can be written in after the match) and the log time. A later edit to any of them would change it (a rescheduled kick-off changes it too). It does not cover closing prices, the result or the value-bet record above; value flags recorded live have their own seal in the public record. Verify in the public record →

Every day a snapshot of the full public record is published to a public Git repository and timestamped with OpenTimestamps. Timestamped snapshots are never overwritten and the Git history shows any difference, so a later change to a past row is visible by comparing two snapshots. The corrections file lists the corrections we announced. Verify on the public log →

Since 20 June 2026 the public record is snapshotted daily (07:40 Bucharest time: 04:40 UTC in summer time, 05:40 UTC in winter) to an external log. A prediction is externally timestamped before kick-off only if it was in a snapshot taken before the match; predictions logged on match day, or whose Pinnacle price was added after logging, first appear there after kick-off. Value flags have been recorded live only since 26 September 2026; earlier value flags were reconstructed on that date.

Methodology

The fair price comes from the sharp market itself: we strip the margin from Pinnacle-style odds — the most accurate public predictor in existence — and use our calibrated Elo + form model as a cross-check and as the fallback where no sharp price exists. Value is flagged only where a softer bookmaker prices a selection above that fair price, never on long shots (implied probability under 30%), and never beyond a plausible band. Most of the time there is no value — and we say so.

Found this useful? Send it to a friend who bets.