The Split No. 1 · 16 Nov 2026

Why is Estonia closing its border with Russia?

Inside Russia, 32 of 34 headlines didn’t say.

Estonia says it will close its road crossings with Russia from 1 December, after what it calls a Russian-organised attempt to set fire to the drone maker Threod Systems. CNN Defense News

The Kremlin denies Russia was behind it. Russia’s foreign ministry called the closure “Russophobia”. Reuters ERR

Headlines that say why the border is closing

  • German86%18 of 21
  • Spanish85%17 of 20
  • English80%98 of 122
  • French75%9 of 12
  • Polish62%28 of 45
  • Ukrainian57%12 of 21
  • Russian, outlets outside Russia43%29 of 67
  • Russian, outlets in Russia6%2 of 34

Share of headlines about the closure that name the incident (an attack, attempted sabotage or arson, the drone maker, or Russian services). Other languages (Swedish, Portuguese, Italian, Estonian, Lithuanian, Latvian, Dutch): 17 of 30 say why.

Outlets in Russia

Elsewhere

What headlines in Russia were about instead

  • When, where and which crossings22
  • What it will cost Estonia, and Moscow’s reaction6
  • Whether Lithuania will follow4
  • The attempted sabotage2

34 headlines from outlets in Russia, sorted by hand.

How we counted

  • 372 headlines about the closure from 278 outlets in 13 languages, from Google News searches on 15–16 November 2026 (Estonian, Latvian and Lithuanian editions included).
  • A headline “says why” if it names the incident: an attack, attempted sabotage or arson, the drone maker, or Russian services. Counted by keyword in each language; all 34 headlines from outlets in Russia were also checked by hand.
  • Outlets in Russia: web addresses ending in .ru or .рф, except The Insider, which works from outside Russia. Russian-language outlets elsewhere include the BBC, DW, Euronews, ERR and outlets in Ukraine, Belarus and Kazakhstan.
  • Headlines only: an article may explain more than its headline. The point is what a reader scanning the news would see.

All 372 headlines: headlines.json. Spotted a mistake? hello@cotext.io, and see our corrections policy.