Football fieldDownload×
Arrow image
English Football League One2026.01.01 / 15:00

Reading vs Burton Match Betting – Odds, Live Updates and Stats – 2026/01/01

2
Finished
-
0

English Football League One 2026/01/01 | 15:00:00

Chatroom

1
Hide chat

Player's profile picture

Show chat

Stats

Reading logo
Reading
Burton
Burton logo
Ball Possession
52%
48%
19
Total Shots
6
8
Blocked shots
2
5
Corner Kicks
3
2
Offsides
4
0
Yellow Cards
0
449
Total Passes
410
13
Key Passes
6
355 (79%)
Accurate Passes
316 (77%)
6 (50%)
Accurate Crosses
3 (16%)
37 (32%)
Accurate Long Balls
25 (30%)
10
Tackles
12
15
Interceptions
4
31
Clearances
12
2
Saves
2
12
Total Shots
4
7
Blocked shots
2
2
Corner Kicks
3
1
Offsides
1
0
Yellow Cards
0
243
Total Passes
200
8
Key Passes
4
196 (81%)
Accurate Passes
152 (76%)
4 (67%)
Accurate Crosses
1 (8%)
18 (35%)
Accurate Long Balls
15 (31%)
6
Tackles
3
3
Interceptions
4
18
Clearances
6
1
Saves
1
7
Total Shots
2
1
Blocked shots
0
3
Corner Kicks
0
1
Offsides
3
0
Yellow Cards
0
206
Total Passes
210
5
Key Passes
2
159 (77%)
Accurate Passes
164 (78%)
2 (33%)
Accurate Crosses
2 (29%)
19 (30%)
Accurate Long Balls
10 (29%)
4
Tackles
9
12
Interceptions
0
13
Clearances
6
1
Saves
1

Match Info

About The Match

Reading vs Burton started on 2026/01/01 at 15:00:00 UTC in Madejski Stadium as part of English Football League One.

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

Match Details
Event: English Football League One
Name: Reading vs Burton
Date: 2026/01/01
Time: 15:00:00 UTC
Referee: Tom Reeves
Stadium: Madejski Stadium
Stadium capacity: 24161
Weather: Sunny
Air pressure: 756mmHg
Temperature: 5°C
Wind speed: 6.1m/s
Air humidity: 81%
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.