In brief
RTP Index recorded five RTP changes at STAKE. Of the three largest movements listed here, one published value rose and two fell. Phoenix Star moved from 98.0 to 96.25. Cavemen and Dinosaurs appears once with the same fall and once with a return from 96.25 to 98.0.
The record captures separate lobby observations rather than a fixed setting that applies indefinitely. A changed RTP value becomes a new observation in our database. We retain the earlier observation, so the record can show a game moving back to a figure that appeared before.
What happened
RTP Index first recorded Phoenix Star at 98.0 and later recorded it at 96.25. The published RTP value fell by 1.75 percentage points. We also recorded Cavemen and Dinosaurs moving from 98.0 to 96.25, which was the same decrease.
A separate observation for Cavemen and Dinosaurs showed the reverse movement, from 96.25 to 98.0. This does not erase the earlier lower observation. RTP Index stores each changed value as a separate entry, with the raw response returned by the operator’s lobby.
The available material says that these are three of the largest movements among five changed games. It does not identify the other games in this summary. It also does not provide their earlier or later lobby values.
What this changes for players
The observations show that a game’s displayed RTP can change over time at the same operator. A player checking Phoenix Star at one point could have seen the higher figure, while a later check showed the lower one. Cavemen and Dinosaurs is a clearer example because the recorded value moved in both directions.
The lobby figure is relevant before a session starts, but it does not establish the result of any individual session. RTP Index reads the value from STAKE’s own lobby before play begins, as Brazilian gambling rules require. We save the raw response that supplied the published value.
Players who compare RTP figures should treat a displayed value as time-specific. The practical question is what the lobby showed when they checked it. Our record can confirm that published figure at the time of observation, but it cannot promise that a later check will show the same value.
What is known and what the source does not say
We know that STAKE is a Brazil-licensed casino brand and that RTP Index had recorded these changes by 2026-08-14. We know the before-and-after values for Phoenix Star and for the two listed Cavemen and Dinosaurs observations. We also know that the full set covered five games.
We do not know why STAKE’s published RTP values changed. The evidence does not attribute a change to a game configuration, a lobby update, or any other operational decision. RTP Index therefore makes no claim about the reason behind any movement.
The record does not say that STAKE hid information. It shows values that the operator published in its own lobby at the moments we checked. It also contains no promotional statement from STAKE that requires confirmation or repetition.
What the RTP Index newsroom thinks
The useful finding is the documented change in a published lobby value. It is not a basis for guessing why an operator made a change. The repeated Cavemen and Dinosaurs entry matters because it shows that a recorded movement can reverse rather than continue in one direction.
Our method preserves an auditable trail. Each observation is linked to the raw response from which we read the RTP value, and earlier observations remain available after a new value appears. That approach is more reliable than relying on a remembered lobby display.
The method has a firm limit. RTP Index records what STAKE published at the time of each check, before a session began. It cannot determine the cause of a change, and a published RTP value is not a prediction of what will happen in a particular session.
