TOTAL VOLUME:

$134b

24H VOL:

$87,176,691

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,391,958,194

394,660

Markets across

30,119

events

MATCHED EVENTS:

2,626

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Tour
All
Sports
Le Havre AC vs. Olympique Lyonnais
kalshi
polymarket

Le Havre AC vs. Olympique Lyonnais

Volume:
$707,031

Draw (Le Havre AC vs. Olympique Lyonnais)

 - Polymarket

Draw (Le Havre AC vs. Olympique Lyonnais) - Polymarket

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Mar 15, 2026

Closed: Mar 15, 12:15 PM EST

polymarket

Polymarket

View
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
polymarket

Draw (Le Havre AC vs. Olympique Lyonnais)

View
100%
Yes 100¢No 0¢
—
N/A
$76,493
N/A
N/A
N/A
Settled
Yes
polymarket

Olympique Lyonnais

0%
Yes 0¢No 100¢
—
N/A
$438,156
N/A
N/A
N/A
Settled
No
polymarket

Le Havre AC

0%
Yes 0¢No 100¢
—
N/A
$192,179
N/A
N/A
N/A
Settled
No
kalshi

Both Teams To Score

0%
Yes 0¢No 100¢
—
N/A
$203
N/A
N/A
$165
Settled
No
Total markets: 4

Description

This event group covers a Ligue 1 match between Le Havre AC (home) and Olympique Lyonnais (away) scheduled for March 15, 2026. Markets track three distinct outcomes: both teams scoring, a draw result, Le Havre winning, and Lyon winning, all evaluated within 90 minutes plus stoppage time.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

All platforms apply identical time scope (90 min + stoppage), identical cancellation logic, and identical primary resolution source (Ligue1.com official statistics with credible reporting fallback).Primary resolution logic: Official Ligue1.com statistics; if unavailable within 2 hours post-match, consensus of credible reporting sources.

Core resolution logic:

  • Match result determined only within 90 minutes of regular play plus stoppage time; extra time and penalties excluded
  • Both Teams Scoring (Kalshi): Resolves Yes if both Lyon and Le Havre score at least one goal each within regulation
  • Draw (Polymarket): Resolves Yes if final score is equal; No if either team wins
  • Le Havre Win (Polymarket): Resolves Yes if Le Havre scores more goals than Lyon; No otherwise
  • Lyon Win (Polymarket): Resolves Yes if Lyon scores more goals than Le Havre; No otherwise
  • Postponement: All markets remain open until match is completed
  • Cancellation with no makeup: Draw and win markets resolve No; both teams scoring resolves Yes

Edge cases & clarifications:

  • Match Postponement: If match is postponed, all markets remain open and unresolved until the rescheduled match is completed. Resolution then occurs based on the completed match result.
  • Match Cancellation: If match is canceled entirely with no makeup game scheduled, draw/win markets resolve No, while both teams scoring market resolves Yes (per Kalshi logic treating cancellation as event non-occurrence).
  • Official Stats Delay: If Ligue1.com does not publish final statistics within 2 hours after match conclusion, resolution uses consensus of credible reporting sources (e.g., major sports news outlets, ESPN, official team sources).
  • Stoppage Time Scoring: Goals scored during stoppage time (injury time) count toward all market resolutions; only extra time and penalty shootout goals are excluded.
Timing: Resolution occurs within 2 hours after the match concludes on March 15, 2026, or upon publication of official Ligue1.com statistics, whichever is earlier. If official stats delayed beyond 2 hours, credible reporting consensus triggers resolution.Our PredictionHero Resolution Divergence Alerts (RDA) are there to help users identify potential differences across platforms. They do not replace or supersede the official rules and description of any prediction market. Users are solely responsible for reviewing and understanding the applicable rules and resolution criteria before placing any trade or bet. If you notice a potential inconsistency, discrepancy, or error in an alert, please report it to our team so we can review and improve the accuracy of our data.