Jonah Rourke is a railroad man, and railroad men don’t believe in miracles.
So when his sister, Nell, disappears into a town that shouldn’t exist—one that won’t let anyone in, and won’t let anyone out, Jonah follows her anyway. Past the last streetlamp. Past the last honest mile. Onto a road that counts down like an execution and charges for every step.
On this road, you don’t pay in money.
You pay in pieces of yourself.
Because something is coming. Something hungry. Something that doesn’t care who you are, only what you’re willing to surrender to keep moving.
Jonah isn’t a hero. He isn’t chosen. He’s a worker with blood under his nails and grief in his mouth, chasing the only person who ever truly knew him. To reach Nell, he’ll have to cross a world built from bargains and monsters—and face the one truth he’s avoided his whole life.
The question isn’t whether he can save his sister.
It’s what he’ll have left to call her name when he does.
Alexander Salazar is a new author, which is rather like being a new black hole - full of the unknown and dense with potential. He once tried to write serious literature, but was distracted by something shiny, possibly a metaphor. When not wrangling words or attempting to explain to his two dogs why character arcs matter, Alexander can be found tapping away at the keyboard. He's written two books, The Last Stand Of Earth and The Last Stand Of Hope, with many more on the way.
It had such promise at the start, and maybe I just didn't get it...but there were no stakes, no danger, nothing made any sense and I just kept waiting for something to happen (which didn't).
I think this one is made for the boys, as it said on Amazon 13-18 year old. I got through it, and understand that this is about him fighting an internal battle. I just don’t know how to feel about the fact that he didn’t really lose much and the fact that all that his sister did was for nothing, would he even go there if she didn’t go first? She was his whole motivation? I thought at the end he would wake up in his bed and it was all a dream, he did not, but he could have, would not change the story if you ask me. I just notice women probably aren’t the targeted audience here, and that’s ok, but sadly can’t give it more stars, since I would not recommend it to any woman.
This entire review has been hidden because of spoilers.
came here to complain about Oyun Book 3… and got ambushed by a masterpiece about a nightmare train
I’m one of those people who’s annoyingly loyal to the Oyun Chronicles. I’m in deep. I want the jokes, the chaos, the momentum—most of all I want the third book. So when I saw the author released The Train That Eats Names instead of finishing the next Oyun installment, my initial reaction was basically: Sir. Please. We were in the middle of something.
And then I did what every devoted reader does when they’re “mad” at an author: I bought the book anyway.
Which turned out to be an incredible mistake, because now I’m not just waiting for Book Three—I’m also staring into the middle distance thinking about rail lines and memory and the terrifying ways a person can disappear while still technically standing upright.
This book is a hard left turn from Oyun. The humor takes a backseat. The sci-fi swagger is gone. In its place is something darker and stranger: a 1930s horror-western with a quiet, literary confidence—more Cormac McCarthy-adjacent in mood than anything I expected from this author. The prose is lean and deliberate. The atmosphere is thick with dust and dread. The story doesn’t rush to scare you—it lets the fear accumulate, like a distant engine you can’t stop hearing once you’ve noticed it.
And the train? It’s not just a monster with a cool hook. It feels like an idea made physical—erasure, forgetting, the terror of losing your name and everything attached to it. The horror works because it’s personal. The sibling relationship at the center gives the whole thing a heartbeat, and it’s the reason the book sticks. You’re not reading to see what the train does next—you’re reading because you can feel what the characters are willing to do for each other, and you’re scared of the answer.
By the time I finished, I wasn’t thinking, “Why didn’t you write Oyun Book Three?” I was thinking, “Oh. You can write this, too.” It’s the kind of pivot that makes you respect the author more—like watching a comedian walk onstage with a guitar and then casually play something devastating.
So yes, I loved it. More than I wanted to. And now I’m doubly cursed: I need this author to keep writing dark, strange, gorgeous books like this…
…and I still need The Last Stand of Harper.
Five stars. Consider my complaint officially upgraded to admiration.
As a genre, Western horror has always been the “weird cousin” at the campfire—older than people think, and at its best when it leans into what the West already is: isolation, lawlessness, long distances, and the feeling that if something goes wrong out here, no one is coming. You can trace that strain from early dime-novel pulp and “Weird West” tales, through modern touchstones like Bone Tomahawk and The Dark Tower—and even the grim, mythic fatalism that haunts Blood Meridian. Western horror works because the frontier is already a haunted house; it just doesn’t have walls.
That’s why The Train That Eats Names feels like it belongs in the tradition and quietly subverts it.
On one hand, it’s perfect Western horror: a hard road, an America that feels sunbaked and remote, strange towns with stranger rules, and a protagonist who reads like a working man caught in something bigger than him. It delivers that classic Western tension where every stop is a test and every horizon looks like it might hide trouble. The atmosphere is all dust-and-dread, and the story has that “campfire tale that got too real” quality Western horror thrives on.
But where it subverts the genre is in what it makes the frontier mean. A lot of Western horror is about physical threat—outlaws, monsters, the savage unknown. This book is scarier in a more intimate way: it treats the road like a psychological landscape. The horror isn’t just what Jonah might run into; it’s what the journey might take from him—identity, certainty, even the basic safety of language and reality. Instead of the usual Western arc of “civilization vs wilderness,” it becomes “self vs erasure.” The frontier isn’t land to conquer. It’s a system you survive, a gauntlet that keeps asking what you’re willing to trade to keep moving.
That’s what makes it such a strong entry in the Western horror lineage: it gives you the genre’s best pleasures—lonely travel, eerie encounters, folklore-level strangeness—while pushing the fear inward, turning the West into a mirror instead of a battlefield. It’s both a love letter to the form and a sharp evolution of it.
If you’ve ever thought, “Westerns are already scary, they just don’t admit it,” this is the book that admits it—and then makes it worse, in the best possible way.
What I loved most about The Train That Eats Names is how strong the villains and side characters are—especially the clean suit man. He’s not necessarily the “final boss” of the story, but he might be the most memorable presence in the whole book. He’s such a unique character: polished, controlled, and somehow tragic underneath it all. The detail that you can tell he’s near when you smell the lye is genius—it’s the kind of sensory warning that instantly makes your stomach drop. And the way he wields shadows like weapons is flat-out cool in a terrifying, folklore-ish way. Every time he’s around, the book’s tension spikes without needing to shout about it.
Without spoiling the ending, I also loved the way Jonah interacts with him near the end. It’s one of those scenes that says a ton with very little—charged, strange, and oddly emotional—and it made the clean suit man feel like more than a simple threat. He’s scary, yes, but he also feels like he has rules, history, and a flaw that keeps pulling him toward the same choices.
And he’s just one part of why this book feels so alive. The side characters and set pieces are incredible. The Orphan Court is such a disturbing, brilliant idea—creepy in a quiet way, like a children’s rhyme that grew teeth. The river market, too, is unforgettable: the kind of scene you can visualize perfectly, down to the damp air and the uneasy energy in the crowd, and you can tell there’s a whole economy of desperation operating under the surface.
That’s what makes this novel work so well: so much of the story is told through the details of the world. It doesn’t over-explain, but it’s insanely vivid, and every strange encounter feels like it’s revealing something about humanity—what people trade, what they hide, what they’ll do to survive, and what it costs them. By the time I finished, I wasn’t just impressed by the plot—I felt like I’d walked through a weird, haunted America where every mile had a story and eve…
I loved The Train That Eats Names in audio—like, devoured it. This is one of those stories where the format actually makes it creepier, because hearing it out loud turns the dread into something you can’t shake off. I was listening with headphones and there were moments I genuinely paused because I thought I heard something behind me. (I did not. I hope.)
The narrator is perfect for the tone: gritty without being try-hard, emotional without going full theater kid, and really good at building that slow-burn tension. The pacing is so steady and inevitable—like a train you can hear coming long before it arrives. The scary parts aren’t cheap “boo!” moments either. It’s that creeping, folklore-ish horror where the world feels slightly wrong, and the narrator sells that feeling so well.
Also: the 1930s vibe comes through hard in the best way. The rail-yard life, the work, the exhaustion, the details—everything feels lived-in. If you’re even remotely into trains or railroad history, the audiobook makes it feel like you’re right there in the dust and soot. And if you’re not a train person? You’ll become one for the duration of this book because it’s just so immersive.
But what made me really love it is that it’s not just “scary train goes brrr.” The emotional core is the sibling bond, and the audiobook performance makes that relationship hit. You can hear the loyalty, the fear, the way love turns into desperation when the stakes get too big. It made the story feel human even when it’s being deeply, aggressively supernatural.
There are little flashes of dry humor too—more like survival humor than comedy—and the narrator threads it in perfectly so it doesn’t break the mood, it just makes the characters feel real.
Five stars. If you want a horror-western that’s genuinely unsettling and somehow also kind of devastating, the audiobook is the move. Just… maybe don’t listen alone on a dark road.
This entire review has been hidden because of spoilers.
I’m still the person who mostly reads the classics—Ernest Hemingway, John Steinbeck, the writers who believed a sentence should carry its own weight and never ask for applause. After how much I admired The Seed in the Killing Ground, a friend told me to try The Train That Eats Names with the same promise: “It reads like an old book—just… haunted.”
They were right.
This novel has the cadence and restraint of something older—clean lines, deliberate repetition, the sort of prose that can feel plain until you realize it’s doing something precise. It doesn’t chatter. It doesn’t over-explain. It lets the landscape and the silences and the small human decisions build their own pressure. That’s a quality I associate with the writers I return to: the confidence to be spare, and the discipline to let implication do the work.
But make no mistake—this is horror, and it’s deeply unsettling. Not the loud, modern kind that leans on shock, but a quieter dread that feels folkloric and inevitable, like an old warning told by someone who survived it. The central conceit—names, identity, what it means to be “kept” or “taken”—lands as both story and metaphor, and the book has an emotional undercurrent that surprised me as much as the fear did.
What struck me most is how human it remains beneath the strangeness. It understands grief. It understands devotion. It understands the stubbornness of love, especially between siblings, and how far a person will go to retrieve someone from a dark place. By the end, the book felt less like a clever premise and more like a hard, old tale—one you’d hear and carry with you, partly because it frightened you and partly because it told you something true.
I don’t say this lightly: it feels timeless. A modern story told in a classic voice, with real literary intention and a genuinely haunting effect.
Haunting Tracks of Love, Loss, and Quiet Devastation
I went into The Train That Eats Names thinking I was getting a strange, atmospheric horror story—and I did. But I wasn’t prepared for how emotional it would be.
There’s something about this book that gets under your skin quietly. It doesn’t force anything. It doesn’t beg you to feel. It just lets you walk beside Jonah as he moves through this broken, haunted world, and somewhere along the way you realize you’re not just reading—you’re carrying it with him.
The horror is there, and it’s real. The kind that lingers. The kind that feels older than the story itself. The train, the places he passes through, the people he meets—they all feel like fragments of something larger and more painful than just a “plot.” But what makes it hit is that none of it feels random. Everything feels connected to something human: memory, identity, love, loss.
And Jonah… that’s where it really got me. His drive to find Nell doesn’t feel like a heroic quest. It feels like something deeper, more desperate. Like he doesn’t have a choice. Like turning back isn’t even a thought he’s allowed to have. That kind of love—the stubborn, painful kind—is what gives the story its weight.
There are moments in this book that just sit with you. Quiet ones. The kind where not much is happening on the surface, but everything is shifting underneath. You start to feel how much is being lost, piece by piece, and it’s not loud or dramatic—it’s slow and inevitable.
And the ending… it doesn’t try to fix everything. It doesn’t pretend the pain goes away. But it gives you something real to hold onto. Something honest. And that honesty is what made it hit so hard.
I didn’t expect to feel this much reading a book with a title like this. But I’m really glad I did.
Five stars. It’s haunting, beautiful, and quietly devastating in the best way.
I’m a working cowboy. Most nights, after the fences are checked and the animals are fed, I’m tired enough that I don’t want much more than a chair and some quiet. I picked up The Train That Eats Names thinking it would be a strange western with a bit of grit and maybe a few good scares.
I didn’t expect it to hit as close to home as it did.
There’s something about reading this book at night, after a long day on the farm, that just fits. The dust, the rail lines, the sense of distance and silence — it all feels familiar. The story is grounded. The work feels real. The stubbornness feels real. And when the world starts bending into something darker and more mystical, it doesn’t lose that foundation.
What surprised me most was how deeply I connected to the man at the center of it. His fight isn’t just against something out there on the tracks — it’s against what’s happening inside him. The weight he carries, the way he keeps moving even when he’s worn down, the battle with depression that hums under the surface — that part felt honest. Not dramatic. Not overplayed. Just honest.
The monsters are unsettling, sure. The church, the strange places along the road, the feeling that something is always watching — it’s good, eerie stuff. But the heart of it is a man trying to hold onto himself and the people he loves when the dark is pressing in. That’s a fight I understand.
I found myself reading longer than I meant to, more than a few nights in a row, just to see how it would turn out. And when it did, it didn’t feel cheap or easy. It felt earned.
Loved it. A hard, thoughtful story with grit and soul. It’s staying on my shelf.
I grabbed The Train That Eats Names because it popped up on the new releases list and the cover stopped me cold. It’s one of those covers that looks like it belongs on a shelf with the “serious” books—minimal, eerie, and confident. I figured worst case I’d get a cool-looking paperback.
I wasn’t ready for how much this story would hit me.
Yes, it’s creepy and original (the central idea is unsettling in the best way), and the writing has this stripped-down, dusty-road intensity that makes everything feel inevitable. But what really got me—what made it stick—was the emotional core underneath the horror. The relationship at the center of the book and the way it explores fear, helplessness, and love felt… uncomfortably familiar.
Quick personal note (nothing graphic): I have a sibling who struggles with depression, and there were moments in this book that felt like they understood something I’ve had trouble putting into words—the way it can feel like you’re watching someone you love walk down a road you can’t follow for them, the way you’d do anything to pull them back, even when you know you can’t “fix” it for them. The book doesn’t preach. It just shows the weight of carrying someone, and being carried, and the way love can be both an anchor and a bruise.
I finished it in that weird state where you’re satisfied as a reader but also a little shaken as a human. Came for the cover. Stayed for the atmosphere. Remembered it for the heart.
What I loved most about The Train That Eats Names is how convincingly real it feels — right up until something impossible leans in close and breathes on your neck.
The setting is grounded in dust and iron and the practical rhythms of rail life. The people feel real. The conversations feel real. Even the fear feels real. And then — without fanfare — the world shifts. A church becomes something hungry. A court of orphans feels older than it should be. A river market lined with jars becomes a place that hums with quiet, unsettling intention. None of it feels random or flashy. It all feels like folklore growing naturally out of the soil.
That’s the magic trick here: the monsters don’t crash into the story — they seep into it. The church that tries to eat Jonah isn’t just a spectacle; it’s horrifying because it exists in a world that otherwise makes sense. The Court of Orphans isn’t just creepy — it feels mythic, like something that has always been there, waiting to be noticed. And the river market, with its many jars, lingers in the mind long after you’ve turned the page.
The book blends realism and the supernatural so seamlessly that you stop asking “Is this possible?” and start asking “What does this mean?” That’s when you know a story has you.
It’s eerie. It’s imaginative. It’s emotionally grounded. And it proves that monsters are most powerful when they grow out of something real.
Some books feel modern no matter what decade they’re set in. The Train That Eats Names feels like it’s been sitting on a shelf for ninety years, waiting for someone brave or foolish enough to open it.
The prose has that stripped-down, timeless quality—clean sentences, heavy pauses, and a voice that trusts you to keep up. The dread is slow and certain. The rules of the world arrive the way real superstition arrives: not with an info-dump, but with warnings, half-truths, and people refusing to meet your eyes.
What I loved most is the way the horror stays conceptual—names, records, what it means to go “unwritten”—but still hits you emotionally. The story gets under your skin because it’s not just scary; it feels inevitable, like the land itself is participating.
By the end I felt like I’d read a piece of folklore that was never supposed to be written down. Five stars for originality, atmosphere, and a voice so confident it feels carved out of the setting.
This is the kind of book you finish and then sit there for a minute like, “Okay, wow, I need a glass of water and possibly a priest.”
The Train That Eats Names has that stripped-down, haunting prose that makes even a simple description feel loaded with dread. The setting is brutal in a quiet way—wide open, sun-bleached, and lonely—and the horror doesn’t come from jump scares. It comes from the rules. From language. From the sense that the world is keeping a ledger and you don’t want to be on it… but you also don’t want to be missing from it.
Jonah’s journey feels like a fable with teeth. Every time he thinks he’s learned the shape of the danger, the book shows him there’s a deeper layer. The idea that refusing a name has a cost—beautiful and horrible. I love when horror is conceptual like that, because it’s harder to shake.
This is literary, creepy, and weird in the exact right way. If you like atmospheric horror with mythic energy and prose that hits like a hammer, five stars.
After calling The Seed in the Killing Ground my best book of the year so far, I picked up The Train That Eats Names expecting something good—but I wasn’t prepared for how profoundly it would hit me.
This book is scary, but not in a cheap, jump-scare way. It’s the creeping, psychological kind of fear that gets under your skin because it feels true. The whole journey reads like a beautiful allegory for depression—the way the road narrows, the way the world feels distorted, the way silence and dread become their own predators. Jonah’s persistence, his exhaustion, his determination to keep going even when it feels impossible… it connected with me on a level I didn’t expect from a horror novel.
It’s also genuinely beautiful in its restraint. The imagery is haunting, the symbolism is sharp without being preachy, and by the end I felt both unsettled and strangely comforted—like the book understood something hard and put it into story form.
I loved it. And I’m officially a fan of whatever this author writes next.
I came back for The Train That Eats Names right after finishing The Seed in the Killing Ground,
I came back for The Train That Eats Names right after finishing The Seed in the Killing Ground, and somehow this one grabbed me even harder. It’s not “jump-scare” horror—it’s creeping, psychological, can’t-look-away dread, and I was completely sucked in. Between Seed and Train, I tore through both books in three days, which honestly never happens to me anymore. Gripping, haunting, and exactly what I needed at this point in my life.
This book feels like finding a prayer written in chalk on a boxcar and realizing the chalk is still wet. It’s spare, mean in the best way, and strange with purpose—like the story is watching you back. The language is powerful, the dread is patient, and by the end I wasn’t sure if I’d finished the book or if the book had finished me. Loved it. Immediate favorite in the “quiet horror that is beautifully profound” category.
After Seed, I picked this up and it delivered in a totally different way—creepy, psychological, and unbelievably atmospheric. Jonah is a great lead, and the story is packed with haunting images and smart metaphors that stick with you long after you’re done. It’s not jump-scare horror; it’s the slow dread that gets under your skin. Loved it, and I’m officially buying whatever this author writes next.
I came back for The Train That Eats Names right after finishing The Seed in the Killing Ground, and somehow this one grabbed me even harder. It’s not “jump-scare” horror—it’s creeping, psychological, can’t-look-away dread, and I was completely sucked in. Between Seed and Train, I tore through both books in three days, which honestly never happens to me anymore. Gripping, haunting, and exactly what I needed at this point in my life. 1:07 AM 1:07 AM
The Train That Eats Names feels like a story you weren’t supposed to hear—something passed down in whispers that somehow made it onto paper. It’s eerie, precise, and quietly devastating. The kind of book that doesn’t chase you, but still manages to catch you anyway. So much happens. It’s so interesting in the journey. I almost felt like I was reading a new folk lore tale. 10/10 recommend reading this.