JUPITER PREDICTIONSSEASON 1
VERIFIED CALL
RC Celta de Vigo v CA Osasuna - More Markets
Over 1.5
ENTRY
65¢
RESULT
+54%
CALLER
@focused555
PLACED
2026-08-27 · 18:38 UTC
Nº 0001903R
WIN
+54%
191803904070
JUPCALLERS.FUN
VerifiedwinRC Celta de Vigo v CA Osasuna - More Markets: Over 1.5, +54%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

https://jup.ag/prediction/POLY-789373 i’m picking over goals 1,5 goals at 65c #nfa

Record

Posted
Thu, 27 Aug 2026 18:38:19 UTC
Event start
Thu, 27 Aug 2026 18:30:00 UTC
Entry
65¢ Entry 65¢, the number the caller wrote. The market briefly showed better odds, and a call never pays more than its caller claimed.

Outcome

Won: the market resolved for Over 1.5.

gamma POLY-800170 "O/U 1.5" outcome "Over" price 0.9995 uma=proposed closed=false

graded Thu, 27 Aug 2026 20:42:31 UTC
Verification details
Message id
1542604191803904070 open in Discord ↗ (requires server membership)
Market
POLY-800170 jup.ag ↗
Capture
auto-captured: #nfa + jup.ag link + parsed side; event "RC Celta de Vigo vs. CA Osasuna - More Markets"; side names a prop, resolved on this fixture's companion event "RC Celta de Vigo vs. CA Osasuna - More Markets" (POLY-800170) — the linked event carries only the match markets; entry 88¢ from the order-book ask at post time (caller stated 65¢); CORRECTED 2026-08-27: side was "Over 0.5" @ 88¢, now "Over 1.5", entry is the caller's stated 65¢; the order book at the post moment reads 64¢ (mid at post time (ask unrecoverable this long after the post)), which is not a buyable ask, so the stated figure stands — caller wrote 'over goals 1,5 goals at 65c': the unit word sat between the direction and the line so the line never parsed, and a totals side with no line matched the first O/U market on the event — boarding his 1.5 call on the 0.5 book at 88c (matcher fixed the same day)
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 (#1903). Corrections are published, never silent: see methodology.