Telegram RegisterThe public register of Telegram
Telegram profile photo for SMSly

Bot

SMSly

@smslybot

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

26,516monthly users

-4,532 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8114654966
TypeBot
Username@smslybot
First recorded13 August 2026
Last confirmed live15 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/smslybot

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

25,23831,52828,38326,5167 August 202615 November 2026
65 measurements spanning 99 days, net -4,532. 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 24,295–32,472 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 65
Measured (UTC)Monthly usersChange
15 Nov 2026, 00:2026,516+232
11 Nov 2026, 21:5926,284-112
10 Nov 2026, 04:1126,396+32
8 Nov 2026, 21:0026,364-126
7 Nov 2026, 14:0026,490+32
6 Nov 2026, 17:1726,458+28
5 Nov 2026, 14:4426,430+418
4 Nov 2026, 13:3826,012-627
3 Nov 2026, 12:4826,639-67
1 Nov 2026, 17:3426,706+99
31 Oct 2026, 16:5526,607-5
30 Oct 2026, 16:0526,612+538
29 Oct 2026, 13:0126,074-470
28 Oct 2026, 14:4126,544-172
27 Oct 2026, 12:4726,716-344
26 Oct 2026, 10:0227,060+130
25 Oct 2026, 07:1526,930+49
24 Oct 2026, 04:0626,881-19
23 Oct 2026, 02:3126,900+427
21 Oct 2026, 23:1626,473first 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 11 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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“SMSly” (@smslybot), 26,516 monthly users as measured 15 November 2026. Telegram Register, tgregister.com/channel/smslybot.

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.