Checked October 28, 2026: the 36-code queue combines the October 5 baseline with seventeen strings repeated by opened October 8–26 third-party lists. “Reported current” means source agreement—not an in-game redemption performed by this site.
October 27 Update 1 check
Two current source records repeat UPDATE1, SORRYFORDELAY, THANKSFORWAITING, and SHARDSPEND. GamesRadar+ also reports a reward bundle for each; the code desk labels those bundles as third-party reported, not redeemed or guaranteed by this site.
Role: October 24 current table independently listing SRYFORLATEUPDATE
Boundary: Third-party supply evidence; agreement supports reported status, not an in-game redemption claim.
October 16 Update 0.75 / Halloween check
Two opened current guides repeat HAPPYHALLOWEEN, IAMATOMIC, UPDATE075, and HALLOWEENEVENT. They support reported status only; this site did not redeem the strings or publish reward quantities.
Role: October 16 current list adding the same four Halloween/update strings
Boundary: Third-party report; its reward labels are not treated as independently verified.
October 12 milestone update
Four opened current guides repeat THANKFOR12KCCU and THANKFOR13KCCU. They support reported status only; this site did not redeem either string or publish reward quantities.
Role: October 12 current table repeating both new strings
Boundary: Third-party report; the official API does not announce these strings.
What each status means
Reported current
The exact string appeared in multiple dated current source tables, including the October 5 baseline or the October 8–22 update checks. It was not redeemed by this site.
Unclear
The string was retained by fewer current sources or was affected by a conflict. It stays separate from the reported queue.
Confirmed expired
This requires stronger current evidence than one table omitting the string. No checked string met that threshold in this research packet.
Tried / marked redeemed on this device
These are visitor-owned browser notes. They do not change the editorial label and are not a Roblox receipt.
October 10–11 Update 0.5 check
Two opened current guides repeat UPDATE05, FATESTAYNIGHT, and GILGAMESH. The official exact-game API supplies update context only; this site did not redeem the strings or publish reward quantities.
Role: Current third-party code table used in the common-set comparison
Boundary: Duplicate rows cannot increase source agreement or the unique-code count.
October 7–8 milestone update
These three opened pages repeated THANKSFOR20KMEMBERDISCORD and THANKSFOR3MVISIT. They support reported status only; this site did not redeem either string.
Role: Official creator group and observed owner identity
Boundary: Identity evidence only; it is not a code announcement feed.
Worked conflict
Why THANKSFOR9000CCU is unclear
Several current sources retain THANKSFOR9000CCU, while Game.Guide marks it expired. That direct conflict is enough to preserve the string for rechecking, but not enough to merge it into the reported queue or call it confirmed expired.
How a status can change
A future status change requires a new dated source check, a fresh comparison of the current tables, and preserved conflict notes. One omission, one visitor's local attempt, or a copied string cannot silently promote or expire a code.