Football fieldDownload×
Arrow image
YBC Levain Cup2023.06.18 / 09:00

Nagoya Grampus vs Sanfrecce Hiroshima Match Betting – Odds, Live Updates and Stats – 2023/06/18

YBC Levain Cup 2023/06/18 | 09:00:00

Chatroom

1
1 Participant(s)
Hide chat

Player's profile picture

Show chat

Stats

Nagoya Grampus logo
Nagoya Grampus
Sanfrecce Hiroshima
Sanfrecce Hiroshima logo
Ball Possession
54%
46%
10
Total Shots
11
Shots off target
Shots on target
5
5
6
5
0
Blocked shots
0
3
Corner Kicks
3
0
Offsides
0
2
Yellow Cards
2
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
0
Shots off target
Shots on target
0
0
0
0
0
Blocked shots
0
0
Corner Kicks
0
0
Offsides
0
0
Yellow Cards
0
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
10
Total Shots
11
Shots off target
Shots on target
5
5
6
5
0
Blocked shots
0
3
Corner Kicks
3
0
Offsides
0
2
Yellow Cards
2
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

Nagoya Grampus vs Sanfrecce Hiroshima started on 2023/06/18 at 09:00:00 UTC in Toyota Stadium as part of YBC Levain Cup.

On SportScore you can watch and track Nagoya Grampus vs Sanfrecce Hiroshima 's live score, timeline, odds and lineups as well as review competition standings and H2H.

Match Details
Event: YBC Levain Cup
Name: Nagoya Grampus vs Sanfrecce Hiroshima
Date: 2023/06/18
Time: 09:00:00 UTC
Stadium: Toyota Stadium
Stadium capacity: 45000
Weather: Overcast
Air pressure: 755mmHg
Temperature: 23°C
Wind speed: 2.9m/s
Air humidity: 62%
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.