Telegram RegisterThe public register of Telegram
Telegram profile photo for SMS |M| 5 c:

Bot

SMS |M| 5 c:

@OnlineSmsM5_bot

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

26,198monthly users

+4,738 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 ID8642010759
TypeBot
Username@OnlineSmsM5_bot
First recorded15 August 2026
Last confirmed live5 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/OnlineSmsM5_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 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

18,10226,19822,1507 August 2026 — 21,460 monthly users8 August 2026 — 21,100 monthly users9 August 2026 — 21,389 monthly users11 August 2026 — 21,647 monthly users12 August 2026 — 21,524 monthly users13 August 2026 — 21,868 monthly users14 August 2026 — 21,969 monthly users15 August 2026 — 21,969 monthly users17 August 2026 — 20,148 monthly users18 August 2026 — 20,105 monthly users20 August 2026 — 20,166 monthly users21 August 2026 — 20,182 monthly users23 August 2026 — 20,688 monthly users24 August 2026 — 21,208 monthly users25 August 2026 — 21,520 monthly users26 August 2026 — 21,743 monthly users27 August 2026 — 21,644 monthly users28 August 2026 — 21,524 monthly users29 August 2026 — 20,849 monthly users30 August 2026 — 20,533 monthly users31 August 2026 — 20,284 monthly users1 September 2026 — 20,439 monthly users2 September 2026 — 20,212 monthly users4 September 2026 — 19,451 monthly users7 September 2026 — 18,363 monthly users10 September 2026 — 18,102 monthly users12 September 2026 — 19,233 monthly users14 September 2026 — 18,571 monthly users16 September 2026 — 18,413 monthly users18 September 2026 — 18,576 monthly users1 October 2026 — 22,492 monthly users6 October 2026 — 23,231 monthly users10 October 2026 — 24,984 monthly users13 October 2026 — 24,043 monthly users16 October 2026 — 24,278 monthly users17 October 2026 — 24,731 monthly users18 October 2026 — 24,841 monthly users19 October 2026 — 24,828 monthly users20 October 2026 — 24,357 monthly users21 October 2026 — 24,921 monthly users22 October 2026 — 23,775 monthly users23 October 2026 — 22,657 monthly users24 October 2026 — 21,487 monthly users25 October 2026 — 20,149 monthly users26 October 2026 — 21,021 monthly users27 October 2026 — 22,563 monthly users28 October 2026 — 22,994 monthly users29 October 2026 — 23,946 monthly users31 October 2026 — 24,542 monthly users2 November 2026 — 24,323 monthly users3 November 2026 — 24,473 monthly users4 November 2026 — 25,944 monthly users5 November 2026 — 26,198 monthly users7 August 20265 November 2026
53 measurements spanning 90 days, net +4,738. 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 16,888–27,412 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 53
Measured (UTC)Monthly usersChange
5 Nov 2026, 19:1626,198+254
4 Nov 2026, 18:3125,944+1,471
3 Nov 2026, 15:4724,473+150
2 Nov 2026, 17:2524,323-219
31 Oct 2026, 19:0724,542+596
29 Oct 2026, 17:0623,946+952
28 Oct 2026, 19:2922,994+431
27 Oct 2026, 16:2622,563+1,542
26 Oct 2026, 17:4621,021+872
25 Oct 2026, 15:0020,149-1,338
24 Oct 2026, 15:2821,487-1,170
23 Oct 2026, 16:4422,657-1,118
22 Oct 2026, 17:0423,775-1,146
21 Oct 2026, 08:3124,921+564
20 Oct 2026, 04:3824,357-471
19 Oct 2026, 01:0624,828-13
18 Oct 2026, 00:4424,841+110
17 Oct 2026, 00:2624,731+453
16 Oct 2026, 03:0024,278+235
13 Oct 2026, 22:4424,043first 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 5 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“SMS |M| 5 c:” (@OnlineSmsM5_bot), 26,198 monthly users as measured 5 November 2026. Telegram Register, tgregister.com/channel/OnlineSmsM5_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.