Channel
Surgery 35
@surgery35
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,870subscribers
+5 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001538727360 |
|---|---|
| Type | Channel |
| Username | @surgery35 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/surgery35 |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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 |
|---|---|---|
| 5 Nov 2026, 02:50 | 1,870 | +2 |
| 1 Nov 2026, 23:07 | 1,868 | -1 |
| 29 Oct 2026, 21:10 | 1,869 | -1 |
| 21 Oct 2026, 00:06 | 1,870 | +1 |
| 17 Oct 2026, 21:11 | 1,869 | +3 |
| 15 Oct 2026, 07:11 | 1,866 | -3 |
| 12 Oct 2026, 01:18 | 1,869 | +5 |
| 27 Sept 2026, 18:37 | 1,864 | -1 |
| 22 Sept 2026, 15:47 | 1,865 | no change |
| 18 Sept 2026, 09:38 | 1,865 | +1 |
| 13 Sept 2026, 03:37 | 1,864 | -1 |
| 11 Sept 2026, 15:47 | 1,865 | 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.
@Surgery_Data · 26,204
Telegram ranks this channel #3 of 84 here — alongside 83 others — read 14 September 2026
@Engaz11 · 20,493
Telegram ranks this channel #11 of 92 here — alongside 91 others — read 29 September 2026
@medicine99 · 26,700
Telegram ranks this channel #11 of 86 here — alongside 85 others — read 11 September 2026
@sdgtbookstore · 35,234
Telegram ranks this channel #23 of 74 here — alongside 73 others — read 24 September 2026
@pedia8 · 23,519
Telegram ranks this channel #26 of 96 here — alongside 95 others — read 19 September 2026
@Emergency_intensivecare · 22,692
Telegram ranks this channel #36 of 84 here — alongside 83 others — read 20 September 2026
@pediatricaljoky · 22,412
Telegram ranks this channel #77 of 93 here — alongside 92 others — read 22 September 2026
This channel appears in 7 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Surgery 35” (@surgery35), 1,870 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/surgery35.
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.