Telegram RegisterThe public register of Telegram
Telegram profile photo for Upscale

Bot

Upscale

@UpscaleTradeBot

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

19,056monthly users

+1,362 since we began measuring on 5 August 2026

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

Register entry

Telegram ID8186486708
TypeBot
Username@UpscaleTradeBot
First recorded16 August 2026
Last confirmed live17 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/UpscaleTradeBot

Growth

17,69419,08318,388.55 August 2026 — 17,694 monthly users7 August 2026 — 18,202 monthly users8 August 2026 — 18,223 monthly users10 August 2026 — 18,193 monthly users11 August 2026 — 18,166 monthly users13 August 2026 — 18,633 monthly users14 August 2026 — 18,826 monthly users15 August 2026 — 19,083 monthly users16 August 2026 — 19,083 monthly users17 August 2026 — 19,056 monthly users19,0565 August 202617 August 2026
10 measurements spanning 11 days, net +1,362. 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 17,486–19,291 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
17 Aug 2026, 09:4319,056-27
16 Aug 2026, 20:4819,083no change
15 Aug 2026, 17:5319,083+257
14 Aug 2026, 05:1518,826+193
13 Aug 2026, 01:2818,633+467
11 Aug 2026, 02:0218,166-27
10 Aug 2026, 03:0118,193-30
8 Aug 2026, 02:1118,223+21
7 Aug 2026, 05:4318,202+508
5 Aug 2026, 22:0217,694first 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

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 170 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Upscale” (@UpscaleTradeBot), 19,056 monthly users as measured 17 August 2026. Telegram Register, tgregister.com/channel/UpscaleTradeBot.

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.