Infinity Nikki codes: a dated list, and why redemption fails
By DayOneFix Editorial · August 14, 2026
Most codes pages hand you a wall of strings with no dates and no sources, so you paste twenty of them and have no idea which failed because it expired and which failed because of your account. This page gives every code the date it first appeared publicly and where it came from, then explains the six official rules that decide whether redemption works at all.
We have not redeemed these ourselves. Treat the date as the confidence signal — the older a code is, the more likely it has quietly expired without anyone updating a list.
Re-checked 23 August 2026. We could not reach the r/InfinityNikki megathread today: reddit.com refuses our fetcher outright, and old.reddit.com bounces to a login wall. So the “first seen” dates below stand unchanged and unre-confirmed. What we could reach were the guides sites, and the status column records what they actually said today.
The codes, by date first seen
Dates below are when each code first appeared in the r/InfinityNikki megathread, which in our checking runs ahead of the big guides sites — the 8 August batch was in the thread days before it showed up elsewhere. The status column is a listing check made on 23 August 2026. It is not a redemption test.
| First seen | Codes | Status on 23 Aug 2026 |
|---|---|---|
| 10 Aug 2026 | EYESONTHEGOLDENFEAST | Still on PCGamesN’s active list |
| 8 Aug 2026 | AAxtye9AVTq · AAxM6fYVAY5 · AAuFNDw2bs6 · AAu2FAUSPUa · AAuJTUa7U9D | Not on any tracker we reached |
| 4 Aug 2026 | AAuEDFnQFpu · AAuMuv96x7r | Not on any tracker we reached |
| 2 Aug 2026 | AAuMe6F9MPU | Not on any tracker we reached |
| 28 Jul 2026 | AAu6hcK7cBp · AAuPeEK4vvp | Not on any tracker we reached |
| 27 Jul 2026 | AAukBUSQ46N · AAuQ8sMjHEC · AAuw8HYBSAx · AAuYEKevUdN · AAuu6Kdqpah · AAuxHNv8eFA | Not on any tracker we reached |
“Not listed” is not the same as “expired”, and we are not going to blur them. PCGamesN publishes an expired list, and none of those sixteen strings are on it — they were dropped off the page rather than retired into it. GamesRadar, which does mark dead codes individually, files whole batches of this shape under “code usage limit reached” rather than “expired”, which matches the redemption page’s own error vocabulary further down this page. Our reading is that the batch strings burn through a shared redemption cap and stop working for everyone. We have not redeemed them, so we are not stating that as fact.
Word codes still listed by at least one major guides site, undated at source: MOMOWISHESNIKKILISTENS, JOINNIKKIATTHEGOLDENFEAST, GoldenFeastDC, SongofGoldReddit, MachineControlFB. All five were still on PCGamesN’s active list today; PocketGamer, whose page was last updated 2 August, still carried two of them.
Codes are case sensitive. The mixed-case ones above are exactly as published — SongofGoldReddit will not work as SONGOFGOLDREDDIT.
Seen today, but undated
PCGamesN’s page (marked updated 22 August 2026) carries codes our dated table does not. They go in a separate block because we have no megathread date for them and will not invent one:
- Flagged “new” there:
AAujNje6sk2·AAuTVhQjaqX·AAxmBaFCVrJ·AAxnJxPbvUj·AAuR3UpfvMS·HEAVENSREACHSEA - Listed active there without a date:
SEEYOUINHEAVENSREACH·DANCEINTHEMIRROR·FINALCHAPTEROFITZALAND·DazzlingSpotlightDC
One source, no date, not redeemed by us — weigh them accordingly. The one thing that argues for them: HEAVENSREACHSEA and SEEYOUINHEAVENSREACH are named after the Heaven’s Reach Relic Hunt, a 2.8 event that appears by name in Infold’s own 6 August patch notes.
Two patterns worth knowing
The AAu / AAx strings are a different species from the word codes. They arrive in batches of five or six on a single day, and the word codes arrive one at a time around events. Nobody publishes an official explanation of what generates them, so we are not going to invent one — but the batch rhythm is real and visible in the table above.
Word codes are named after the channel that published them. GoldenFeastDC came from Discord, SongofGoldReddit from Reddit, MachineControlFB from Facebook. That suffix is the most useful thing on this page if you want to catch codes early: it tells you Infold distributes different codes to different social channels, so following only one account means missing the others.
⚠️ The guides sites disagree about what these give you
This is worth stating plainly because it affects whether you bother:
- Eurogamer lists the
AAuseries as 30 Shiny Bubbles + 20,000 Bling each. - PCGamesN lists several of the same strings as “Diamonds and Bling”.
- The Reddit megathread lists them with no reward description at all.
Three sources, three answers, same codes. We could not confirm which is right, so we are not picking one. The official 2.9 notice published today details event rewards, not code rewards, so it does not settle this either. If a page tells you confidently that these grant Diamonds, ask where that came from.
How to redeem
Two routes. On iPhone and iPad the website is the practical route, which is the single most common source of “I can’t find where to enter this”.
Website (works everywhere): open Infold’s official redemption page, sign in, then select your Server and Character before pasting the code. Both dropdowns are mandatory — this is where most web redemptions fail.
In game: the redemption entry inside the game client, on platforms where it is present.
Why redemption fails — straight from the official rules
Infold publishes six rules on the redemption page. Five of them are failure modes:
| Rule | What it means when it bites you |
|---|---|
| Account binding | You must be logged into an Infold account and have a character bound to it. A fresh Infold account with no bound character cannot redeem anything, regardless of the code. |
| Rewards go to in-game mail | Nothing appears in your inventory. It lands in mail, and mail expires — a “successful” redemption you never opened is a lost reward. |
| Conditions and expiry | Codes carry both an expiry date and eligibility conditions. A code can be live and still refuse you. |
| One use per character | Not per account — per character. Retrying a code you already used reads as a failure. |
| Irreversible | Redemption cannot be undone, so confirm which account you are signed into first. Redeeming onto the wrong account is unrecoverable. |
Two mechanical traps the rules do not cover: O versus 0 and l versus 1 in the AAu strings, and a trailing space picked up when copying out of a chat app.
What the page actually tells you when it refuses
The redemption page ships its own error messages, which we read out of its script bundle on 23 August 2026. The exact wording tells you which rule you hit:
| Message | What actually happened |
|---|---|
| Invalid code | The code does not exist — a typo, or a string that was never real |
| Not available yet | Real code, but its window has not opened |
| Code expired | Past its validity window |
| Redemption limit reached | The code’s total redemption cap is used up |
| Already redeemed | This character has already used this code |
| Reward claimed already | The account already holds the reward behind this code |
| Requirements not met | Live code, but you do not qualify for it |
| Character does not exist / No available characters for this account | The account-binding rule above |
“Redemption limit reached” is the one people misread as their own fault. It is not, and retrying will not help — that code is finished for everybody. It is also the message we would expect the older AAu batches to return.
Version 2.9 is official: 28 August
Infold published its first official 2.9 notice on 23 August 2026, on the Traditional Chinese official site. It is titled 2.9版本「向晴空綻放」活動說明, timestamped 23 August 2026 at 04:10 UTC, and it prints the event window three separate times as 2026年8月28日2.9版本更新後 — 2026年9月24日03:49（UTC+8）: from the 2.9 update on 28 August 2026 until 24 September 2026, 03:49 UTC+8. The key art carries the English line “Bloom Beneath Bright Skies”.
That date matches what the English patch notes already implied. Infold’s 6 August update notice sets nearly every 2.8 limited-time event to end 27 August 2026 at 12:49 (UTC-7) — the same instant as 28 August 03:49 UTC+8. Two official sources, one changeover moment.
The 23 August 2026 check found no 2.9 announcement in the English news feeds checked. The official Steam news feed’s newest post was “Behind the Seams | The Inspiration Behind [Golden Dust]” from 13 August; the official site’s English news list stopped at 5 August; the Japanese list stopped at 13 August. Among those news channels, only the Traditional Chinese channel had published a 2.9 announcement.
How our projection did
This page previously carried a community projection instead of official dates. It stays here, scored, rather than being quietly deleted:
| What the community trackers projected | What happened |
|---|---|
| Preheat starts around 21–22 August | Missed. Nothing official appeared on 21 or 22 August. The first official 2.9 publication landed on 23 August. |
| Version goes live around 28 August | Correct. Officially 28 August 2026 (UTC+8). |
So the cadence-readers called the update date correctly, days before Infold confirmed it, and were one to two days early on the run-up. That is roughly how much weight to give them next version.
Codes cluster around version previews, so the 2.9 run-up is where the next batch should show up. Watch the channel-suffixed word codes especially — Discord, Reddit and Facebook each get their own.
How this page is maintained
Codes go up here with a date and a source, never scraped into an undated pile. When one is confirmed dead it stays listed and gets marked expired rather than vanishing — “was this code ever real?” is half of why people search. Where sources conflict, we show the conflict instead of picking the convenient answer. And when a projection we published turns out wrong, it stays up and gets scored, as the 2.9 one is above.
Related
- Genshin Impact 7.0 countdown in your timezone
- HSR codes: how to redeem and why yours failed
- Endfield codes and how to redeem
Sources
Everything below was checked on 23 August 2026.
Official. The 2.9 dates come from Infold’s Traditional Chinese notice 2.9版本「向晴空綻放」活動說明, published 23 August 2026 at 04:10 UTC; the body of that post is three images, and the event window is printed inside them. The corroborating 2.8 end time — 27 August 2026, 12:49 (UTC-7) — is in the “August 6: Version 2.8 Update Notice” post on the official Steam news feed, which we also used to establish that no English-language 2.9 announcement exists yet: its newest item is dated 13 August 2026. The redemption rules, and the error messages quoted above, come from Infold’s official redemption page.
The codes. The dated table comes from the r/InfinityNikki code megathread, and those dates record when each string first appeared in that thread, not when Infold issued it. We could not re-reach that thread today — reddit.com refuses our fetcher and old.reddit.com redirects to a login wall — so no date in that column has been re-confirmed, and we have left the column exactly as it was rather than restating it as current. The status column and the undated block were read today from PCGamesN, whose page says updated 22 August 2026; PocketGamer, last updated 2 August 2026; and GamesRadar, last updated 5 May 2026 and therefore too stale for its silence about a code to mean anything — we used it only for its status vocabulary. We have not redeemed any of these codes. A listing check is not a redemption test.
Still unresolved. The reward disagreement stands three ways: Eurogamer lists 30 Shiny Bubbles and 20,000 Bling per code, PCGamesN labels several of the same strings “Diamonds and Bling”, and the Reddit megathread gives no reward description at all. We could not reach a Eurogamer codes page today — the URL patterns we tried returned 404 and their on-site search is client-rendered — so Eurogamer stays described without a link, as it was before. Case sensitivity, the O-versus-zero confusion and trailing whitespace on paste remain our own handling notes, drawn from the shape of the codes.