Bot
KUPIKOD Чат поддержки
@KUPIKOD_bot
On this record: Growth · Engagement · Cite this entry
40,826monthly users
-3,744 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 5601268378 |
|---|---|
| Type | Bot |
| Username | @KUPIKOD_bot |
| First recorded | 12 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/KUPIKOD_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 26 Aug 2026, 23:57 | 40,826 | +125 |
| 25 Aug 2026, 21:13 | 40,701 | +718 |
| 24 Aug 2026, 19:35 | 39,983 | -367 |
| 23 Aug 2026, 01:29 | 40,350 | -1,708 |
| 19 Aug 2026, 17:37 | 42,058 | +140 |
| 18 Aug 2026, 14:14 | 41,918 | -42 |
| 16 Aug 2026, 15:35 | 41,960 | -298 |
| 14 Aug 2026, 23:07 | 42,258 | -367 |
| 12 Aug 2026, 19:43 | 42,625 | -780 |
| 12 Aug 2026, 19:25 | 43,405 | no change |
| 11 Aug 2026, 20:02 | 43,405 | -654 |
| 8 Aug 2026, 17:41 | 44,059 | -511 |
| 6 Aug 2026, 22:29 | 44,570 | 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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“KUPIKOD Чат поддержки” (@KUPIKOD_bot), 40,826 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/KUPIKOD_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.