Price history
Select outcomes to plot.
Description
Singapore’s June 26 temperature peak is tracked at Changi Airport Station, with the highest reading on 26 Jun ’26 determining the winning range. The market resolves to the temperature interval that contains that day’s maximum Celsius reading, based on Wunderground data, published after the first datapoint of 26 Jun. Temperature values are rounded to whole degrees Celsius and may be revised until the next day’s first datapoint is published.
Event stats
24h volume
Total volume
Liquidity
Markets
11
Market highlights
Top market
24h gainer
24h loser
Highest volume
Top market
24h gainer
24h loser
Highest volume
Related events
Highest temperature in Seoul on June 24?Highest temperature in Wellington on June 24?Highest temperature in London on June 24?Highest temperature in NYC on June 23?Highest temperature in Sao Paulo on June 24?Highest temperature in Hong Kong on June 24?Highest temperature in Taipei on June 24?Highest temperature in Singapore on June 24?Highest temperature in Tokyo on June 24?Highest temperature in Seattle on June 23?
Markets
Rules
This market will resolve to the temperature range that contains the highest temperature recorded at the Singapore Changi Airport Station in degrees Celsius on 26 Jun '26. The resolution source for this market will be information from Wunderground, specifically the highest temperature recorded for all times on this day for the Singapore Changi Airport Station, available here: https://www.wunderground.com/history/daily/sg/singapore/WSSS. To toggle between Fahrenheit and Celsius, click the gear icon next to the search bar and switch the Temperature setting between °F and °C. This market can not resolve until the first data point for the following date has been published on the resolution source. The resolution source for this market measures temperatures to whole degrees Celsius (eg, 9°C). Thus, this is the level of precision that will be used when resolving the market. Revisions to temperatures recorded within this market's timeframe will be considered until the first datapoint for the following date has been published, after which any alterations will not be considered.