Counter-Strike: LPH Gaming vs UNiTY esports (BO3) - United21 Group B
The conditions, incentives and evidence that could shape the answer.An old fixture with an open statistical contract
The Counter-Strike: LPH Gaming vs UNiTY esports (BO3) fixture was dated June 2, 2026. An eligible Map 1 odd/even kills contract remains open in the October 4 data at 50% on each side. This is an outstanding-settlement explainer, not a preview of a future match. [1]
For the exact contract “Map 1: Odd/Even Total Kills?”, our October 4 observation was Odd 50%; Even 50%. These are recorded contract prices, not an official result. The parent event’s cumulative volume was $102,001; that turnover includes other constituent contracts and is not the volume of this selection alone. [1]
The detail that changes the question
For this Map 1 kill-parity proposition, a remade game replaces the abandoned version for settlement. Combining both versions would produce the wrong count even if the arithmetic itself were correct. [1]
What would strengthen or weaken the case
Odd is supported only if the recognised combined kill count for Map 1 is an odd integer. For example, a hypothetical total of 101 would be odd and 102 would be even; these are illustrations, not reported match statistics.
A round score, winning team or combined deaths figure cannot safely substitute for the required count. Friendly-fire kills and self-inflicted deaths are excluded, while qualifying overtime kills are included. [1]
The evidence that will settle it
The contract counts both teams’ qualifying kills in Map 1, including overtime, then settles Odd or Even. If the map is remade, only the remade game counts. The designated record is HLTV; credible reporting can be used if it has no final result within two hours. [3]
The seven-day postponement window from June 2 reaches June 9, 2026, which has passed. Cancellation, no kills, an unplayed map or delay beyond that window produces 50–50 under the rules. No settlement cause is inferred from the open API status. [3]
WEIGH BOTH SIDES
What would change the outlook?
Map 1: Odd total kills
Quoted market evidence: Oct 4, 2026, 09:57 UTC. The live market panel may show a newer observation.
Odd is supported only if the recognised combined kill count for Map 1 is an odd integer. For example, a hypothetical total of 101 would be odd and 102 would be even; these are illustrations, not reported match statistics.
A round score, winning team or combined deaths figure cannot safely substitute for the required count. Friendly-fire kills and self-inflicted deaths are excluded, while qualifying overtime kills are included. [1]
The next signals to watch
The Odd side of “Map 1: Odd/Even Total Kills?” was 50% in the October 4 snapshot. That price belongs to this exact question; it should not be transferred to a different line, period or match-winner proposition. [1]
For this Map 1 kill-parity proposition, a remade game replaces the abandoned version for settlement. Combining both versions would produce the wrong count even if the arithmetic itself were correct. [1]
A FEW GOOD QUESTIONS
What else should you know?
Does 50% mean this old match is still about to happen?
No. It is an observed contract quote; the original fixture date has passed. [1]
Do team kills count in this market?
No. Friendly-fire kills and self-inflicted deaths are excluded by the contract. [1]
What if the map was remade?
Only the remade version supplies the settlement count. [1]
CHECK THE EVIDENCE
Sources & further reading
- Polymarket: Counter-Strike: LPH Gaming vs UNiTY esports (BO3) - United21 Group B ↗polymarket.com
- Valve: Counter-Strike 2 official game description ↗store.steampowered.com
- Exact Polymarket contract: Odd/Even Total Kills ↗polymarket.com
Published . AI-assisted, source-linked analysis. We distinguish evidence from interpretation; this article does not establish a trading edge. How we work →



