JUPITER PREDICTIONSSEASON 1
VERIFIED CALL
LoL: Bilibili Gaming v ThunderTalk Gaming (BO3) - LPL Group Ascend
Bilibili Gaming -1.5 games
ENTRY
67¢
RESULT
-100%
CALLER
@Pampa
PLACED
2026-07-23 · 11:09 UTC
Nº 0000453R
LOSS
-100%
759158284298
JUPCALLERS.FUN
VerifiedlossLoL: Bilibili Gaming v ThunderTalk Gaming (BO3) - LPL Group Ascend: Bilibili Gaming -1.5 games, -100%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

LoL: Bilibili Gaming vs ThunderTalk Gaming (BO3) pick : BLG -1.5 67c Thesis: BLG had a lot of drama lately (Bin not playing ) but i still think they will stomp the other team They have knight and xun and viper which are great players that reached the final of MSI but lost against HLE if you are not confident in the 1.5 you can go with BLG straight win with lower odds as kevin mentioned here #nfa #dyor https://jup.ag/prediction/POLY-707295

Record

Posted
Thu, 23 Jul 2026 11:09:52 UTC
Event start
Thu, 23 Jul 2026 12:25:00 UTC
Entry
67¢

Outcome

Lost: the market resolved against this pick.

gamma POLY-707295 "Game Handicap: BLG (-1.5) vs ThunderTalk Gaming (+1.5)" outcome "Bilibili Gaming" price 0.005 uma=none

graded Thu, 23 Jul 2026 14:16:46 UTC
Verification details
Message id
1529807759158284298 open in Discord ↗ (requires server membership)
Market
POLY-707295 jup.ag ↗
Capture
boarded via manual browser scan; corrected same day: the scan attached the wrong source message (a reply whose quoted text was mis-read as the call). True call: pick BLG -1.5 at a stated 67c, msg 1529807759158284298. The game-handicap market grades this call. Correction logged in the audit trail.; SIDE CANONICALISED 2026-07-31: "BLG -1.5" -> "Bilibili Gaming -1.5" (same bet, proper outcome name); SIDE CANONICALISED 2026-08-01: "Bilibili Gaming -1.5" -> "Bilibili Gaming -1.5 games" (same bet, proper outcome name)
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 (#453). Corrections are published, never silent: see methodology.