
Evgeny Shishkov - Andrey Borisov: betting on this bare-knuckle bout
Evgeny Shishkov - Andrey Borisov is a bare-knuckle boxing bout between Evgeny Shishkov and Andrey Borisov, set for 12.12.2026 16:00. The page opens with the two names on either side of the date, the start time above them and the card's name underneath.
Two markets, one winner
The Evgeny Shishkov - Andrey Borisov page gives two ways of naming the winner:
1X2, where W1 backs Evgeny Shishkov, W2 backs Andrey Borisov and X is the draw;
Team Wins, cut down to W1 and W2, with no draw option.
A draw is the only result that pulls these markets apart. In 1X2 it makes X the winner and both W1 and W2 losers. For a two-way market of the "Win (2way)" type, section 10.8 has W1 and W2 settled at odds of 1 after a draw, so each side gets its stake back; the rules do not name Team Wins as such. On any other result, W1 pays in both blocks when Evgeny Shishkov wins, and W2 does the same for Andrey Borisov.
From the page to the bet slip


A price tapped on the page drops into the bet slip, whose icon stays at the bottom of the screen, and the stake is typed there in Algerian dinars before you confirm. Two positions taken from the same meeting will not sit together in an accumulator; the coupon flags them as incompatible and offers to run them as separate tickets instead.
The rest of the night's bouts are gathered on Top Dog FC, and every card in the discipline sits in the bare-knuckle boxing section. A 1xBet account in dinars lets you back Evgeny Shishkov or Andrey Borisov.
Popular events and sports news
Evgeny Shishkov - Andrey Borisov: draws and stoppages
When does X win on Evgeny Shishkov - Andrey Borisov?
When the judges find, at the end of the last round, that both boxers have scored the same (section 10.8, point 8).
Evgeny Shishkov - Andrey Borisov is ruled a no contest. What happens to bets?
They are void, as with any bout halted before a winner is known. A bet whose outcome was already decided at the moment of the stoppage is settled on the declared result instead (section 10.8, point 2).