Telegram RegisterThe public register of Telegram
Telegram profile photo for Досье Шпиона

Channel

Досье Шпиона

@dosye_shpiona

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Referenced elsewhere · Cite this entry

83,217subscribers

+1,750 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001789650068
TypeChannel
Username@dosye_shpiona
DescriptionКанал Досье Шпиона – телеграм-канал сотрудника одной из специальных служб. Я среди вас и много про вас знаю.
Created5 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/dosye_shpiona

Topic

International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 80% 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 why it has no browse page of its own yet.

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.

Views per post sit far above this size band

161,000 average views per post against 83,217 subscribers — an engagement rate of 194.0%. Across the 8,379 registered channels in the same cohort — 31,624–99,993 subscribers, posting mainly in Russian — the middle half sit between 5.06% and 21.0%, with a median of 10.6%.

What this was computed from
Window30 days (25 August 2026 – 24 September 2026)
Posts measured10 of 10 published in the window (0 exact, 10 rounded by Telegram)
Views totalled1,614,000
Mature posts only194.0% over 10 posts read at least 24h after publication
Subscribers83,217 measured 17 September 2026
Cohortb31623:rus · 8,379 channels · p10 2.52% · p25 5.06% · p50 10.6% · p75 21.0% · p90 35.8%
Position in cohort99.940th percentile · 18.4× the cohort median
Uncertainty±0.051% of the figure, from Telegram’s rounding
Post languageRussian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 24 September 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

80,73483,21781,975.56 August 2026 — 81,467 subscribers6 August 2026 — 81,467 subscribers6 August 2026 — 81,439 subscribers7 August 2026 — 81,401 subscribers8 August 2026 — 81,366 subscribers9 August 2026 — 81,335 subscribers10 August 2026 — 81,286 subscribers11 August 2026 — 81,240 subscribers12 August 2026 — 81,200 subscribers14 August 2026 — 81,161 subscribers15 August 2026 — 81,117 subscribers17 August 2026 — 81,046 subscribers18 August 2026 — 80,960 subscribers19 August 2026 — 80,932 subscribers20 August 2026 — 80,939 subscribers21 August 2026 — 80,932 subscribers22 August 2026 — 80,885 subscribers24 August 2026 — 80,837 subscribers25 August 2026 — 80,802 subscribers26 August 2026 — 80,776 subscribers27 August 2026 — 80,752 subscribers28 August 2026 — 80,734 subscribers29 August 2026 — 80,852 subscribers30 August 2026 — 80,885 subscribers31 August 2026 — 81,056 subscribers1 September 2026 — 81,168 subscribers2 September 2026 — 81,165 subscribers4 September 2026 — 82,469 subscribers6 September 2026 — 82,523 subscribers9 September 2026 — 82,519 subscribers11 September 2026 — 82,845 subscribers13 September 2026 — 83,091 subscribers15 September 2026 — 83,208 subscribers17 September 2026 — 83,217 subscribers6 August 202617 September 2026
34 measurements spanning 42 days, net +1,750. 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 80,362–83,589 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
17 Sept 2026, 08:4183,217+9
15 Sept 2026, 11:5983,208+117
13 Sept 2026, 18:3983,091+246
11 Sept 2026, 22:0182,845+326
9 Sept 2026, 10:3882,519-4
6 Sept 2026, 02:5782,523+54
4 Sept 2026, 00:0282,469+1,304
2 Sept 2026, 18:1581,165-3
1 Sept 2026, 15:2681,168+112
31 Aug 2026, 15:0881,056+171
30 Aug 2026, 13:3480,885+33
29 Aug 2026, 12:2580,852+118
28 Aug 2026, 10:0480,734-18
27 Aug 2026, 11:3780,752-24
26 Aug 2026, 14:0480,776-26
25 Aug 2026, 17:0580,802-35
24 Aug 2026, 14:2580,837-48
22 Aug 2026, 22:0280,885-47
21 Aug 2026, 10:3580,932-7
20 Aug 2026, 08:3380,939first reading

Engagement

24 posts held, back to 3 June 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 101 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
194.0%
avg views ÷ 83,217 subscribers
Avg views / post
161,000
10 posts measured
Reaction rate
1.62%
reactions ÷ views · ER floor
Posts in window
10
of 24 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 September 2026
Posts held24 (3 June 2026 – 13 September 2026)
Views total1,614,000
Reactions total26,085
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Sept 2026, 11:47 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

