No official complete count or room-by-room list of all Anomaly Detected anomalies is publicly available. The developer does confirm three examples—misplaced objects, flickering lights, and shadows that move on their own—and official badges confirm a separate Journal completion goal for each of five chapters. The useful “all anomalies” answer is therefore a currently documented index plus a reliable way to expand it from the live Journal.
Known family index
Misplaced object
Type: object comparison.
Official signal: named in the Experience description.
Check: position, presence, count, orientation, and silhouette against fixed room edges.
Best page: Anomalias de objetos.
Flickering light
Type: lighting behavior.
Official signal: named in the Experience description.
Check: repeated fixture behavior and the surfaces whose illumination changes.
Best page: Anomalias de luz.
Moving shadow
Type: independent motion.
Official signal: named in the Experience description.
Check: movement relative to a fixed doorway, wall, floor line, or light source.
Best page: Anomalias de sombra.
The developer’s wording uses examples, not an exhaustive taxonomy. Do not conclude that an unfamiliar report-menu label is false, or that every changed object uses one universal category. Read the current interface and connect a label to visible feedback before adding it to a saved index.
Sort a new anomaly safely
Start with what changed rather than what the event might be called. Compare the current feed with a baseline and choose the strongest observable property:
- Position or presence: an item has moved, appeared, vanished, rotated, or changed count.
- Illumination: a light source or the area it affects now flickers or holds a different state.
- Independent motion: a shadow or silhouette changes without a matching normal source.
- Other current label: the live report menu or Journal provides a category not covered by the three public examples.
For the fourth case, record the exact in-game wording and what successful feedback demonstrated. Do not force it into object, light, or shadow merely to keep the index simple. A future update can introduce more anomalies, and the official description already says new anomalies are in development.
Record an entry from the live game
An entry becomes In-game verified when the chapter, baseline, visible change, report outcome, and current Journal support it. A clear current walkthrough can be Community reported or Community corroborated, but it should not be relabeled Official unless the creator publishes the fact.
Search each feed by evidence type
For objects, scan large silhouettes and empty spaces before tiny decorations. Use a shelf edge, wall line, doorway, or nearby furniture to judge position. Count only when the baseline makes the original number clear.
For lights, observe behavior over time. A single bright or dark frame can come from camera effects, compression, or a normal cycle. Repeated flicker tied to a fixture is a stronger comparison. Check whether the surrounding illumination changes with it.
For shadows, keep your gaze on one edge rather than chasing the shape. Independent movement against a fixed boundary is the creator’s key clue. If a visible person, fan, tree, or light explains the motion in the normal scene, it is not enough by itself.
Use the official zoom controls—Shift, L2, or double tap—only after selecting the suspicious zone. Restore wide view before moving to the next feed so the room remains connected to its full baseline.
Connect the index to chapters and Journal
The official badge list names The Residence, The Neighbourhood, The School, The Hospital, and The Mall, each with a Journal 100% goal. Open the matching chapter guide and Journal page rather than combining all entries into one undifferentiated checklist.
Before a run, note which entries the live Journal already reveals. After a successful report, compare the same chapter. The badge description says “capture,” but the public sources do not define exactly when credit is saved. Treat the current Journal feedback as the record.
If an update adds slots, keep previously verified entries but date the expanded set. Do not use an old total to declare the new Journal impossible or bugged.
Avoid false completeness
Community lists may use names that differ from the game, count visual variants separately, combine chapters, or preserve removed entries. They are useful starting points for live checks, not proof of a current complete total. A list is strongest when every row shows a chapter, location, baseline, change, report label, evidence status, and date.
Leave unknown fields blank. The player benefits more from three reliable family methods than from dozens of invented names. New contracts and anomalies are officially described as in development, so maintenance is part of the game.
Frequently asked questions
How many anomalies are there?
No official complete total is published in the sources checked on September 15, 2026. Use the live chapter Journal and dated current observations.
What anomalies are officially confirmed?
The public description explicitly names a misplaced object, a flickering light, and a shadow that moves on its own.
Does the Journal contain every anomaly?
Official badges describe capturing all known anomalies within each chapter Journal, but the public material does not define hidden entries or update behavior. Read the current Journal.