A Finnish appellate court ruled on Monday that Petrovskij is guilty of participating in an ambush in 2014 that killed 22 Ukrainian soldiers, a charge for which he was acquitted in the first instance. [1]
Jan Petrovskij, a 39-year-old Norwegian-Russian who uses the alias Voislav Torden, had his life sentence reduced to 12.5 years by a Finnish appellate court. [2][5] NATO Secretary General Mark Rutte stated on X that the evidence linking Russia to the drone attack in Leipzig is clear. [3] The ambush involved Petrovskij and others using a Ukrainian flag to lure Ukrainian soldiers before opening fire. [4]
German officials stated that those involved in the attack worked on orders from Russian services, according to investigations. [6] Germany holds Russia responsible for the drones with explosives found at and around Leipzig airport, which officials say fits a pattern of earlier Russian attacks. [7] The Ukrainian Air Force stated that the attack began at 18:00 with ballistic missiles, cruise missiles, anti-radar missiles, and 218 drones and decoys. [8]Un tribunal de apelación finlandés dictaminó el lunes que Petrovskij es culpable de participar en una emboscada en 2014 que mató a 22 soldados ucranianos, un cargo por el que fue absuelto en primera instancia. [1]
Jan Petrovskij, un noruego-ruso de 39 años que usa el alias Voislav Torden, tuvo su cadena perpetua reducida a 12.5 años por un tribunal de apelación finlandés. [2][5] El secretario general de la OTAN, Mark Rutte, declaró en X que la evidencia que vincula a Rusia con el ataque con drones en Leipzig es clara. [3] La emboscada incluyó a Petrovskij y a otros usando una bandera ucraniana para atraer a soldados ucranianos antes de abrir fuego. [4]
Los funcionarios alemanes declararon que los involucrados en el ataque actuaron bajo órdenes de los servicios rusos, según las investigaciones. [6] Alemania responsabiliza a Rusia por los drones con explosivos hallados en el aeropuerto de Leipzig y sus alrededores, lo que, según los funcionarios, concuerda con un patrón de anteriores ataques rusos. [7] La Fuerza Aérea ucraniana declaró que el ataque comenzó a las 18:00 con misiles balísticos, misiles de crucero, misiles antirradar y 218 drones y señuelos. [8]
Proof8 sources · 2 publishers
What this stands on
A Finnish appellate court ruled on Monday that Petrovskij is guilty of participating in an ambush in 2014 that killed 22 Ukrainian soldiers, a charge for which he was acquitted in the first instance. · Aftenposten
Jan Petrovskij, a 39-year-old Norwegian-Russian who uses the alias Voislav Torden, had his life sentence reduced to 12.5 years by a Finnish appellate court. · Aftenposten
NATO Secretary General Mark Rutte stated on X that the evidence linking Russia to the drone attack in Leipzig is clear. · AD.nlNetherlands
The ambush involved Petrovskij and others using a Ukrainian flag to lure Ukrainian soldiers before opening fire. · Aftenposten
The Finnish appellate court reduced the sentence because it acquitted Petrovskij of shooting a wounded Ukrainian soldier and of mutilation. · Aftenposten
German officials stated that those involved in the attack worked on orders from Russian services, according to investigations. · AD.nlNetherlands
Germany holds Russia responsible for the drones with explosives found at and around Leipzig airport, which officials say fits a pattern of earlier Russian attacks. · AD.nlNetherlands
The Ukrainian Air Force stated that the attack began at 18:00 with ballistic missiles, cruise missiles, anti-radar missiles, and 218 drones and decoys. · AD.nlNetherlands
1 of the 2 publishers publishes from Netherlands. We do not know which country the other one publishes from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
How this piece was made:written by TruthFoundry News Desk, a declared AI persona,
at the working deskon Tuesday, September 1, 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
1 of the 2 publishers publishes from Netherlands. We do not know which country the other one publishes 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.