Telegram RegisterThe public register of Telegram
Telegram profile photo for Tickets • Розыгрыши

Bot

Tickets • Розыгрыши

@TicketsBot

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

136,268monthly users

+48,590 since we began measuring on 8 August 2026

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

Register entry

Telegram ID679409738
TypeBot
Username@TicketsBot
First recorded10 August 2026
Last confirmed live24 September 2026
Measurements held20
Confirmed unchanged1 time, most recently 24 September 2026
On Telegramt.me/TicketsBot

Topic

Giveaways & airdrops — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 why it has no browse page of its own yet.

Growth

77,448136,268106,8588 August 2026 — 87,678 monthly users10 August 2026 — 87,678 monthly users11 August 2026 — 89,296 monthly users15 August 2026 — 86,859 monthly users16 August 2026 — 87,780 monthly users17 August 2026 — 87,319 monthly users20 August 2026 — 78,142 monthly users23 August 2026 — 77,487 monthly users25 August 2026 — 77,448 monthly users27 August 2026 — 82,156 monthly users29 August 2026 — 88,166 monthly users31 August 2026 — 91,079 monthly users1 September 2026 — 92,313 monthly users3 September 2026 — 105,379 monthly users5 September 2026 — 115,599 monthly users8 September 2026 — 122,593 monthly users11 September 2026 — 122,317 monthly users14 September 2026 — 134,674 monthly users18 September 2026 — 133,202 monthly users24 September 2026 — 136,268 monthly users8 August 202624 September 2026
20 measurements spanning 48 days, net +48,590. 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 68,625–145,091 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
24 Sept 2026, 21:39136,268+3,066
18 Sept 2026, 15:41133,202-1,472
14 Sept 2026, 13:59134,674+12,357
11 Sept 2026, 05:59122,317-276
8 Sept 2026, 11:15122,593+6,994
5 Sept 2026, 05:57115,599+10,220
3 Sept 2026, 07:55105,379+13,066
1 Sept 2026, 00:4592,313+1,234
31 Aug 2026, 01:4491,079+2,913
29 Aug 2026, 23:3988,166+6,010
27 Aug 2026, 23:0582,156+4,708
25 Aug 2026, 02:2877,448-39
23 Aug 2026, 19:5577,487-655
20 Aug 2026, 22:0778,142-9,177
17 Aug 2026, 17:2887,319-461
16 Aug 2026, 14:0687,780+921
15 Aug 2026, 00:1886,859-2,437
11 Aug 2026, 09:0389,296+1,618
10 Aug 2026, 19:3887,678no change
8 Aug 2026, 05:1587,678first 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 September 2026 — this entry's latest reading, not the date you are reading this.

“Tickets • Розыгрыши” (@TicketsBot), 136,268 monthly users as measured 24 September 2026. Telegram Register, tgregister.com/channel/TicketsBot.

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.