K League 1 shots table 2026
South Korea · 194 of 198 league matches counted; the rest have no shot data · latest match 24 October 2026
- Most shots: Gangwon (13.59 per match). Fewest conceded: Gangwon (9.03 per match).
- Best conversion: Seoul, 14.4% of shots scored.
| # | Team | Table | MP | Shots | On target | Against | On target against | Diff | Goals | Conv. % |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Gangwon | 5 | 32 | 13.6 | 4.6 | 9.0 | 3.2 | +4.6 | 37 | 8.5 |
| 2 | Seoul | 1 | 32 | 13.0 | 4.9 | 9.5 | 3.2 | +3.5 | 60 | 14.4 |
| 3 | Jeonbuk | 4 | 32 | 13.6 | 4.7 | 11.2 | 3.9 | +2.3 | 42 | 9.7 |
| 4 | Incheon | 6 | 32 | 11.0 | 3.8 | 9.5 | 3.8 | +1.5 | 41 | 11.6 |
| 5 | Daejeon | 3 | 33 | 12.7 | 4.3 | 11.6 | 4.3 | +1.2 | 53 | 12.6 |
| 6 | Ulsan HD | 2 | 33 | 13.3 | 4.8 | 12.2 | 4.1 | +1.1 | 52 | 11.8 |
| 7 | Gimcheon Sangmu | 10 | 32 | 11.8 | 3.6 | 10.8 | 3.6 | +1.1 | 33 | 8.7 |
| 8 | Jeju SK | 7 | 33 | 12.8 | 4.2 | 12.0 | 4.1 | +0.8 | 39 | 9.2 |
| 9 | Pohang | 9 | 32 | 10.2 | 3.3 | 11.8 | 3.9 | −1.6 | 29 | 8.9 |
| 10 | Anyang | 8 | 33 | 10.2 | 3.5 | 13.9 | 4.6 | −3.7 | 40 | 11.9 |
| 11 | Bucheon FC 1995 | 11 | 32 | 10.2 | 3.6 | 14.8 | 4.5 | −4.6 | 32 | 9.8 |
| 12 | Gwangju FC | 12 | 32 | 9.6 | 3.5 | 15.8 | 5.7 | −6.3 | 30 | 9.8 |
Order = shot difference per match. Shots, on target and against are per match.
How this table is made
Shots come from third-party data providers. Conversion is goals per 100 shots, over the matches counted. This season has no xG table because too few of its matches carry xG.
League-phase matches only: play-offs and promotion ties are left out, so a club's numbers can sit beside its place in the table. A season appears here only when at least 80% of its matches have the data.
Use this table
Free to use. If you publish these numbers, please credit Football Charts with a link:
<a href="https://www.football-charts.com/leagues/south-korea/k-league-1/shots-table">K League 1 shots table 2026, Football Charts</a>Match-by-match shots and passes and historical odds are on the paid API plans and in the data archive.