Channel
Vet updates
@vetdrs
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,511subscribers
+101 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 | -1001250621091 |
|---|---|
| Type | Channel |
| Username | @vetdrs |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/vetdrs |
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 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 |
|---|---|---|
| 8 Nov 2026, 21:11 | 3,511 | +5 |
| 5 Nov 2026, 17:06 | 3,506 | +4 |
| 2 Nov 2026, 13:56 | 3,502 | +3 |
| 30 Oct 2026, 18:27 | 3,499 | +6 |
| 27 Oct 2026, 15:59 | 3,493 | +1 |
| 24 Oct 2026, 06:07 | 3,492 | +2 |
| 21 Oct 2026, 07:16 | 3,490 | +7 |
| 17 Oct 2026, 22:56 | 3,483 | +2 |
| 15 Oct 2026, 02:55 | 3,481 | +1 |
| 11 Oct 2026, 17:36 | 3,480 | +15 |
| 5 Oct 2026, 15:40 | 3,465 | +5 |
| 27 Sept 2026, 13:21 | 3,460 | +12 |
| 15 Sept 2026, 19:54 | 3,448 | +11 |
| 11 Sept 2026, 17:41 | 3,437 | +3 |
| 8 Sept 2026, 21:04 | 3,434 | no change |
| 7 Sept 2026, 09:20 | 3,434 | +4 |
| 2 Sept 2026, 12:37 | 3,430 | +4 |
| 27 Aug 2026, 01:34 | 3,426 | +5 |
| 23 Aug 2026, 23:38 | 3,421 | +1 |
| 19 Aug 2026, 23:02 | 3,420 | 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.
@vets_hub · 22,563
Telegram ranks this channel #6 of 82 here — alongside 81 others — read 20 September 2026
@UGC_NET_JRF_NTA_CSIR · 130,874
Telegram ranks this channel #53 of 71 here — alongside 70 others — read 13 August 2026
@DrAtefElhendi · 26,720
Telegram ranks this channel #73 of 83 here — alongside 82 others — read 12 September 2026
@vet100 · 26,832
Telegram ranks this channel #77 of 83 here — alongside 82 others — read 12 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Vet updates” (@vetdrs), 3,511 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/vetdrs.
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.