Soul swing of 8,152
Team soul advantage moved from +6,516 to -1,636 (lost 8,152). In the same window your team lost a Walker, a Walker.
| Metric | Trend | Recent values | This match | Vs median |
|---|---|---|---|---|
| Economy rank in lobby | #5, #3, #10, #6, #8 | #10 | worse than #6 | |
| Deaths | 8, 6, 7, 9, 12 | 8 | worse than 6 | |
| Deaths after 12 min | 5, 4, 6, 7, 12 | 6 | worse than 4 | |
| Player damage | 45,333, 48,329, 36,837, 26,675, 60,062 | 45,741 | better than 39,354 | |
| Objective damage | 5,205, 11,564, 8,190, 4,535, 6,422 | 4,249 | worse than 6,289 | |
| Souls at 10 min | 5,210, 7,730, 5,766, 6,788, 5,984 | 6,206 | better than 6,018 | |
| Kill participation | 46.2%, 54.7%, 52.3%, 83.3%, 43.2% | 76.0% | better than 54.7% | |
| Last hits | 104, 142, 128, 114, 139 | 122 | worse than 168 |
Statistical analysis was generated successfully - the full match breakdown is below.
Positive means your team was ahead in total souls. Sampled at 10 points the API provides; the line between samples is interpolated.
Team soul advantage moved from +6,516 to -1,636 (lost 8,152). In the same window your team lost a Walker, a Walker.
Team soul advantage moved from -1,636 to -16,286 (lost 14,650). In the same window your team lost a Walker; you died 2x.
Team soul advantage moved from -16,286 to -22,386 (lost 6,100). In the same window your team took a Walker; you died 2x.
You died at 31:12 with the team advantage at -22,386 souls. Within 90s your team lost: Base objective at 31:13, Base objective at 31:39. This sequence coincided with the objective loss; the data cannot show whether it caused it.
You died at 34:55 with the team advantage at -22,386 souls. Within 90s your team lost: Patron at 35:45. This sequence coincided with the objective loss; the data cannot show whether it caused it.
Team soul advantage moved from -22,386 to -46,999 (lost 24,613). In the same window your team lost a Base objective, a Base objective; you died 2x.
17 purchases · 33,600 souls spent, in order.
Context around each of your deaths. The API does not expose map awareness or vision, so no positioning claims are made.