Ilves Tampere vs. UMF Stjarnan

Platform comparison

Market context

Ilves Tampere are hosting UMF Stjarnan in the UEFA Europa Conference League second qualifying round, with the market’s 100% YES pricing implying the match is already being treated as a completed or effectively certain outcome rather than a live football balance-of-play call. For a power user running this programmatically, that usually means the key task is not price discovery but state verification: checking whether the event feed has been settled, whether the fixture time has elapsed, and whether the platform is still carrying stale probability data from the scheduled kick-off at 16:00 UTC.[6][11]

Comparable Europe qualification ties show why traders should read this kind of market through context as much as through a single headline price. Ilves and Stjarnan met in the first leg on 23 July, which finished 1-0 to Stjarnan according to live score providers, while pre-match stats sites showed a relatively even pairing with modest scoring rates and market odds that did not suggest a runaway mismatch.[12][3][4] That matters for copy-trading and conditional-order logic because a 100% reading can reflect post-result certainty, delayed updates, or hard caps on pricing rather than a fresh edge, so bots should confirm match status before assuming there is any executable mispricing.[2][6]

The main catalysts are administrative rather than tactical: the official line-up publication, any late injury or travel news, and whether the second-leg result has already been incorporated into the market feed. Sky Sports and Flashscore both list this as the second qualifying-round meeting, with the return fixture in Tampere and the aggregate context implying that settlement should track the final whistle and any extra-time outcome once the event is fully resolved.[1][11] A tooling workflow should therefore poll the fixture state, compare the platform’s yes/no mapping with the live match clock, and lock out new orders once the settlement window is reached or the match enters a confirmed post-result state.[6][11]

Sources: 1 · 2 · 3 · 4 · 5

Methodology

Methodologically we separate two layers: the live probability (Polymarket mid-price) and the platform attributes (fee, KYC, settlement currency, payment rails). That keeps the comparison honest — a single canonical probability across the row, with the venue-by-venue trade-offs spelt out in the columns next to it.

Resolution & payout

At resolution the UMA oracle takes over: a proposer posts the outcome with a bond, any token holder can dispute within two hours. Without dispute the result is accepted and the smart contract distributes USDC instantly.

On Kalshi (CFTC-regulated) resolution runs through their in-house clearing engine in USD. Betfair Exchange settles after match end in the account's local currency. Manifold pays no cash — only its in-platform "mana" currency.

FAQ

How does resolution work?

Through the UMA Optimistic Oracle on Polygon: a proposer submits the outcome, a two-hour challenge window opens, and USDC payouts settle automatically once the result is final.

What's the difference between YES and NO shares?

A YES share pays $1.00 if the event happens, $0 otherwise. A NO share pays $1.00 if the event doesn't happen. The market price between 0¢ and 100¢ is the implied probability.

What does Polymarket cost to trade?

Polymarket itself charges 0% — the only cost is the Polygon network fee, typically under $0.01 per transaction. Off-chain venues like Kalshi or Betfair charge 2-7% commission.

Do I need to KYC for this market?

On Polymarket directly, no — it's wallet-based. Intermediary brokers like Kalshi Fees trigger KYC only above $1,500 of lifetime trading volume; under that you trade pseudonymously with a single wallet address.

How reliable are the quoted odds?

The YES/NO percentages are the live mid-prices of the Polymarket order book. On deep markets they move every few seconds; on thinner ones you'll see short plateaus.