The Stake Engine catalogue checked 2026-08-19 does not identify a separate base RTP for System Infiltration by 0DayGames. RTP Ledger therefore leaves the base value unknown and lists the 6 published modes separately.
The catalogue does not identify a separate base return. RTP Ledger leaves the base return unknown. Use the mode table for the published values.
At the two-decimal display precision, 6 modes share the highest displayed RTP of 96.5%: easy, extreme, and hard and 3 more. 6 modes share the lowest displayed RTP of 96.5%: easy, extreme, and hard and 3 more. The difference between the displayed extremes is 0 percentage points.
| Mode | Type | Published RTP | House edge | Reported events |
|---|---|---|---|---|
| easy | Other feature or mode | 96.5% | 3.5% | 135,673 |
| normal | Other feature or mode | 96.5% | 3.5% | 812,183 |
| hard | Other feature or mode | 96.5% | 3.5% | 1,684,539 |
| extreme | Other feature or mode | 96.5% | 3.5% | 547,126 |
| swarm | Other feature or mode | 96.5% | 3.5% | 1,189,046 |
| root access | Other feature or mode | 96.5% | 3.5% | 1,074,163 |
RTP Ledger checked Stake Engine (fair.stake-engine.com) on 2026-08-19. RTP Ledger displays each published mode RTP rounded to two decimal places and calculates house edge as 100 − displayed RTP. “Reported events” preserves the source field name; it is not labelled as observed rounds or unique outcomes. RTP Ledger does not independently recalculate the catalogue RTP from weights and payouts.
The Stake Engine catalogue does not identify a separate base-game RTP for System Infiltration by 0DayGames. RTP Ledger lists each published mode and leaves the base RTP unknown.
At the two-decimal display precision, 6 modes share the highest displayed RTP of 96.5%: easy, extreme, and hard and 3 more. 6 modes share the lowest displayed RTP of 96.5%: easy, extreme, and hard and 3 more.
RTP Ledger uses the mode RTP values and reported event counts in the Stake Engine catalogue snapshot dated 2026-08-19. RTP values are rounded to two decimal places for presentation while the source precision remains in the data record. The source field is named “events”; RTP Ledger does not relabel it as observed rounds or unique outcomes.
Stake Engine published the catalogue used for the game record. Compare the in-game mode with the published mode table before you play. RTP Ledger can earn a commission if you open Stake through the link. The commission does not change the RTP figures, the publication decision, or the order of records.
Review casino, payment, and withdrawal information for Stake →
5saveUse this if signup asks for a code.
0DayGames has fewer than five catalogue records, so RTP Ledger keeps its studio profile inside the complete games list instead of a separate page.
Version 14, first recorded by RTP Ledger on 2026-08-19. No version change has been recorded since tracking began.