Channel
Метод Сташевич
@dr_stashevich
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,900subscribers
-65 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001617864836 |
|---|---|
| Type | Channel |
| Username | @dr_stashevich |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/dr_stashevich |
Topic
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 00:58 | 4,900 | -4 |
| 12 Sept 2026, 13:41 | 4,904 | -12 |
| 8 Sept 2026, 14:21 | 4,916 | -6 |
| 3 Sept 2026, 08:35 | 4,922 | -2 |
| 1 Sept 2026, 22:20 | 4,924 | no change |
| 31 Aug 2026, 00:24 | 4,924 | -7 |
| 28 Aug 2026, 03:04 | 4,931 | -4 |
| 24 Aug 2026, 20:05 | 4,935 | +3 |
| 20 Aug 2026, 20:33 | 4,932 | -7 |
| 17 Aug 2026, 13:59 | 4,939 | -6 |
| 14 Aug 2026, 03:45 | 4,945 | -9 |
| 11 Aug 2026, 06:02 | 4,954 | -9 |
| 7 Aug 2026, 19:23 | 4,963 | -2 |
| 7 Aug 2026, 13:41 | 4,965 | 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.
@polyakovacash · 33,482
Telegram ranks this channel #7 of 56 here — alongside 55 others — read 22 September 2026
@cosmetology_content · 23,995
Telegram ranks this channel #18 of 57 here — alongside 56 others — read 22 September 2026
@lubaeva · 28,753
Telegram ranks this channel #26 of 65 here — alongside 64 others — read 22 September 2026
@aynastudy · 24,378
Telegram ranks this channel #35 of 55 here — alongside 54 others — read 22 September 2026
@kosmetologia_ru · 158,870
Telegram ranks this channel #42 of 52 here — alongside 51 others — read 22 September 2026
@health_club_drPomoinetskaya · 22,163
Telegram ranks this channel #76 of 84 here — alongside 83 others — read 21 September 2026
This channel appears in 6 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Метод Сташевич” (@dr_stashevich), 4,900 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/dr_stashevich.
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.