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

Channel

Досье Шпиона

@dosye_shpiona

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

83,428subscribers

+1,961 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
Created5 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live17 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 17 November 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 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 3 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@dosye_shpiona/811 · this entry29 Oct 2026, 14:53 UTC@ukrainian_militant/4181929 Oct 2026, 15:00 UTC1.008 minutes
@dosye_shpiona/813 · this entry4 Nov 2026, 16:32 UTC@ukrainian_militant/418914 Nov 2026, 16:40 UTC1.008 minutes
@dosye_shpiona/813 · this entry4 Nov 2026, 16:32 UTC@captain_parker/913384 Nov 2026, 16:34 UTC1.002 minutes
@dosye_shpiona/820 · this entry15 Nov 2026, 09:36 UTC@captain_parker/9273015 Nov 2026, 09:37 UTC1.0072 seconds
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
@ukrainian_militant8 (8/8 hand-verifiable sample passed)1.008 minutesthis entry (8–0)
@captain_parker5 (5/5 hand-verifiable sample passed)1.0072 secondsthis entry (5–0)
@britishmi613 (8/8 hand-verifiable sample passed)1.005 minutesthis entry (13–0)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 34 comparable posts for this entry, running 3 June 2026 to 15 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @dosye_shpiona — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 16 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

80,73483,42882,0816 August 202617 November 2026
67 measurements spanning 103 days, net +1,961. 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,330–83,832 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
17 Nov 2026, 07:4183,428+93
14 Nov 2026, 00:0083,335+240
11 Nov 2026, 08:4783,095+68
9 Nov 2026, 15:5183,027+18
8 Nov 2026, 09:5783,009-26
7 Nov 2026, 05:3983,035-16
6 Nov 2026, 06:0783,051+18
5 Nov 2026, 02:0983,033-7
3 Nov 2026, 23:0683,040-27
2 Nov 2026, 20:0883,067-13
1 Nov 2026, 19:1083,080-18
31 Oct 2026, 19:1783,098+14
30 Oct 2026, 15:3783,084+825
29 Oct 2026, 14:4682,259-40
28 Oct 2026, 14:4182,299-12
27 Oct 2026, 12:4582,311-27
26 Oct 2026, 11:4782,338-22
25 Oct 2026, 08:2682,360-22
24 Oct 2026, 11:5082,382-17
23 Oct 2026, 13:5682,399first reading

Engagement

34 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 208 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
154.4%
avg views ÷ 83,428 subscribers
Avg views / post
129,000
8 posts measured
Reaction rate
1.70%
reactions ÷ views · ER floor
Posts in window
8
of 34 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 15 November 2026
Posts held34 (3 June 2026 – 15 November 2026)
Views total1,030,500
Reactions total17,489
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 07:34 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
4m 43s
Average length
31s

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

83,719 reactions across 34 posts, in 43 distinct kinds. The most used accounts for 60.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥50,51160.3%
❤8,53910.2%
👍8,2939.91%
🍾6,0187.19%
👏1,1001.31%
🥰1,0181.22%
🤬8681.04%
😡8270.988%
😢6240.745%
🏆6150.735%
🤝6140.733%
😱5450.651%
🎉5130.613%
👎5010.598%
❤‍🔥4900.585%
😁3780.452%
😍3230.386%
⚡2890.345%
💩2320.277%
😭2150.257%
23 further kinds1,2061.44%

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

Measured over the 34 most recent posts we hold, published 3 June 2026 to 15 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: 0 of 8 posts held from the last 30 days (0%) 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).

15 Nov 2026, 09:36 UTC≈71,900 views1,705 reactionsread 17 November 2026

💥Удар по аэродрому. 13.11.2026 была совершена атака на военный аэродром «Липецк-2», г. Липецк. Аэродром используется 968 исследовательско-инструкторским смешанным авиационным полком (в/ч 81819). • Атакован командно-диспетчерский пункт аэродрома, незначительные повреждения оборудования. • Поврежден Су-34. Осколками посекло корпус. • Атакован ангар для ремонта техники. • Ранения получили два офицера из состава техни…

🔥1,050❤226🍾171👍117😡76🏆15🥰15🤷13

13 Nov 2026, 08:57 UTC≈104,000 views2,155 reactionsread 17 November 2026
Photo

💥Атака на позиции радиолокационной разведки. 11.11.2026 была совершена атака по позициям части РЛР, расположенной в Ленинградской области. Поражены: • РЛС «Небо-СВУ»; • Универсальная передвижная вышка 40В6; • Трассовый радиолокационный комплекс «Сопка-2». @dosye_shpiona

🔥1,440👍364❤173👎47🤩30🏆23🥰22😱20

10 Nov 2026, 12:06 UTC≈87,100 views2,463 reactionsread 17 November 2026

💥Атака на НПЗ в Киришах. Вчера, 09.11.2026, была совершена массированная атака БПЛА по нефтеперерабатывающему предприятию «Киришинефтеоргсинтез», н.п. Кириши, Ленинградская область. Вследствие совершенных ударов были нанесены существенные повреждения ключевым узлам предприятия, а именно: • Установка ЭЛОУ-АВТ-2; • Установка АТ-1; • Установка АТ-6; • Комплекс переработки мазута; • Установка Парекс-2; • Два блока обор…

