The 10:12 Problem
In early 2019, a watch repair shop in Des Moines logged an unusual service request.
The item was a wall clock—mass-produced, mid-1980s, battery-powered. Nothing collectible. Nothing mechanically complex. The owner’s complaint was brief:
Clock intermittently runs backward.
The technician assumed user error or a failing quartz movement. These clocks are cheap, disposable. You replace the mechanism, not diagnose it.
Except the clock worked perfectly on the bench.
The owner, a woman in her forties, returned two weeks later.
She reported that the clock only reversed at night, usually between 11:30 p.m. and midnight. When it happened, the ticking didn’t change speed—it simply reversed direction. Second hand first. Then minute. Then hour.
By morning, it corrected itself.
The technician replaced the movement anyway.
The problem followed the clock.
Skeptical explanations are easy to list.
Temperature fluctuations can affect cheap components. Low batteries can cause stuttering or reversal. Electrical interference is known to disrupt quartz timing.
The owner changed batteries daily.
She unplugged nearby electronics.
She moved the clock to different rooms.
The reversal continued.
The first documentation came when the owner set up a camera.
The footage shows the clock behaving normally until 11:47 p.m. At that moment, the second hand hesitates, then begins ticking counterclockwise. No jump. No glitch.
Smooth. Intentional.
At 11:53, the minute hand follows.
The hour hand lags behind, then complies.
The camera timestamp continues forward.
The clock does not.
What drew wider attention was not the reversal itself, but its precision.
Each night, the clock rewound to the same point: 10:12 p.m.
It never went further.
Once it reached that time, it stopped.
Not paused.
Stopped.
The owner described the room as feeling “held,” like something unfinished was being revisited.
A horologist consulted on the case confirmed the mechanism could not do this under normal conditions. Even deliberate tampering would produce erratic movement, not coordinated reversal across all hands.
More troubling was what appeared after several weeks.
The owner began noticing discrepancies.
Her phone logs showed calls she didn’t remember making—short, unanswered. Her fitness tracker recorded steps during the rewind period, despite her being asleep.
And always, when the clock stopped at 10:12, she reported a strong sense of recognition.
As if that time mattered.
Attempts to remove the clock failed.
When stored in a drawer, the sound of ticking continued faintly through the wood. When the clock was disassembled, the hands were found repositioned in the morning.
Eventually, the owner stopped trying to correct it.
She began watching instead.
The final incident occurred on April 3rd.
That night, the clock reversed as usual.
But it did not stop at 10:12.
It continued.
At 9:58, the owner woke abruptly, heart racing. At 9:41, she reported feeling a pressure in the room, like air thickening. At 9:23, the camera feed distorted briefly.
At 9:17, the clock stopped.
The owner later recalled that time clearly.
“That’s when I decided not to leave.”
There is no official record of what that means.
The clock was surrendered to the shop the following morning.
It has not reversed since.
It runs forward now. Reliably. Boringly.
But technicians note that it consistently loses time.
Exactly fifty-five minutes per night.
Always settling at 10:12 p.m.
3 responses to “Ep. 7: The 10:12 Problem”
I don’t care what the explanation is, I wouldn’t keep that clock in my house. Something about “watching instead” feels like giving it permission.
Memory gaps and sleep disturbances can absolutely produce the sensations described. Still, the clock continuing to lose the same chunk of time afterward is unnerving.
This sounds like a bad movement and a stressed owner reading too much into it. Cheap clocks do weird stuff all the time.