Event

Gençlerbirliği SK vs. Alanyaspor - More Markets

3 signals across 2 markets · $4,505 tracked · resolves Nov 2, 2026

This Polymarket event covers whether both Gençlerbirliği SK and Alanyaspor will score in their Süper Lig match. A profitable serial bettor recently added to the No outcome; check the market for current odds and activity.

Markets (2)

  1. Gençlerbirliği SK vs. Alanyaspor: Both Teams to Score2 signals · $3,318 tracked
  2. Gençlerbirliği SK vs. Alanyaspor: O/U 5.51 signal · $1,187 tracked

Top trades across all markets

  1. 97% winner with $1.8M profit

    A highly profitable bettor with 4,307 resolved trades and a 97% win rate placed a sizable Under bet in a low-volume market.

    $1,187Wallet win rate: 97%Score: 4.9
  2. Profitable serial bettor adds to No

    A highly active, profitable bettor is adding to an existing No position, though their win rate is only modestly above their average winning price.

    $1,098Wallet win rate: 75%Score: 4.3
  3. Profitable serial cross-market bettor

    A profitable serial cross-market bettor added about $2,220 to an existing No position in a thin market, though their historical win rate is only modestly above their average winning price.

    $2,220Wallet win rate: 75%Score: 4.3

Top wallets in this event

  1. 0x051ade…1db9$3,318 · 1 market · 2 alerts · 75% wins
  2. 0x8191c7…da72$1,187 · 1 market · 1 alert · 97% wins

More on this event

FAQs

What outcome is traded in the Gençlerbirliği vs. Alanyaspor event?

The listed child market asks whether both teams will score in the Süper Lig match, with Yes and No outcomes.

What are the Polymarket odds for both teams to score?

Odds can change as traders buy and sell shares. Check the live market on this page for the latest prices.

What is smart money doing in this event?

PolySpotter tracked one smart money signal, with a profitable serial bettor adding to the No outcome.

When does the Gençlerbirliği vs. Alanyaspor market resolve?

The event is scheduled for November 2, 2026, at 12:00 PM ET and is listed to resolve by 5:00 PM UTC that day.