
Lowest temperature in Miami on October 31?
PM $1.9K
1
11
Lowest temperature in Miami on October 31?

PM $1.9K
1
11
Current odds
Snapshot from
As of Oct 30, 2026, 9:00 PM UTC, the highest-priced outcome on Polymarket is 76-77°F at 44%.
Polymarket
- 76-77°F44%
- 78-79°F41.5%
- 74-75°F14%
- 82-83°F3.9%
- 72-73°F2.4%
Yes prices. They are not order quotes; check each platform's rules, fees and live prices before trading.
AI Analysis
Trader mode: Market mechanics, assumptions and risks
PM $1.9K
Reported volume · provider units
11
Saved contracts
0
Same-question pairs
Source snapshot: Oct 30, 2026, 9:00 PM UTC
About This Event
This market will resolve to the temperature range that contains the lowest temperature reported at Miami Intl Airport (KMIA) on 31 Oct '26. The qualifying value is the lowest temperature reported in the hourly temperature remark of any routine (METAR) observation for Miami Intl Airport (KMIA) on that date, in tenths of a degree Celsius as reported. A report whose line begins with SPECI is a special observation and does not count. Every other report is routine, including one issued off the nominal hour and one that carries no METAR or SPECI label. For How to Read the METAR Report, see: https://polymarket-upload.s3.us-east-2.amazonaws.com/market_products/Weather/How+to+Read+the+METAR+Report.pdf The hourly temperature remark is the group beginning with the letter T followed by exactly eight digits. After the T, one digit for sign (0 positive, 1 negative) and three for tenths of a degree Celsius give the temperature; the following four are the dew point and are not used. T01390133 is 13.9°C; T10171022 is −1.7°C. If a routine observation does not carry the hourly temperature remark, the temperature group in the body of that observation governs for that observation, in whole degrees Celsius as reported. It appears as temperature and dew point separated by a slash, with M marking a negative value: 18/12 is 18°C; M11/M17 is −11°C. An observation that reports no temperature in either place is disregarded. Each market in this event states its range in whole degrees Fahrenheit. The qualifying value is converted using °F = °C × 9/5 + 32 and rounded to the nearest whole degree, with a value ending in exactly half rounded up to the next higher whole degree, and that whole Fahrenheit value determines which range contains it. For example, 18.3°C is 64.94°F and counts as 65°F; 17.8°C is 64.04°F and counts as 64°F; 19°C is 66.2°F and counts as 66°F; −22.5°C is exactly −8.5°F and counts as −8°F. An observation counts if its time stamp, converted to the station's local time (including any daylight-saving shift in effect), falls on the observation date. This market will resolve at the issuance of the first METAR observation for the station on the day following the observation date or by 11:59 PM ET on the day following the observation date, whichever comes first. Resolution is determined from the observations the resolution source shows for the observation date. In the event that the Aviation Weather Center has published no routine observation reporting a temperature for the observation date by 11:59 PM ET on the day following the observation date, the Weather Underground Daily Observations table will be used as the resolution source. In the event that neither source has published data sufficient to determine a temperature for the observation date by 11:59 PM ET on the day following the observation date, this market will resolve to the lowest bracket. The report the resolution source shows for a given observation time is the one that counts, whether or not it is marked as a correction (COR). Changes to observations 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. Where the first routine observation for the following date is published before that deadline, resolution is determined from a read taken after it. Where it is not, resolution is determined from a read taken at that deadline. In the case that the Resolution Source publishes data, sufficient to settle a Market, that is clearly erroneous and the result of technical or operational error, or of unauthorized interference with the Resolution Source or its data, the Market may remain open for a period of up to seven (7) calendar days (ET) from the time of the original release, in anticipation of a correction by the Resolution Source. If the Resolution Source publishes a corrected value within that period, that value will be eligible for resolution. If no corrected value is published within that period, Polymarket will issue a Clarification to determine whether the originally published value may be eligible for resolution, or whether other action is required to preserve the orderly functioning of the Market. The resolution source for this market will be the routine observations for Miami Intl Airport (KMIA) published here: https://aviationweather.gov/api/data/metar?ids=KMIA&format=raw&date=2026-11-01T07:00:00Z&hours=30
Snapshot observed 2026-10-30T21:00:05.889Z. This analysis describes that snapshot and is not a live news update.
What the contract measures
This event asks for the lowest temperature reported at Miami Intl Airport (KMIA) on 31 Oct '26. The qualifying value comes from routine METAR observations. Special observations, whose lines begin with SPECI, do not count [1]. Each range is stated in whole degrees Fahrenheit, and the rules convert the Celsius value using °F = °C × 9/5 + 32, rounded to the nearest whole degree [1].
The rules also set the resolution timing. The market resolves at the issuance of the first METAR for the station on the following day or by 11:59 PM ET on the following day, whichever comes first. If neither the Aviation Weather Center nor the Weather Underground Daily Observations table has published sufficient data by that deadline, the market resolves to the lowest bracket [1]. The provider lists an end time of 2026-10-31T12:00:00.000Z [1]. That field does not replace the resolution wording, so readers should check the rules text for timing.
Reading the snapshot
The provider observed these prices at 2026-10-30T21:00:05.889Z, and the data was retrieved at 2026-10-31T01:02:32.377Z. These are historical snapshot values, not current quotes. The event includes 11 markets, all of which are shown in the sample, with no partial sampling reported [1].
The highest Yes prices in the sample are for the 76-77°F range at 0.44, the 78-79°F range at 0.415, and the 74-75°F range at 0.14. Lower Yes prices appear for the remaining brackets, including 0.039 for 82-83°F and 0.0055 for 84-85°F. These are quoted snapshot prices, not executable quotes or verified probabilities.
The Yes prices across the 11 ranges add up to about 1.107. The contracts are separate markets, so this total does not establish an arbitrage opportunity. Volume and trader counts are not included in the supplied data, so they cannot be used to judge liquidity or participation.
What remains uncertain
The supplied evidence does not explain why prices took these values. It also does not show any news, weather forecasts, or observed temperatures for October 31. The rules allow corrections and a holding period for clearly erroneous data, so the final result depends on the published observations, not on the snapshot prices [1].
References
- Polymarket: Lowest temperature in Miami on October 31?. Provider data observed 2026-10-30T21:00:05.889Z.
AI-generated analysis based on market data. Not financial advice.
Saved Oct 31, 2026 UTCOverview
This contract asks which temperature range will contain the lowest temperature reported at Miami International Airport (KMIA) on October 31, 2026. The rules state that it resolves to the range containing the lowest qualifying value reported at that station on the date [1]. Each range in the event is stated in whole degrees Fahrenheit, so the contract is about a specific official observation rather than a general description of Miami's weather [1]. The qualifying values come from routine METAR observations. Reports beginning with SPECI are special observations and do not count, while other reports do, including those issued off the nominal hour [1]. Where a routine observation includes an hourly temperature remark, that value is used, expressed in tenths of a degree Celsius. If that remark is absent, the temperature group in the body of the routine report governs, in whole degrees Celsius [1]. The rules then convert the Celsius value to Fahrenheit using the standard formula and round to the nearest whole degree, with values ending in exactly half rounded up. The resulting whole Fahrenheit value determines which range applies [1]. Timing and fallback rules matter as much as the readings themselves. An observation counts if its timestamp, converted to local time with any daylight-saving shift, falls on October 31 [1]. The market resolves when the first METAR for the following day is issued or by 11:59 PM ET on November 1, whichever comes first [1]. If the Aviation Weather Center has published no routine temperature observation for the date by that deadline, the Weather Underground Daily Observations table is used. If neither source has enough data by the deadline, the market resolves to the lowest bracket [1]. The report shown for a given observation time counts even if it is marked as a correction, and changes are considered only until the first datapoint for the following date is published [1]. If a source publishes clearly erroneous data caused by technical or operational error, the market may stay open for up to seven calendar days to await a correction, after which the platform may issue a clarification [1]. For background, the Wikipedia article on the climate of Miami describes a tropical monsoon climate with hot, humid summers, short warm winters, and a drier winter season, shaped by sea-level elevation, a coastal location, and proximity to the Gulf Stream [2]. This general description does not indicate what any single morning's low will be, and it does not bear on how this contract resolves.
Why It Matters
The contract measures a single station's recorded low for one calendar day, read from specific aviation weather reports. Because it depends on KMIA rather than on Miami as a whole, the result is tied to one observation source and to the rules for choosing among reports [1]. The rules show why small details matter: special observations are excluded, a correction shown by the resolution source counts, and a Celsius reading is converted and rounded to a whole Fahrenheit degree before a range is chosen [1]. For a reader, the practical question is which report and which conversion the rules assign, not the general climate of the area [1][2].
Snapshot context
The latest published provider snapshot for this topic was observed on 2026-10-30 at 21:00 UTC. It contains listings from Polymarket. Market descriptions and listed closing times define the contracts; they do not establish that the real-world outcome has occurred. This article does not include a separately verified news update. [1]
Frequently Asked Questions
Which station's data does this contract use?
The resolution source is the routine observations for Miami International Airport, identified as KMIA [1].
Do special weather observations count toward the lowest temperature?
No. The rules say that a report whose line begins with SPECI is a special observation and does not count. Other reports are treated as routine, including those issued off the nominal hour [1].
How is a Celsius reading turned into a Fahrenheit range?
The qualifying Celsius value is converted using the standard formula and rounded to the nearest whole degree Fahrenheit, with values ending in exactly half rounded up. The rules give examples, such as 18.3 degrees Celsius counting as 65 degrees Fahrenheit [1].
What happens if the main source does not publish a usable temperature?
The Weather Underground Daily Observations table is used if the Aviation Weather Center has published no routine observation reporting a temperature for the date by the deadline. If neither source has enough data by the deadline, the market resolves to the lowest bracket [1].
Does a corrected observation count?
The report the resolution source shows for a given observation time counts whether or not it is marked as a correction. Changes are considered only until the first datapoint for the following date has been published [1].
Does the listed end time equal the resolution time?
No. The saved listing shows an end time of 12:00 UTC on October 31, 2026, but the rules describe resolution at the first METAR for the following day or by 11:59 PM ET on that day, whichever comes first [1].
Can climate background information determine the outcome?
No. The climate article describes Miami's general climate and coastal setting [2], but the contract is settled only by the qualifying station readings and rules described in the market rules [1].
AI-written background. References identify the evidence used; Wikipedia links under Learn More are additional reading. Prices and provider rules are dated snapshots. This is not financial advice.
Related prediction markets
Prices are catalog snapshots and may have changed. Check each market's rules and observation time.

Lowest temperature in Karachi on October 31?
PM $310.96
Lowest temperature in Jeddah on October 31?
PM $87.23
Highest temperature in Miami on October 31?
PM $15.9K
Lowest temperature in Hong Kong on October 31?
PM $11.5K
Lowest temperature in Tokyo on October 31?
PM $5.8K
Lowest temperature in Shanghai on October 31?
PM $5.0KMarket Insights
Price gaps of 2 pp+
0
Same-question pairs
0
No outcomes on this page have been reviewed as the same question on both platforms yet.
Price differences do not establish arbitrage. Check each pair's review, current order prices, fees and settlement rules.