Channel
Surgery (37A)
@Surgery37A
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,056subscribers
+50 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001868035245 |
|---|---|
| Type | Channel |
| Username | @Surgery37A |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 2 times, most recently 7 November 2026 |
| On Telegram | t.me/Surgery37A |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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, 19:11 | 2,056 | -3 |
| 1 Nov 2026, 16:08 | 2,059 | +3 |
| 29 Oct 2026, 12:37 | 2,056 | +10 |
| 23 Oct 2026, 14:06 | 2,046 | +2 |
| 17 Oct 2026, 15:06 | 2,044 | +9 |
| 14 Oct 2026, 13:06 | 2,035 | +1 |
| 11 Oct 2026, 07:14 | 2,034 | +9 |
| 5 Oct 2026, 00:16 | 2,025 | -1 |
| 25 Sept 2026, 20:15 | 2,026 | +13 |
| 20 Sept 2026, 23:16 | 2,013 | no change |
| 17 Sept 2026, 01:58 | 2,013 | +5 |
| 12 Sept 2026, 20:21 | 2,008 | +4 |
| 3 Sept 2026, 09:36 | 2,004 | -2 |
| 30 Aug 2026, 23:30 | 2,006 | 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.
@Systemic7Medicine · 38,587
Telegram ranks this channel #5 of 87 here — alongside 86 others — read 31 August 2026
@pediatricaljoky · 22,444
Telegram ranks this channel #8 of 93 here — alongside 92 others — read 22 September 2026
@Surgery_Data · 26,261
Telegram ranks this channel #10 of 84 here — alongside 83 others — read 14 September 2026
@pedia8 · 23,572
Telegram ranks this channel #13 of 96 here — alongside 95 others — read 19 September 2026
@Clinical_Notes · 40,288
Telegram ranks this channel #23 of 79 here — alongside 78 others — read 30 August 2026
@Engaz11 · 20,554
Telegram ranks this channel #64 of 92 here — alongside 91 others — read 29 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Surgery (37A)” (@Surgery37A), 2,056 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/Surgery37A.
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.