🔥1,540❤328🎉211👍148🤬104🍾59💩22🏆16

9 Nov 2026, 16:51 UTC≈102,000 views1,643 reactionsread 17 November 2026
Video

💥Удары по логистике. Продолжаются непрерывные удары по логистическому транспорту ВС РФ на территории Донецкой области. На видео: Эпизод №1 – 27.10.2026 удар по автомобилю «Урал» в районе н.п. Богдановка; Эпизод №2 – 03.11.2026 удар по грузовому автомобилю в районе н.п. Василевка. @dosye_shpiona

🔥986🍾296❤127👍86😡71😱18🥰16👎15

4 Nov 2026, 16:32 UTC≈115,000 views2,318 reactionsread 17 November 2026
Photo

❗️Убил двоих военнослужащих. На фото – Москвичев Руслан Владимирович, капитан, командир 5 мотострелковой роты 3 мсб 64 отдельной мотострелковой бригады (в/ч 51460, Хабаровский край). 03.11.2026, при неустановленных обстоятельствах, Москвичев совершил убийство двоих военнослужащих 218 танкового полка (в/ч 82588, Приморский край). Погибшие военнослужащие обнаружены с многочисленными огнестрельными ранениями, в том чи…

❤756🤝595🔥425🍾270🤣76🤷‍♂61💩55😁42

1 Nov 2026, 12:40 UTC≈92,500 views1,928 reactionsread 17 November 2026
Video

💥Удары по логистике. Продолжаются систематические удары по логистике ВС РФ на территории Донецкой области. На видео – четыре эпизода нанесения ударов по транспорту. Эпизод № 1 – уничтожен топливозаправщик бригады материально-технического обеспечения ВС РФ. Район н.п. Покровск; Эпизод № 2 – уничтожен топливозаправщик бригады материально-технического обеспечения ВС РФ. Район н.п. Мангуш; Эпизод № 3 – уничтожен гру…

🔥1,190❤305👍176🤬100🏆42👏35🥰23❤‍🔥19

29 Oct 2026, 14:53 UTC≈228,000 views3,139 reactionsread 17 November 2026

💥Уничтожение самолетов. 29.10.2026 был нанесен удар по военному аэродрому «Мариновка», расположенному в н.п. Октябрьский, Волгоградская область. Аэродром используется 11-м смешанным авиационным полком. Вследствие удара уничтожено 2 Су-34. Двое военнослужащих полка погибло, еще двое получили ранения. @dosye_shpiona

🔥1,920❤451👍301🍾227🤬119👏43😭28🏆15

21 Oct 2026, 16:32 UTC≈230,000 views2,138 reactionsread 17 November 2026
Video

💥Подрыв на мине. На видео - последствия подрыва на мине автомобиля военнослужащих 60 отдельной мотострелковой бригады. Вследствие подрыва один военнослужащий погиб, еще один ранен. Событие произошло в районе н.п. Приютное, Запорожская область. @dosye_shpiona

🔥1,200🍾451❤186😢115🤬70🙏28🫡24🥰22

7 Oct 2026, 11:04 UTC≈136,000 views1,701 reactionsread 17 November 2026
Video

💥Удары по логистике. Продолжаются систематические удары по логистическому транспорту на территории Донецкой области. Видео № 1 – 29.09.2026, удар по а/м «КамАЗ» в районе н.п. Докучаевск, Донецкая область; Видео № 2 – 30.09.2026, удар по грузовому автомобилю в районе н.п. Новотроицкое, Донецкая область; Видео № 3 – 02.10.2026, удар по автомобильной цистерне в районе н.п. Волноваха, Донецкая область. @dosye_shpion

🔥1,080👏235❤143👍58💩57🎉48😱26😈21

2 Oct 2026, 09:36 UTC≈208,000 views3,245 reactionsread 17 November 2026

💥Сбили «Ми-8». По предварительной информации, 01.10.2026, во время отражения массированной атаки БПЛА, дружеским огнем был сбит вертолет «Ми-8». Экипаж «Су-35» сбил «Ми-8» ошибочно идентифицировав его как БПЛА. Трое членов экипажа «Ми-8» погибли. Событие произошло в Воронежской области. @dosye_shpiona

🔥1,600🍾915❤229👍163😁105🤣91👏55🤷‍♂47

13 Sept 2026, 08:28 UTC≈238,000 views2,834 reactionsread 17 November 2026

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

🔥1,780❤428👍296🍾169😱75🌚21🥰20🏆16

11 Sept 2026, 10:46 UTC≈351,000 views2,105 reactionsread 17 November 2026

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

🔥1,320❤312👍294😡66👎33🏆24🥰22🤡16

Showing the 12 most recent of 34 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 45 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 1 November 2026
Перелік українських атак по прикордонних регіонах РФ (2026) (uk.wikipedia.org)
“…полковника Петрова Ігоря Ігоровича{{Cite web |url=https://t.me/dosye_shpiona/720 |title=Досье Шпиона |website=Telegram |access-date=2026-02-10}}…”
read 1 November 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 November 2026 — this entry's latest reading, not the date you are reading this.

“Досье Шпиона” (@dosye_shpiona), 83,428 subscribers as measured 17 November 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.