Telegram RegisterThe public register of Telegram
Telegram profile photo for TT Save

Bot

TT Save

@Buddy_saveTT_bot

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

31,313monthly users

+602 since we began measuring on 8 August 2026

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

Register entry

Telegram ID1438364794
TypeBot
Username@Buddy_saveTT_bot
First recorded14 August 2026
Last confirmed live4 September 2026
Measurements held21
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/Buddy_saveTT_bot

Growth

29,86031,31330,586.58 August 2026 — 30,711 monthly users10 August 2026 — 30,575 monthly users11 August 2026 — 30,021 monthly users12 August 2026 — 29,988 monthly users14 August 2026 — 29,988 monthly users14 August 2026 — 30,325 monthly users16 August 2026 — 30,285 monthly users17 August 2026 — 30,243 monthly users19 August 2026 — 30,239 monthly users20 August 2026 — 30,234 monthly users22 August 2026 — 30,183 monthly users23 August 2026 — 29,860 monthly users25 August 2026 — 30,282 monthly users25 August 2026 — 30,424 monthly users27 August 2026 — 30,463 monthly users29 August 2026 — 30,672 monthly users30 August 2026 — 30,738 monthly users31 August 2026 — 30,884 monthly users31 August 2026 — 30,983 monthly users2 September 2026 — 31,124 monthly users4 September 2026 — 31,313 monthly users8 August 20264 September 2026
21 measurements spanning 27 days, net +602. 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 29,642–31,531 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 21
Measured (UTC)Monthly usersChange
4 Sept 2026, 10:2131,313+189
2 Sept 2026, 21:2331,124+141
31 Aug 2026, 20:5430,983+99
31 Aug 2026, 00:2630,884+146
30 Aug 2026, 02:2430,738+66
29 Aug 2026, 05:3430,672+209
27 Aug 2026, 01:4630,463+39
25 Aug 2026, 22:5430,424+142
25 Aug 2026, 01:3830,282+422
23 Aug 2026, 17:1329,860-323
22 Aug 2026, 05:1430,183-51
20 Aug 2026, 21:3730,234-5
19 Aug 2026, 18:0230,239-4
17 Aug 2026, 14:0730,243-42
16 Aug 2026, 05:1630,285-40
14 Aug 2026, 17:5730,325+337
14 Aug 2026, 03:1429,988no change
12 Aug 2026, 04:5329,988-33
11 Aug 2026, 08:2630,021-554
10 Aug 2026, 07:3330,575first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 4 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 4 September 2026 — this entry's latest reading, not the date you are reading this.

“TT Save” (@Buddy_saveTT_bot), 31,313 monthly users as measured 4 September 2026. Telegram Register, tgregister.com/channel/Buddy_saveTT_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.