JUPITER PREDICTIONSSEASON 1
VERIFIED CALL
Counter-Strike: FURIA v Legacy (BO3) - Esports World Cup Playoffs
Under 2.5 games
ENTRY
58¢
SOLD AT
13¢
CALLER
@_varsha7
PLACED
2026-08-23 · 08:19 UTC
Nº 0001661R
LOSS
-78%
833637564427
JUPCALLERS.FUN
VerifiedlossCounter-Strike: FURIA v Legacy (BO3) - Esports World Cup Playoffs: Under 2.5 games, -78%Market ↗

Verified: message id, word-for-word text, market link and entry price all captured when the call was posted.

Original Discord message, word for word

Counter-Strike: FURIA vs Legacy (BO3) - Esports World Cup Playoffs Map 1 Although chosen by legacy but furia too has good hold over the map , gonna take furia , leading rn Map2 furia has a dominance So Under 2.5 @55c #nfa https://jup.ag/prediction/POLY-891755

Record

Posted
Sun, 23 Aug 2026 08:19:12 UTC
Event start
Sun, 23 Aug 2026 08:00:00 UTC
Entry
58¢ → sold 13¢ (closed early; scored on the sale price)Entry 58¢: the price the Buy button actually charged the moment the call was posted. The caller wrote 55¢, but that price was not there to buy.

Outcome

Closed early by the caller at 13¢, -45¢ on the 58¢ entry.

closed early via #close (msg 1541021804099805245, posted 2026-08-23T09:50:28.898Z): entry 58c -> exit 14c (-44.0c realized); CLOB history 0.14 at 2026-08-23T09:50:09.000Z (19s from post); "#close under 2.5 Counter-Strike: FURIA vs Legacy (BO3) - Esports World Cup Playoffs" | RE-PRICED from the trade tape once it indexed: exit 14c -> 13c (taker bought the other outcome at 87c, which is this one sold at 13c, 26s from the post)

graded Sun, 23 Aug 2026 09:50:36 UTC
Verification details
Message id
1540998833637564427 open in Discord ↗ (requires server membership)
Market
POLY-891755 jup.ag ↗
Capture
auto-captured: #nfa + jup.ag link + parsed side; event "Counter-Strike: FURIA vs Legacy (BO3) - Esports World Cup Playoffs"; entry 58¢ from the order-book ask at post time (caller stated 55¢)
Think this is wrong (misattributed, wrong entry, wrong grade, duplicate, not a call)? Say so in #prediction-alpha-nfa and tag AG with this call id (#1661). Corrections are published, never silent: see methodology.