Telegram RegisterThe public register of Telegram
Telegram profile photo for SANAYDI_BOT 👥

Bot

SANAYDI_BOT 👥

@Sanaydi_Bot

On this record: Topic · Growth · Engagement · Citations · Cite this entry

74,981monthly users

-10,573 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID5333634932
TypeBot
Username@Sanaydi_Bot
First recorded10 August 2026
Last confirmed live19 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/Sanaydi_Bot

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 9 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

69,17893,24581,211.56 August 2026 — 85,554 monthly users7 August 2026 — 86,535 monthly users8 August 2026 — 87,849 monthly users10 August 2026 — 87,849 monthly users11 August 2026 — 88,084 monthly users14 August 2026 — 88,751 monthly users15 August 2026 — 90,487 monthly users16 August 2026 — 91,444 monthly users17 August 2026 — 92,098 monthly users18 August 2026 — 92,399 monthly users21 August 2026 — 92,733 monthly users23 August 2026 — 90,376 monthly users24 August 2026 — 93,245 monthly users26 August 2026 — 92,585 monthly users28 August 2026 — 91,812 monthly users30 August 2026 — 90,379 monthly users31 August 2026 — 89,574 monthly users2 September 2026 — 87,758 monthly users4 September 2026 — 86,839 monthly users6 September 2026 — 86,064 monthly users10 September 2026 — 82,996 monthly users12 September 2026 — 81,944 monthly users13 September 2026 — 82,100 monthly users15 September 2026 — 81,468 monthly users17 September 2026 — 78,454 monthly users27 September 2026 — 71,815 monthly users4 October 2026 — 69,800 monthly users9 October 2026 — 70,349 monthly users13 October 2026 — 69,325 monthly users14 October 2026 — 69,678 monthly users16 October 2026 — 69,504 monthly users17 October 2026 — 69,581 monthly users18 October 2026 — 69,212 monthly users19 October 2026 — 69,191 monthly users20 October 2026 — 69,439 monthly users22 October 2026 — 69,407 monthly users23 October 2026 — 69,291 monthly users24 October 2026 — 69,563 monthly users25 October 2026 — 69,915 monthly users28 October 2026 — 70,324 monthly users29 October 2026 — 70,714 monthly users1 November 2026 — 70,427 monthly users3 November 2026 — 69,993 monthly users4 November 2026 — 69,458 monthly users5 November 2026 — 69,178 monthly users7 November 2026 — 69,924 monthly users8 November 2026 — 70,298 monthly users12 November 2026 — 72,447 monthly users16 November 2026 — 73,588 monthly users19 November 2026 — 74,981 monthly users74,9816 August 202619 November 2026
50 measurements spanning 105 days, net -10,573. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 65,568–96,855 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
19 Nov 2026, 02:2174,981+1,393
16 Nov 2026, 01:2873,588+1,141
12 Nov 2026, 12:0172,447+2,149
8 Nov 2026, 18:4670,298+374
7 Nov 2026, 10:4569,924+746
5 Nov 2026, 12:2669,178-280
4 Nov 2026, 11:2669,458-535
3 Nov 2026, 12:2169,993-434
1 Nov 2026, 16:3670,427-287
29 Oct 2026, 13:1770,714+390
28 Oct 2026, 14:1070,324+409
25 Oct 2026, 06:5469,915+352
24 Oct 2026, 08:0069,563+272
23 Oct 2026, 05:3669,291-116
22 Oct 2026, 04:3669,407-32
20 Oct 2026, 20:4869,439+248
19 Oct 2026, 18:1969,191-21
18 Oct 2026, 19:0969,212-369
17 Oct 2026, 18:5169,581+77
16 Oct 2026, 15:0469,504first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 19 November 2026 — this entry's latest reading, not the date you are reading this.

“SANAYDI_BOT 👥” (@Sanaydi_Bot), 74,981 monthly users as measured 19 November 2026. Telegram Register, tgregister.com/channel/Sanaydi_Bot.

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.