This market will resolve to the temperature range that contains the highest temperature reported at Munich Airport (EDDM) on 29 Oct '26.
Leading outcome
99.3%
99%
2 outcomes
Yes
No
Now Gained in 24h Lost in 24hChanges are in percentage points (pp).
Latest update
The timeline is waiting for a meaningful movement. We won’t invent a story to fill the space.
Story so far
MonitoringPolySays is monitoring this market.
No evidence-qualified explanation has been published yet.
No evidence logged yet. No catalyst, open question, or public source is attached to this story, and we won’t guess.
Odds chart
Living timeline
Market rules, made readable
Official descriptionRead the rules before reading the headline. Resolution wording decides the outcome, not the news.
This market will resolve to the temperature range that contains the highest temperature reported at Munich Airport (EDDM) on 29 Oct '26. The qualifying value is the highest temperature reported in the hourly temperature remark of any routine (METAR) observation for Munich Airport (EDDM) 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: The hourly temperature remark is the group beginning with the letter T followed by exactly eight digits.
PolySays is independent and is not affiliated with, endorsed by, sponsored by, or operated by Polymarket. PolySays provides informational and educational content only and does not provide financial, betting, investment, tax, or legal advice. Prediction markets involve risk, and regulatory status varies by jurisdiction.
Source market
Figures refresh periodically, not tick by tick. PolySays explains markets; it doesn’t run one or give trading advice.
View on PolymarketPolySays may earn referral rewards from Polymarket links at no added cost to you. Full disclosure.
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 Celsius.
The qualifying value is rounded to the nearest whole degree, with a value ending in exactly half rounded up to the next higher whole degree, and that whole Celsius value determines which range contains it. For example, 13.9°C counts as 14°C; 17.4°C counts as 17°C; 16.5°C counts as 17°C; −1.7°C counts as −2°C; −8.5°C counts as −8°C.
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 Munich Airport (EDDM) published here: