Football fieldDownload×
Arrow image
FA Cup2026.01.09 / 19:30

Wrexham vs Nottingham Forest Match Betting – Odds, Live Updates and Stats – 2026/01/09

10
Finished
-
9

FA Cup 2026/01/09 | 19:30:00

Chatroom

1
Hide chat

Player's profile picture

Show chat

Stats

Wrexham logo
Wrexham
Nottingham Forest
Nottingham Forest logo
Ball Possession
40%
60%
14
Total Shots
18
2
Blocked shots
7
6
Corner Kicks
4
2
Offsides
0
0
Yellow Cards
2
361
Total Passes
539
14
Key Passes
11
288 (80%)
Accurate Passes
468 (87%)
5 (29%)
Accurate Crosses
8 (31%)
21 (31%)
Accurate Long Balls
36 (47%)
20
Tackles
10
9
Interceptions
9
27
Clearances
10
7
Saves
4
5
Total Shots
3
1
Blocked shots
1
3
Corner Kicks
2
0
Offsides
0
0
Yellow Cards
0
202
Total Passes
256
5
Key Passes
2
164 (81%)
Accurate Passes
217 (85%)
1 (11%)
Accurate Crosses
3 (33%)
10 (32%)
Accurate Long Balls
15 (45%)
9
Tackles
6
7
Interceptions
4
11
Clearances
8
1
Saves
0
9
Total Shots
15
1
Blocked shots
6
3
Corner Kicks
2
2
Offsides
0
0
Yellow Cards
2
159
Total Passes
283
9
Key Passes
9
124 (78%)
Accurate Passes
251 (89%)
4 (50%)
Accurate Crosses
5 (29%)
11 (30%)
Accurate Long Balls
21 (49%)
11
Tackles
4
2
Interceptions
5
16
Clearances
2
6
Saves
4

Match Info

About The Match

Wrexham vs Nottingham Forest started on 2026/01/09 at 19:30:00 UTC in Racecourse Ground as part of FA Cup.

On SportScore you can watch and track Wrexham vs Nottingham Forest 's live score, timeline, odds and lineups as well as review competition standings and H2H.

Match Details
Event: FA Cup
Name: Wrexham vs Nottingham Forest
Date: 2026/01/09
Time: 19:30:00 UTC
Referee: Paul Tierney
Stadium: Racecourse Ground
Stadium capacity: 15500
Weather: Partially cloudy
Air pressure: 756mmHg
Temperature: 3°C
Wind speed: 2.9m/s
Air humidity: 93%
Lost connection to chat server. Reconnecting in {connect_timeout} seconds...
Failed to load script from server. Parts of the site might not function properly.
Check your connection and try refreshing the page. If this persists, file a support ticket
Failed to load page from server.
Check your connection and try again.