Channel
Shadowing with Salaydinov
@shadowingwithsalaydinov
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,429subscribers
+340 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001984722269 |
|---|---|
| Type | Channel |
| Username | @shadowingwithsalaydinov |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/shadowingwithsalaydinov |
Topic
Education — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 02:54 | 2,429 | +8 |
| 1 Nov 2026, 09:16 | 2,421 | -6 |
| 29 Oct 2026, 19:09 | 2,427 | +7 |
| 27 Oct 2026, 03:58 | 2,420 | +7 |
| 24 Oct 2026, 06:55 | 2,413 | +12 |
| 21 Oct 2026, 13:05 | 2,401 | -1 |
| 18 Oct 2026, 12:46 | 2,402 | +7 |
| 15 Oct 2026, 16:41 | 2,395 | +50 |
| 12 Oct 2026, 16:26 | 2,345 | +22 |
| 5 Oct 2026, 17:00 | 2,323 | +11 |
| 28 Sept 2026, 06:59 | 2,312 | +86 |
| 18 Sept 2026, 14:45 | 2,226 | no change |
| 16 Sept 2026, 03:41 | 2,226 | +149 |
| 12 Sept 2026, 07:21 | 2,077 | +26 |
| 7 Sept 2026, 20:20 | 2,051 | -9 |
| 2 Sept 2026, 14:18 | 2,060 | -5 |
| 30 Aug 2026, 12:54 | 2,065 | +5 |
| 27 Aug 2026, 17:34 | 2,060 | -5 |
| 24 Aug 2026, 11:17 | 2,065 | -12 |
| 20 Aug 2026, 11:34 | 2,077 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.
@OfficialCambridgeGuidetoIELTS · 19,386
Telegram ranks this channel #3 of 81 here — alongside 80 others — read 4 October 2026
@EnglishPodcastsOfficial · 27,177
Telegram ranks this channel #27 of 85 here — alongside 84 others — read 10 September 2026
@stjegypt · 370,345
Telegram ranks this channel #33 of 64 here — alongside 63 others — read 16 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Shadowing with Salaydinov” (@shadowingwithsalaydinov), 2,429 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/shadowingwithsalaydinov.
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.