Telegram RegisterThe public register of Telegram
Telegram profile photo for 📥 Receive SMS BOT 📮

Bot

📥 Receive SMS BOT 📮

@ReceiveSMSRobot

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

22,993monthly users

+1,570 since we began measuring on 6 August 2026

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

Register entry

Telegram ID5555490172
TypeBot
Username@ReceiveSMSRobot
First recorded15 August 2026
Last confirmed live2 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/ReceiveSMSRobot

Growth

21,08323,34322,2136 August 2026 — 21,423 monthly users8 August 2026 — 21,083 monthly users10 August 2026 — 22,101 monthly users12 August 2026 — 22,198 monthly users14 August 2026 — 22,439 monthly users15 August 2026 — 22,439 monthly users17 August 2026 — 22,181 monthly users18 August 2026 — 22,925 monthly users19 August 2026 — 23,059 monthly users22 August 2026 — 22,719 monthly users24 August 2026 — 23,343 monthly users26 August 2026 — 23,090 monthly users28 August 2026 — 23,018 monthly users30 August 2026 — 22,963 monthly users2 September 2026 — 22,993 monthly users22,9936 August 20262 September 2026
15 measurements spanning 27 days, net +1,570. 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 20,744–23,682 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
2 Sept 2026, 12:4522,993+30
30 Aug 2026, 17:5722,963-55
28 Aug 2026, 13:5423,018-72
26 Aug 2026, 17:5723,090-253
24 Aug 2026, 15:1923,343+624
22 Aug 2026, 19:4722,719-340
19 Aug 2026, 14:1823,059+134
18 Aug 2026, 12:0422,925+744
17 Aug 2026, 09:5322,181-258
15 Aug 2026, 20:1322,439no change
14 Aug 2026, 12:3722,439+241
12 Aug 2026, 00:2422,198+97
10 Aug 2026, 04:4622,101+1,018
8 Aug 2026, 00:4121,083-340
6 Aug 2026, 23:0321,423first 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 9 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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“📥 Receive SMS BOT 📮” (@ReceiveSMSRobot), 22,993 monthly users as measured 2 September 2026. Telegram Register, tgregister.com/channel/ReceiveSMSRobot.

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.