Channel
Доктор Шипицын
@shipicyn
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,169subscribers
-112 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 | -1001765606254 |
|---|---|
| Type | Channel |
| Username | @shipicyn |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/shipicyn |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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, 23:21 | 3,169 | -4 |
| 1 Nov 2026, 18:26 | 3,173 | -11 |
| 29 Oct 2026, 16:50 | 3,184 | -5 |
| 26 Oct 2026, 20:51 | 3,189 | -1 |
| 24 Oct 2026, 01:47 | 3,190 | -5 |
| 20 Oct 2026, 21:39 | 3,195 | -5 |
| 17 Oct 2026, 17:39 | 3,200 | -3 |
| 14 Oct 2026, 12:56 | 3,203 | -27 |
| 11 Oct 2026, 05:02 | 3,230 | -4 |
| 5 Oct 2026, 08:15 | 3,234 | -6 |
| 27 Sept 2026, 00:36 | 3,240 | -8 |
| 15 Sept 2026, 07:00 | 3,248 | -2 |
| 11 Sept 2026, 23:41 | 3,250 | -7 |
| 9 Sept 2026, 23:04 | 3,257 | no change |
| 7 Sept 2026, 07:56 | 3,257 | -3 |
| 2 Sept 2026, 21:25 | 3,260 | -2 |
| 30 Aug 2026, 09:35 | 3,262 | -1 |
| 27 Aug 2026, 14:25 | 3,263 | -2 |
| 24 Aug 2026, 06:47 | 3,265 | -6 |
| 20 Aug 2026, 17:54 | 3,271 | 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.
@drdubuk · 22,721
Telegram ranks this channel #16 of 68 here — alongside 67 others — read 20 September 2026
@drartempark · 45,207
Telegram ranks this channel #43 of 72 here — alongside 71 others — read 27 August 2026
@epifanovnews · 49,180
Telegram ranks this channel #56 of 93 here — alongside 92 others — read 26 August 2026
@maximpolovinko · 22,124
Telegram ranks this channel #58 of 84 here — alongside 83 others — read 22 September 2026
This channel appears in 4 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.
“Доктор Шипицын” (@shipicyn), 3,169 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/shipicyn.
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.