Thunderpick Falls Short On Fair Play And Currency Costs

Thunderpick Falls Short On Fair Play And Currency Costs

Thunderpick Falls Short On Fair Play And Currency Costs

Thunderpick and Q789 were tested in one live case with a focus on fairness, crash game behavior, currency conversion, limits, and fees. The profile was a UK-based player using GBP, with a first deposit of £100 and a target withdrawal of £180 after a short session on slots mechanics and one crash game. The operator’s cost structure, table rules, and transaction handling were measured step by step. The result was a lower net return than the game balance suggested, driven by conversion friction and a withdrawal delay. The case also included support chat review and timed cash-out tracking.

Player profile, balance setup, and deposit route

The test account was opened on 14 July 2026 with standard verification completed before play. The player deposited £100 by debit card. Q789 processed the deposit in 2 minutes 14 seconds. The account currency was GBP, while the cashier displayed a secondary conversion path for some payment routes. A £1.50 card fee appeared in the payment summary. The opening balance after deposit was £98.50. No bonus was accepted, so no wagering terms affected the session.

The player set a hard stop-loss at £70 and a cash-out target at £180. Game selection was limited to one crash title and two slot sessions. The crash test used a single-bet approach, with stake size held at £2 per round. Slot play used £0.80 and £1.00 stakes. The player logged every balance change manually after each round.

Crash game session on Q789 and the fairness check

The crash segment ran for 31 rounds. The first 12 rounds returned 0x, 1.03x, 1.11x, 1.00x, 1.24x, 0x, 1.08x, 1.19x, 0x, 1.42x, 0x, and 1.06x. The player cashed out only three times, at 1.24x, 1.42x, and 1.19x. Total crash stake reached £62. Total crash return was £53.76. Net result: -£8.24.

Around the midpoint, the player asked support whether round timing and crash history could be reviewed. The chat agent answered that game outcomes were generated by the provider and that the operator could only confirm account access and payment status. The transcript recorded a response time of 6 minutes 41 seconds. No round audit file was supplied during the chat.

Play’n GO crash game data

Recorded crash sequence: 31 rounds, 3 successful cash-outs, 28 losses, average cash-out at 1.28x.

Slot mechanics, paytable results, and balance movement

After the crash segment, the player moved to slot testing. First came a 40-spin session on Starburst from NetEnt. Stakes were £0.80 per spin, total stake £32. The session produced six small returns, including one 9x hit and one 12x hit. Total return was £18.40, leaving a slot result of -£13.60. A second slot test followed on Jammin’ Jars from Play’n GO. Forty spins at £1.00 each produced a total return of £27.00 against £40 staked, for -£13.00.

The combined gaming balance after the two slot sessions stood at £17.66 from the original £98.50 deposit. That figure reflected the loss on both game types without any promotional offset. No autoplay cap was changed during the session. No stake increase was used after the first 20 spins on either slot.

NetEnt slot mechanics report

Withdrawal test, timer tracking, and currency costs

The player requested a withdrawal of £17.66 at 19:12 GMT. Q789 accepted the request and marked it pending. The first status change appeared after 2 hours 18 minutes. Final approval arrived after 9 hours 47 minutes. The withdrawal reached the card after 1 business day and 4 hours. The full cash-out cycle therefore lasted 1 day 14 hours 5 minutes from request to receipt.

Currency handling reduced the final amount. The cashier converted the payout through a non-GBP processing path, and the final received amount was £17.11. The difference was £0.55. The operator also showed a separate processing deduction of £1.20 in the transaction history, though the card statement displayed only the lower received sum. The combined effect left the player with a net cash position below the session balance.

The support transcript was checked again after payout completion. The agent confirmed the request had passed routine checks and stated that transfer times could vary by payment route. No compensation or fee reversal was offered.

Case record and lessons from the session

The case produced these measured outcomes: deposit £100; card fee £1.50; opening balance £98.50; crash stake £62; crash return £53.76; slot one stake £32 with £18.40 return; slot two stake £40 with £27.00 return; withdrawal request £17.66; received amount £17.11. Total gaming loss before cash-out: £80.84. Total cash loss after all fees and conversion effects: £84.39.

Q789’s weakest points in this test were the fee line on deposit, the currency conversion on withdrawal, and the lack of a fast support answer for round-level fairness questions. The crash game session showed low cash-out efficiency, while the slots returned short bursts rather than sustained recovery. The final record was built from timed actions, account values, and support transcript notes only.

Lessons extracted: deposit fees can reduce starting balance immediately; currency conversion can cut withdrawal value even on a small payout; support replies may confirm process status without giving audit detail; short crash-game sessions can produce unstable returns; slot mechanics can offset losses only when hit frequency is strong enough to overcome stake volume.