Photos
450
Videos
49
Links
11

Lifetime counters from Telegram’s own channel header, read 24 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
2m 21s
Average length
28s

Measured directly from 5 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

60,315 reactions across 24 posts, in 42 distinct kinds. The most used accounts for 62.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥37,51462.2%
👍6,75411.2%
❤5,4899.10%
🍾3,5705.92%
🥰8941.48%
👏7221.20%
😡6771.12%
😢5020.832%
🤬4740.786%
🏆4480.743%
👎4310.715%
❤‍🔥4220.7%
😱4100.68%
😍3170.526%
⚡2620.434%
🎉2520.418%
😁2200.365%
😭1870.31%
🆒820.136%
💩790.131%
22 further kinds6091.01%

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 24 of the 24 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 60,315 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 3 June 2026 to 13 September 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

13 Sept 2026, 08:28 UTC≈115,000 views2,577 reactionsread 24 September 2026

💥Атака на Таганрог. Город без ПВО. 12.09.2026 была совершена атака на объекты, расположенные в районе г. Таганрог, Ростовская область. В ходе атаки был уничтожен ЗРПК «Панцирь-С1». Стоит отметить, что комплекс за день до атаки вышел из ремонта после предыдущего поражения. Состоянием на 13.09.2026 на территории г. Таганрог больше нет действующих ЗРПК «Панцирь-С1» и ЗРК «С300/400». Также, в ходе атаки был нанесен у…

🔥1,620❤389👍271🍾156😱65🌚20🥰19🏆12

11 Sept 2026, 10:46 UTC≈275,000 views1,960 reactionsread 24 September 2026

💥Удар по вертолету и самолету. В ходе атаки 09.09.2026 на объекты, расположенные в Краснодарском крае, были нанесены удары по авиационной технике. Уничтожен вертолет Ми-8АМТШ (бортовой номер – 84). Удар нанесен 1 БПЛА в районе вертолетной площадки Чембурка, г. Анапа. Вертолет принадлежал подразделению 318 отдельного смешанного авиационного полка. Существенно поврежден самолет Су-30 (бортовой номер – 41). Удар нане…

🔥1,230❤292👍274😡63👎29🥰22🏆21🤡13

10 Sept 2026, 14:24 UTC≈70,400 views1,805 reactionsread 24 September 2026
Photo

💥Удары по Новороссийску. На фото – последствия удара по казарме роты БПЛА, расположенной близ г. Новороссийск, Краснодарский край. Информация относительно пострадавших отсутствует. 09.09.2026. @dosye_shpiona

🔥1,180👍291❤106⚡73👎47😢41👏25🥰14

9 Sept 2026, 10:15 UTC≈105,000 views2,435 reactionsread 24 September 2026
Photo

💥Охота за Панцирями продолжается. На фото – поражение двух ЗРПК «Панцирь-С1». Фото 1-2 – уничтоженный «Панцирь» в районе г. Санкт-Петербург. Двое военнослужащих (начальник расчета и оператор) погибли. Фото 3-4 – уничтоженный «Панцирь» в районе н.п. Чалтырь, Ростовская область. У начальника расчета травматическая ампутация правой ноги, оператор погиб. Точную дату событий установить не удалось. Лето 2026. @dosye_s…

🔥1,590❤391👍269👏50💊39🥰28😍21🏆16

8 Sept 2026, 09:44 UTC≈124,000 views3,744 reactionsread 24 September 2026

❗️Гибель спецназовцев при схождении лавины. 06.09.2026 в результате схождения лавины погибла группа альпинистов, среди которых были военнослужащие Центра специального назначения «Витязь» войск национальной гвардии РФ. Катастрофа произошла в Безенгийском ущелье, Кабардино-Балкария. По предварительной информации, погибло 13 военнослужащих. Еще один находится в состоянии комы. @dosye_shpiona

🔥1,690🍾1,260👍277😢159😁150🎉71❤68😱41

7 Sept 2026, 14:40 UTC≈73,600 views1,794 reactionsread 24 September 2026
Video

💥Удары по логистике. На видео – результаты ударов по двум топливозаправщикам ВС РФ. 26.08.2026. н.п. Самсоново, Донецкая область. @dosye_shpiona

🔥1,160❤229👍178🤬78🍾49👏30🥰23💩17

3 Sept 2026, 10:10 UTC≈338,000 views5,100 reactionsread 24 September 2026
Photo

