Telegram RegisterThe public register of Telegram
Telegram profile photo for 🇷🇺IL RUSSO🇷🇺

Channel

🇷🇺IL RUSSO🇷🇺

@i20028843

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

13,457subscribers

-480 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001590974429
TypeChannel
Username@i20028843
Created13 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/i20028843

Topic

International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ClashReport/919668 Aug 2026, 18:15 UTC@i20028843/310803 · this entry8 Aug 2026, 18:46 UTC1.0031 minutes
@ClashReport/9227011 Aug 2026, 19:04 UTC@i20028843/311221 · this entry11 Aug 2026, 19:22 UTC1.0017 minutes
@ClashReport/9367825 Aug 2026, 20:16 UTC@i20028843/312979 · this entry25 Aug 2026, 20:18 UTC1.0072 seconds
@ClashReport/10278524 Oct 2026, 12:01 UTC@i20028843/323365 · this entry3 Nov 2026, 03:33 UTC1.0010 days
@ClashReport/10278724 Oct 2026, 12:03 UTC@i20028843/323366 · this entry3 Nov 2026, 04:02 UTC1.0010 days
@ClashReport/10278624 Oct 2026, 12:02 UTC@i20028843/323367 · this entry3 Nov 2026, 04:33 UTC1.0010 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@ClashReport16 (8/8 hand-verifiable sample passed)1.001.9 hours@ClashReport (16–0)
@news_israel_europe6 (6/6 hand-verifiable sample passed)1.009 days@news_israel_europe (5–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 21 of the 21 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 786 comparable posts for this entry, running 5 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

13,45713,95313,7056 August 202611 November 2026
66 measurements spanning 97 days, net -480. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 13,383–14,027 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
11 Nov 2026, 08:1113,457-8
9 Nov 2026, 11:5013,465-11
8 Nov 2026, 00:1013,476-13
6 Nov 2026, 20:2513,489-7
5 Nov 2026, 22:0613,496-4
4 Nov 2026, 19:5613,500-7
3 Nov 2026, 21:0613,507+1
2 Nov 2026, 18:0813,506-4
1 Nov 2026, 18:5713,510-7
31 Oct 2026, 18:4913,517-2
30 Oct 2026, 15:2813,519-7
29 Oct 2026, 16:4413,526-5
28 Oct 2026, 14:5613,531-4
27 Oct 2026, 17:1713,535-5
26 Oct 2026, 16:4013,540-8
25 Oct 2026, 16:2013,548-6
24 Oct 2026, 14:2613,554-3
23 Oct 2026, 15:0413,557-4
22 Oct 2026, 14:4613,561-7
21 Oct 2026, 06:0013,568first reading

Engagement

1,228 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 67 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.72%
avg views ÷ 13,457 subscribers
Avg views / post
231
315 posts measured
Reaction rate
4.32%
reactions ÷ views · ER floor
Posts in window
315
of 1,228 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 295 of 315 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held1,228 (5 August 2026 – 11 November 2026)
Views total72,745
Reactions total2,950
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 07:56 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
56m 25s
Average length
27s

Measured directly from 125 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

11,172 reactions across 938 posts, in 30 distinct kinds. The most used accounts for 50.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5,62950.4%
🤣2,73924.5%
💯6145.50%
custom 50220702767041754143142.81%
🤡2932.62%
💩2882.58%
🤬2712.43%
👏1811.62%
🖕1541.38%
custom 52964334661774951651341.20%
😁1080.967%
👍930.832%
❤‍🔥870.779%
✍510.456%
🫡430.385%
👎340.304%
🙏310.277%
🥴240.215%
😎140.125%
⚡130.116%
10 further kinds570.51%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 939 of the 1,000 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 11,172 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 10 August 2026 to 11 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 15 of 315 posts held from the last 30 days (4.76%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 07:51 UTC17 views3 reactionsread 11 November 2026

📺New explosions have occurred in Kharkiv. Explosions have also been reported in the Zhytomyr region and in Pavlograd, in the Dnipropetrovsk region

🔥3

11 Nov 2026, 07:45 UTC33 views6 reactionsread 11 November 2026

📺In the Odessa Oblast, 135,000 customers were left without power due to new attacks on energy infrastructure, according to the regional administration

🔥6

11 Nov 2026, 07:37 UTC52 views5 reactionsread 11 November 2026

📺New explosions were heard in Kyiv, the Odessa region, and the Vinnytsia region

🔥5

11 Nov 2026, 07:35 UTC63 views7 reactionsread 11 November 2026
Video

📺The Russian armed forces have neutralized a hideout containing Ukrainian soldiers and two drone command centers in the Kramatorsk sector. The enemy was seeking refuge among the ruins of a factory, in an abandoned residential neighborhood, and in a wooded area. The target was struck by drones and an "Msta-B" howitzer, according to the Ministry of Defense

🔥7

11 Nov 2026, 07:18 UTC109 views10 reactionsread 11 November 2026

📺More explosions in Kyiv Attacks were also carried out against targets in Mykolaiv

🔥10

11 Nov 2026, 07:17 UTC109 views9 reactionsread 11 November 2026

📺Attacks are being carried out against targets in Kharkiv. Targeted attacks have been carried out against targets in the Vinnytsia region

🔥9

11 Nov 2026, 07:07 UTC135 views10 reactionsread 11 November 2026

📺The Iranian army announces that a vessel caught fire in the Strait of Hormuz after attempting to cross the strait illegally

🔥10

11 Nov 2026, 07:00 UTC146 views10 reactionsread 11 November 2026
Photo

📺Yemeni forces have reached the Huwayrib area in Lahij's al-Mudharabah district and are advancing towards Khawr Umayrah to complete the encirclement of thousands of Saudi-aligned troops stationed in al-Mudharabah and advancing in Dhubab and al-Mandab

🔥10

11 Nov 2026, 06:58 UTC133 views13 reactionsread 11 November 2026

📺This morning, there was another attack on bridges in the Odessa region. This time, the Mayaki and Zatoka bridges were struck by Dan-T, UMVK, and Geran drones, according to the Telegram channel "Chronicles of Geran

🔥13

11 Nov 2026, 06:55 UTC135 views10 reactionsread 11 November 2026
Photo

📺Yemeni forces have made significant gains on the ground, reaching Jabal Kharaz and approaching Khawr Umayrah. This places Saudi-aligned forces in the Bab al-Mandab and Dhubab areas, as well as those remaining in al-Mudharabah, at risk of encirclement

🔥10

11 Nov 2026, 06:53 UTC141 views9 reactionsread 11 November 2026
Photo

📺Yemeni forces have taken control of the Sarih junction, 20 kilometers from the sea

🔥9

11 Nov 2026, 06:40 UTC148 views13 reactionsread 11 November 2026

📺A missile attack on the Penza region was repelled," the governor said. I would like to thank the Russian Ministry of Defense personnel who ensure our air defense. The missiles aimed at the Penza region did not reach their targets. Thank you to everyone who protects the peace of mind of our citizens for the precision and coordination of their actions

💯13

Showing the 12 most recent of 1,228 posts we hold for @i20028843. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

The Right People Z
@the_Right_People · 36,797
Telegram ranks this channel #8 of 73 here — alongside 72 others — read 2 September 2026
UKR LEAKS_eng
@ukr_leaks_eng · 74,944
Telegram ranks this channel #8 of 81 here — alongside 80 others — read 19 August 2026
Military Summary
@militarysummary · 76,966
Telegram ranks this channel #8 of 77 here — alongside 76 others — read 19 August 2026
MoD Russia
@mod_russia_en · 93,800
Telegram ranks this channel #9 of 80 here — alongside 79 others — read 16 August 2026
AMK Mapping
@AMK_Mapping · 61,326
Telegram ranks this channel #11 of 78 here — alongside 77 others — read 23 August 2026
Rybar in English
@rybar_in_english · 77,360
Telegram ranks this channel #18 of 81 here — alongside 80 others — read 18 August 2026
Slavyangrad
@Slavyangrad · 111,582
Telegram ranks this channel #20 of 81 here — alongside 80 others — read 14 August 2026
Intel Slava
@intelslava · 385,509
Telegram ranks this channel #23 of 84 here — alongside 83 others — read 10 August 2026
Suriyakmaps
@Suriyak_maps · 48,122
Telegram ranks this channel #24 of 80 here — alongside 79 others — read 27 August 2026
RT Documentary
@militarywave · 41,230
Telegram ranks this channel #25 of 84 here — alongside 83 others — read 29 August 2026
Ukraine Watch
@ukraine_watch · 69,155
Telegram ranks this channel #25 of 81 here — alongside 80 others — read 20 August 2026
DD Geopolitics
@DDGeopolitics · 189,932
Telegram ranks this channel #27 of 84 here — alongside 83 others — read 11 August 2026
Two Majors - English Channel
@two_majors · 47,608
Telegram ranks this channel #28 of 82 here — alongside 81 others — read 27 August 2026
Источни Фронт
@istocni_front · 65,513
Telegram ranks this channel #30 of 84 here — alongside 83 others — read 28 September 2026
Node of Time EN
@node_of_time_en · 19,844
Telegram ranks this channel #31 of 83 here — alongside 82 others — read 30 September 2026
World Pravda
@worldpravda · 53,476
Telegram ranks this channel #32 of 82 here — alongside 81 others — read 24 August 2026
Victor vicktop55
@vicktop55 · 26,853
Telegram ranks this channel #33 of 84 here — alongside 83 others — read 11 September 2026
InfoDefenseENGLISH
@infodefENGLAND · 50,396
Telegram ranks this channel #33 of 85 here — alongside 84 others — read 25 August 2026
🇷🇺☦️ Russian БaZa ☦️🇷🇺
@RussianBaZa · 20,594
Telegram ranks this channel #35 of 83 here — alongside 82 others — read 28 September 2026
Fearless John - @European_dissident
@European_dissident · 69,221
Telegram ranks this channel #35 of 83 here — alongside 82 others — read 20 August 2026
The Islander
@TheIslanderNews · 61,594
Telegram ranks this channel #36 of 83 here — alongside 82 others — read 22 August 2026
War Leaks 18+ (Channel)
@warleaks11 · 66,943
Telegram ranks this channel #37 of 74 here — alongside 73 others — read 27 August 2026
🇦🇺AussieCossack🇷🇺
@AussieCossack · 70,529
Telegram ranks this channel #47 of 82 here — alongside 81 others — read 20 August 2026
SITREP - Independent OSINT Channel
@sitreports · 22,862
Telegram ranks this channel #49 of 80 here — alongside 79 others — read 19 September 2026

This channel appears in 36 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 11 November 2026 — this entry's latest reading, not the date you are reading this.

“🇷🇺IL RUSSO🇷🇺” (@i20028843), 13,457 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/i20028843.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.