Better tools. Better news.
Sunday, November 22, 2026 · UTC
Sports

Three freight cars derail near Rijeka station without injuries

Three freight cars derailed near Rijeka station on September 2 without injuries.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 6 placed sources from 2 publishers.
Three freight cars derailed from the tracks near the Sušak-Pećine railway station in Rijeka on September 2 in the afternoon. [1] The derailment occurred around 17:20, and authorities from the police and HŽ Infrastruktura confirmed that no one was injured. [2] The railway line between Rijeka and Škrljeva was closed for traffic following the incident. [3] No injuries were reported as a result of the derailment. [4] The specific cars that derailed were the sixth, seventh, and eighth cars of a container freight train. [5] No one was injured in the passenger train derailment at Đurđevac station. [6]
Proof6 sources · 2 publishers
What this stands on
  1. Three freight cars derailed from the tracks near the Sušak-Pećine railway station in Rijeka on September 2 in the afternoon. · Nezavisne novine
  2. The derailment occurred around 17:20, and authorities from the police and HŽ Infrastruktura confirmed that no one was injured. · Nezavisne novine
  3. The railway line between Rijeka and Škrljeva was closed for traffic following the incident. · Nezavisne novine
  4. No injuries were reported as a result of the derailment. · Večernji.hr
  5. The specific cars that derailed were the sixth, seventh, and eighth cars of a container freight train. · Večernji.hr
  6. No one was injured in the passenger train derailment at Đurđevac station. · Nezavisne novine
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 6 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Thursday, September 3, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)acefd289701292f668e60a9e127aadc458b0899c4227ef729e56960984adb2db
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.