Loading shell…
GeopoliticsMulti-outcomeExpires Jun 3, 2026

Will Kim Jin-tae win the 2026 Gangwon Province gubernatorial election?

Probability

10¢

1h

-0.1pp

24h

+1.3pp

24h Vol

$37.84

Liquidity

$24.0K

Probability (last 7 days)

+6.7pp 7d
Apr 18, 2026, 15:00Apr 25, 2026, 11:53
updated 0s ago·src:Polymarket CLOB

Why did it move?

 

Heuristic summary, generated from the public market metrics above: probability movement, volume, liquidity, spread, signals, and resolution status.

Timeline — news, trades, signals, price moves

AllTradesSignalsPrice
  • 0s agoResolve

    Market resolves in 924.1h

    LOW
  • 11:54Signal

    Signal · Resolution risk

    Expires in 924h with open resolution ambiguity.

    LOW
  • 2d agoPrice

    Probability up 3.1pp

    to 9¢

    MEDIUM
  • 2d agoPrice

    Probability up 3.8pp

    to 9¢

    MEDIUM
updated 0s ago·src:Polymarket CLOB·Polymarket Data

Active signals

Recent Trades

No recent trades visible from the Data API for this market.

updated 0s ago·src:Polymarket Data

Market Description

The Gangwon Province gubernatorial election is scheduled to take place in South Korea on June 3, 2026 to elect the next governor of Gangwon Province. This market will resolve according to the candidate that wins this election. If the result of this election isn't known by December 31, 2026, 11:59 PM ET, the market will resolve to "Other". This market will resolve based on the result of the election as indicated by a consensus of credible reporting. If there is ambiguity, this market will resolve based solely on the official results as reported by the South Korean government, specifically the National Election Commission (https://www.nec.go.kr/).

Resolution & Risk

LOW risk
End date
Jun 3, 2026
UMA status
n/a
Resolution source
Not specified in metadata
Market type
Multi-outcome (neg-risk)
  • Part of a multi-outcome event (neg-risk): only one market can resolve YES.
Read full market rules on Polymarket

Alerts

¢
Deliver

In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).