Telegram RegisterThe public register of Telegram
Telegram profile photo for Notz - SMS

Bot

Notz - SMS

@NotzSMSBot

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

26,421monthly users

+4,998 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 ID1464242559
TypeBot
Username@NotzSMSBot
First recorded16 August 2026
Last confirmed live5 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/NotzSMSBot

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

20,19726,99723,5977 August 2026 — 21,423 monthly users8 August 2026 — 21,414 monthly users10 August 2026 — 21,295 monthly users11 August 2026 — 21,126 monthly users12 August 2026 — 21,137 monthly users13 August 2026 — 21,135 monthly users14 August 2026 — 20,583 monthly users16 August 2026 — 20,930 monthly users16 August 2026 — 20,930 monthly users17 August 2026 — 20,654 monthly users19 August 2026 — 20,602 monthly users20 August 2026 — 20,641 monthly users21 August 2026 — 20,497 monthly users23 August 2026 — 20,778 monthly users25 August 2026 — 20,678 monthly users26 August 2026 — 20,690 monthly users27 August 2026 — 20,698 monthly users28 August 2026 — 20,746 monthly users29 August 2026 — 20,770 monthly users30 August 2026 — 20,713 monthly users31 August 2026 — 20,197 monthly users2 September 2026 — 20,464 monthly users4 September 2026 — 20,621 monthly users6 September 2026 — 20,716 monthly users9 September 2026 — 20,442 monthly users12 September 2026 — 20,754 monthly users13 September 2026 — 20,606 monthly users15 September 2026 — 20,486 monthly users17 September 2026 — 20,525 monthly users28 September 2026 — 20,355 monthly users5 October 2026 — 20,450 monthly users9 October 2026 — 21,936 monthly users13 October 2026 — 26,295 monthly users14 October 2026 — 26,225 monthly users15 October 2026 — 26,353 monthly users16 October 2026 — 26,422 monthly users18 October 2026 — 26,443 monthly users18 October 2026 — 26,468 monthly users19 October 2026 — 26,498 monthly users21 October 2026 — 26,386 monthly users22 October 2026 — 26,891 monthly users23 October 2026 — 26,995 monthly users25 October 2026 — 26,997 monthly users26 October 2026 — 26,864 monthly users27 October 2026 — 26,350 monthly users28 October 2026 — 26,685 monthly users29 October 2026 — 26,760 monthly users30 October 2026 — 26,775 monthly users1 November 2026 — 26,708 monthly users2 November 2026 — 26,647 monthly users3 November 2026 — 26,443 monthly users4 November 2026 — 26,374 monthly users5 November 2026 — 26,421 monthly users26,4217 August 20265 November 2026
53 measurements spanning 90 days, net +4,998. 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 19,177–28,017 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, 15:2126,421+47
4 Nov 2026, 18:0626,374-69
3 Nov 2026, 15:5126,443-204
2 Nov 2026, 13:5026,647-61
1 Nov 2026, 16:2726,708-67
30 Oct 2026, 13:5526,775+15
29 Oct 2026, 17:1526,760+75
28 Oct 2026, 16:0726,685+335
27 Oct 2026, 14:1826,350-514
26 Oct 2026, 12:1826,864-133
25 Oct 2026, 12:5626,997+2
23 Oct 2026, 14:3726,995+104
22 Oct 2026, 12:4626,891+505
21 Oct 2026, 04:0126,386-112
19 Oct 2026, 23:4426,498+30
18 Oct 2026, 23:1626,468+25
18 Oct 2026, 01:4626,443+21
16 Oct 2026, 23:1126,422+69
15 Oct 2026, 21:1526,353+128
14 Oct 2026, 20:5526,225first 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“Notz - SMS” (@NotzSMSBot), 26,421 monthly users as measured 5 November 2026. Telegram Register, tgregister.com/channel/NotzSMSBot.

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.