Football fieldDownload×
Arrow image
Russian Cup2024.04.03 / 13:00

Ural Yekaterinburg vs Lokomotiv Moscow Match Betting – Odds, Live Updates and Stats – 2024/04/03

Russian Cup 2024/04/03 | 13:00:00

Chatroom

1
1 Participant(s)
Hide chat

Player's profile picture

Show chat

Stats

Ural Yekaterinburg logo
Ural Yekaterinburg
Lokomotiv Moscow
Lokomotiv Moscow logo
Ball Possession
43%
57%
1
Total Shots
9
Shots off target
Shots on target
0
1
5
4
0
Blocked shots
0
11
Corner Kicks
7
0
Offsides
0
4
Yellow Cards
4
0
Total Passes
0
0
Key Passes
0
0
Accurate Passes
0
0
Accurate Crosses
0
0
Accurate Long Balls
0
0
Tackles
0
0
Interceptions
0
0
Clearances
0
2
Total Shots
5
Shots off target
Shots on target
0
2
3
2
0
Blocked shots
0
6
Corner Kicks
5
0
Offsides
0
1
Yellow Cards
1
0
Total Passes
0
0
Key Passes
0
0
Accurate Passes
0
0
Accurate Crosses
0
0
Accurate Long Balls
0
0
Tackles
0
0
Interceptions
0
0
Clearances
0
0
Total Shots
4
Shots off target
Shots on target
0
0
2
2
0
Blocked shots
0
5
Corner Kicks
2
0
Offsides
0
3
Yellow Cards
3
0
Total Passes
0
0
Key Passes
0
0
Accurate Passes
0
0
Accurate Crosses
0
0
Accurate Long Balls
0
0
Tackles
0
0
Interceptions
0
0
Clearances
0

Match Info

About The Match

Ural Yekaterinburg vs Lokomotiv Moscow started on 2024/04/03 at 13:00:00 UTC in Central Stadium as part of Russian Cup.

On SportScore you can watch and track Ural Yekaterinburg vs Lokomotiv Moscow 's live score, timeline, odds and lineups as well as review competition standings and H2H.

Match Details
Event: Russian Cup
Name: Ural Yekaterinburg vs Lokomotiv Moscow
Date: 2024/04/03
Time: 13:00:00 UTC
Stadium: Central Stadium
Stadium capacity: 35696
Weather: Partially cloudy
Air pressure: 763mmHg
Temperature: 13°C
Wind speed: 6.1m/s
Air humidity: 53%
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.