❗️Покушение на убийство генерала. Сегодня, 03.09.2026, около 07:00 было совершено покушение на жизнь командира 22 тяжелой бомбардировочной авиационной дивизии дальней авиации ВКС РФ генерал-майора Варпаховича Николая Николаевича. На данный момент известно, что нападавший подкараулил генерал-майора у частного домовладения по адресу ул. Энтузиастов, д.2, н.п. Пробуждение, Саратовская область. Было совершено два выст…

🔥3,250❤617👏466👍308🍾250😱100🏆39🆒27

31 Aug 2026, 09:24 UTC≈229,000 views2,613 reactionsread 24 September 2026
Photo

💥Охота на «Панцири». На фото – подтверждение уничтожения двух ЗРК «Панцирь-С1». Первое фото – уничтоженный «Панцирь-С1» 29.08.2026 в районе г. Керчь, Крым. Второе фото – уничтоженный «Панцирь-С1» 30.08.2026 в районе аэродрома Ейск, Краснодарский край. @dosye_shpiona

🔥1,690😍296👍202❤150😡123🎉51💩37😱24

29 Aug 2026, 08:41 UTC≈168,000 views2,364 reactionsread 24 September 2026

💥Удар по Панцирю прикрытия Искандера. 27.08.2026 был уничтожен ЗРПК «Панцирь-С1» из состава 210 зрп (в/ч 51890), в районе н.п. Клетня, Брянская область. Удар нанесен 1 БПЛА. Комплекс осуществлял прикрытие ОТРК «Искандер». В результате удара погиб лейтенант Арсененко Аркадий, получил ранения сержант Курмашетов Руслан. @dosye_shpiona

🔥1,320🍾528👍215❤84😡78😢66🆒19🥰16

27 Aug 2026, 09:43 UTC≈116,000 views1,693 reactionsread 24 September 2026

💥Атаки БПЛА. 23.08.2026 был нанесен ряд ударов по Адлерскому району, г. Сочи. Использовано 15 БПЛА. По имеющейся информации, все были сбиты средствами ПВО. Однако, один из сбитых БПЛА упал на ЗРПК «Панцирь-С1». Трое военнослужащих 1721 зрп (в/ч 11754, Сочи) получили осколочные ранения. 24.08.2026 была совершена атака по территории 91 центральной базы хранения автомобильной техники (в/ч 48670, Каменск-Шахтинский).…

🔥984👍312❤144🍾89😡78💩25⚡24🤔13

19 Aug 2026, 09:52 UTC≈126,000 views1,759 reactionsread 24 September 2026

💥Удар по Саваслейке. 15.08.2026 была совершена атака по территории 44 отдельного авиационного полка особого назначения (в/ч 83122, Саваслейка). Атака совершена с использованием 22 БПЛА. Вследствие удара: • повреждено 5 из 22 резервуаров хранения топлива (50 т каждый); • повреждено техническое помещение; • поврежден самолетный ангар № 18; Пострадавших среди военнослужащих нет. @dosye_shpiona

🔥1,060🍾238👍165❤130🤬73🤡25😢25👀17

18 Aug 2026, 07:39 UTC≈110,000 views1,773 reactionsread 24 September 2026
Video

💥Удар по складу боеприпасов. 15.08.2026 был нанесен удар по складу боеприпасов, расположенному в н.п. Ялынское, Донецкая область. Атака совершена с использованием 2-х БПЛА. Вследствие удара возник пожар, который сопровождался детонацией содержимого склада. @dosye_shpiona

🔥1,110👍309❤127🍾105😡55😱15🏆13👏13

Showing the 12 most recent of 24 posts we hold for @dosye_shpiona. 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 33 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

2 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Russian corvette Boikiy (en.wikipedia.org)
“…the ship’s superstructure.{{Cite web |title=Досье Шпиона |url=https://t.me/dosye_shpiona/773 |access-date=2026-06-04 |website=Telegram}}{{cite…”
read 13 September 2026
Перелік українських атак по прикордонних регіонах РФ (2026) (uk.wikipedia.org)
“…полковника Петрова Ігоря Ігоровича{{Cite web |url=https://t.me/dosye_shpiona/720 |title=Досье Шпиона |website=Telegram |access-date=2026-02-10}}…”
read 13 September 2026

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Досье Шпиона” (@dosye_shpiona), 83,217 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/dosye_shpiona.

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.