Telegram RegisterThe public register of Telegram
Telegram profile photo for Sweet Me AI (18+)

Bot

Sweet Me AI (18+)

@sweet_me_bot

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

111,240monthly users

+91,592 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8630934818
TypeBot
Username@sweet_me_bot
First recorded15 August 2026
Last confirmed live7 November 2026
Measurements held50
Confirmed unchanged2 times, most recently 7 November 2026
On Telegramt.me/sweet_me_bot

Topic

Adult — 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 90% 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

19,648116,36368,005.57 August 2026 — 19,648 monthly users9 August 2026 — 20,057 monthly users11 August 2026 — 20,550 monthly users11 August 2026 — 21,873 monthly users13 August 2026 — 22,644 monthly users15 August 2026 — 22,644 monthly users16 August 2026 — 23,477 monthly users17 August 2026 — 23,998 monthly users18 August 2026 — 24,467 monthly users19 August 2026 — 24,825 monthly users20 August 2026 — 25,078 monthly users23 August 2026 — 25,794 monthly users25 August 2026 — 24,372 monthly users26 August 2026 — 25,474 monthly users27 August 2026 — 25,785 monthly users28 August 2026 — 26,000 monthly users30 August 2026 — 26,747 monthly users31 August 2026 — 26,765 monthly users2 September 2026 — 27,213 monthly users3 September 2026 — 27,470 monthly users5 September 2026 — 27,915 monthly users8 September 2026 — 27,564 monthly users11 September 2026 — 27,497 monthly users13 September 2026 — 26,863 monthly users14 September 2026 — 27,499 monthly users16 September 2026 — 29,186 monthly users19 September 2026 — 31,035 monthly users25 September 2026 — 42,499 monthly users4 October 2026 — 68,927 monthly users8 October 2026 — 79,775 monthly users13 October 2026 — 93,075 monthly users14 October 2026 — 96,228 monthly users15 October 2026 — 101,101 monthly users17 October 2026 — 103,398 monthly users18 October 2026 — 105,048 monthly users19 October 2026 — 107,686 monthly users21 October 2026 — 109,056 monthly users22 October 2026 — 111,196 monthly users23 October 2026 — 114,683 monthly users24 October 2026 — 115,730 monthly users25 October 2026 — 116,363 monthly users26 October 2026 — 116,124 monthly users27 October 2026 — 115,690 monthly users29 October 2026 — 111,893 monthly users31 October 2026 — 114,825 monthly users1 November 2026 — 112,063 monthly users3 November 2026 — 115,694 monthly users4 November 2026 — 115,499 monthly users5 November 2026 — 115,150 monthly users6 November 2026 — 111,240 monthly users111,2407 August 20266 November 2026
50 measurements spanning 91 days, net +91,592. 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 5,141–130,870 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
6 Nov 2026, 05:27111,240-3,910
5 Nov 2026, 06:41115,150-349
4 Nov 2026, 08:06115,499-195
3 Nov 2026, 05:19115,694+3,631
1 Nov 2026, 11:29112,063-2,762
31 Oct 2026, 11:45114,825+2,932
29 Oct 2026, 15:30111,893-3,797
27 Oct 2026, 18:29115,690-434
26 Oct 2026, 18:27116,124-239
25 Oct 2026, 16:25116,363+633
24 Oct 2026, 16:36115,730+1,047
23 Oct 2026, 19:17114,683+3,487
22 Oct 2026, 17:44111,196+2,140
21 Oct 2026, 13:28109,056+1,370
19 Oct 2026, 11:57107,686+2,638
18 Oct 2026, 12:39105,048+1,650
17 Oct 2026, 13:54103,398+2,297
15 Oct 2026, 12:31101,101+4,873
14 Oct 2026, 12:3196,228+3,153
13 Oct 2026, 00:2093,075first 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 8 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“Sweet Me AI (18+)” (@sweet_me_bot), 111,240 monthly users as measured 6 November 2026. Telegram Register, tgregister.com/channel/sweet_me_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.