Channel
ABED sir
@ABED_sir
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,630subscribers
-243 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001662418785 |
|---|---|
| Type | Channel |
| Username | @ABED_sir |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/ABED_sir |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 1 Nov 2026, 01:08 | 4,630 | -9 |
| 29 Oct 2026, 06:18 | 4,639 | -13 |
| 25 Oct 2026, 20:36 | 4,652 | -4 |
| 23 Oct 2026, 02:46 | 4,656 | -11 |
| 20 Oct 2026, 06:00 | 4,667 | -7 |
| 17 Oct 2026, 14:18 | 4,674 | -5 |
| 14 Oct 2026, 21:45 | 4,679 | -10 |
| 11 Oct 2026, 13:38 | 4,689 | -22 |
| 4 Oct 2026, 22:40 | 4,711 | -27 |
| 25 Sept 2026, 12:01 | 4,738 | -38 |
| 15 Sept 2026, 13:58 | 4,776 | -11 |
| 12 Sept 2026, 04:40 | 4,787 | -19 |
| 8 Sept 2026, 00:20 | 4,806 | -9 |
| 3 Sept 2026, 01:02 | 4,815 | -18 |
| 1 Sept 2026, 23:26 | 4,833 | no change |
| 30 Aug 2026, 12:44 | 4,833 | -8 |
| 27 Aug 2026, 19:18 | 4,841 | -15 |
| 25 Aug 2026, 03:58 | 4,856 | -9 |
| 22 Aug 2026, 05:48 | 4,865 | -8 |
| 21 Aug 2026, 03:30 | 4,873 | 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.
@Shivani_Pallela · 63,718
Telegram ranks this channel #1 of 46 here — alongside 45 others — read 21 August 2026
@DANDUVENKATRAMULU · 25,485
Telegram ranks this channel #3 of 62 here — alongside 61 others — read 12 September 2026
@Osmania · 28,391
Telegram ranks this channel #8 of 64 here — alongside 63 others — read 9 September 2026
@examupdt · 24,960
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 13 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“ABED sir” (@ABED_sir), 4,630 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/ABED_sir.
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.