Telegram RegisterThe public register of Telegram
Telegram profile photo for Jetton Games Finish width asset mountain come faculty

Bot

Jetton Games Finish width asset mountain come faculty

@jetons

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

30,652monthly users

+461 since we began measuring on 11 August 2026

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

Register entry

Telegram ID8732409331
TypeBot
Username@jetons
First recorded14 August 2026
Last confirmed live26 August 2026
Measurements held13
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/jetons

Growth

30,19130,91430,552.511 August 2026 — 30,191 monthly users11 August 2026 — 30,408 monthly users12 August 2026 — 30,403 monthly users14 August 2026 — 30,403 monthly users14 August 2026 — 30,611 monthly users16 August 2026 — 30,731 monthly users17 August 2026 — 30,813 monthly users18 August 2026 — 30,664 monthly users20 August 2026 — 30,809 monthly users22 August 2026 — 30,767 monthly users23 August 2026 — 30,914 monthly users26 August 2026 — 30,657 monthly users26 August 2026 — 30,652 monthly users30,65211 August 202626 August 2026
13 measurements spanning 16 days, net +461. 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 30,083–31,022 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Aug 2026, 23:2330,652-5
26 Aug 2026, 02:2630,657-257
23 Aug 2026, 22:3730,914+147
22 Aug 2026, 08:3830,767-42
20 Aug 2026, 20:1630,809+145
18 Aug 2026, 21:5430,664-149
17 Aug 2026, 18:5830,813+82
16 Aug 2026, 15:1330,731+120
14 Aug 2026, 21:5330,611+208
14 Aug 2026, 02:5530,403no change
12 Aug 2026, 09:1530,403-5
11 Aug 2026, 12:4930,408+217
11 Aug 2026, 04:4530,191first 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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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 26 August 2026 — this entry's latest reading, not the date you are reading this.

“Jetton Games Finish width asset mountain come faculty” (@jetons), 30,652 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/jetons.

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.