
Callum Nulty - Amado Fernando Vargas: betting on this bare-knuckle bout
Callum Nulty - Amado Fernando Vargas is a bare-knuckle boxing bout between Callum Nulty and Amado Fernando Vargas, set for 14.11.2026 18:45. 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 Callum Nulty - Amado Fernando Vargas page gives two ways of naming the winner:
1X2, where W1 backs Callum Nulty, W2 backs Amado Fernando Vargas 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 Callum Nulty wins, and W2 does the same for Amado Fernando Vargas.
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. A dedicated control empties the coupon in one go, sparing you the line-by-line removal when the ticket needs a fresh start.
The rest of the night's bouts are gathered on Bare Knuckle Boxing, and every card in the discipline sits in the bare-knuckle boxing section. A 1xBet account in dinars lets you back Callum Nulty or Amado Fernando Vargas.
Popular events and sports news
Callum Nulty - Amado Fernando Vargas: draws and stoppages
When does X win on Callum Nulty - Amado Fernando Vargas?
When the judges find, at the end of the last round, that both boxers have scored the same (section 10.8, point 8).
Callum Nulty - Amado Fernando Vargas 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).