Bot
Золотое Яблоко: поддержка
@GoldappleSupportBot
On this record: Growth · Engagement · Cite this entry
27,192monthly users
+1,774 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 ID | 6169867583 |
|---|---|
| Type | Bot |
| Username | @GoldappleSupportBot |
| First recorded | 15 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/GoldappleSupportBot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 24 Aug 2026, 21:15 | 27,192 | -175 |
| 23 Aug 2026, 09:59 | 27,367 | +38 |
| 21 Aug 2026, 20:34 | 27,329 | +1,394 |
| 20 Aug 2026, 15:48 | 25,935 | +52 |
| 18 Aug 2026, 11:55 | 25,883 | +104 |
| 17 Aug 2026, 10:25 | 25,779 | +221 |
| 15 Aug 2026, 02:34 | 25,558 | no change |
| 14 Aug 2026, 05:16 | 25,558 | +402 |
| 10 Aug 2026, 21:23 | 25,156 | -78 |
| 9 Aug 2026, 19:02 | 25,234 | -361 |
| 8 Aug 2026, 18:41 | 25,595 | +177 |
| 6 Aug 2026, 22:24 | 25,418 | first 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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“Золотое Яблоко: поддержка” (@GoldappleSupportBot), 27,192 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/GoldappleSupportBot.
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.