Channel
AnestesiandoEstoy
@AnestesiandoEstoy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,101subscribers
+125 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001238270419 |
|---|---|
| Type | Channel |
| Username | @AnestesiandoEstoy |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/AnestesiandoEstoy |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 7 Nov 2026, 14:47 | 3,101 | +4 |
| 4 Nov 2026, 07:26 | 3,097 | +8 |
| 1 Nov 2026, 09:40 | 3,089 | +2 |
| 29 Oct 2026, 17:06 | 3,087 | +3 |
| 26 Oct 2026, 11:40 | 3,084 | -1 |
| 23 Oct 2026, 11:34 | 3,085 | +7 |
| 20 Oct 2026, 22:00 | 3,078 | +2 |
| 17 Oct 2026, 20:08 | 3,076 | +3 |
| 14 Oct 2026, 23:48 | 3,073 | +3 |
| 11 Oct 2026, 13:42 | 3,070 | +7 |
| 5 Oct 2026, 02:18 | 3,063 | +17 |
| 26 Sept 2026, 11:18 | 3,046 | +15 |
| 17 Sept 2026, 06:38 | 3,031 | +10 |
| 13 Sept 2026, 02:16 | 3,021 | +9 |
| 11 Sept 2026, 13:55 | 3,012 | no change |
| 9 Sept 2026, 00:18 | 3,012 | +3 |
| 4 Sept 2026, 01:15 | 3,009 | +12 |
| 31 Aug 2026, 17:15 | 2,997 | +7 |
| 28 Aug 2026, 11:52 | 2,990 | +12 |
| 25 Aug 2026, 10:34 | 2,978 | 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.
@librosdeenfermeriaysalud · 41,746
Telegram ranks this channel #28 of 51 here — alongside 50 others — read 1 October 2026
@articulosmedicosdelMedtwitter · 51,624
Telegram ranks this channel #29 of 77 here — alongside 76 others — read 24 August 2026
@intensivistapediatrico · 23,214
Telegram ranks this channel #45 of 73 here — alongside 72 others — read 20 September 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“AnestesiandoEstoy” (@AnestesiandoEstoy), 3,101 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/AnestesiandoEstoy.
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.