Telegram RegisterThe public register of Telegram
Telegram profile photo for TRIO Network

Bot

TRIO Network

@TRIONetworkdrop_bot

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

24,855monthly users

-9,846 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 ID8286540731
TypeBot
Username@TRIONetworkdrop_bot
First recorded15 August 2026
Last confirmed live2 September 2026
Measurements held15
Confirmed unchanged2 times, most recently 2 September 2026
On Telegramt.me/TRIONetworkdrop_bot

Growth

23,30134,70129,0016 August 2026 — 34,701 monthly users8 August 2026 — 28,632 monthly users10 August 2026 — 24,087 monthly users11 August 2026 — 23,301 monthly users15 August 2026 — 23,815 monthly users15 August 2026 — 23,815 monthly users18 August 2026 — 25,238 monthly users19 August 2026 — 25,562 monthly users21 August 2026 — 25,686 monthly users24 August 2026 — 29,383 monthly users26 August 2026 — 24,271 monthly users27 August 2026 — 24,304 monthly users30 August 2026 — 25,140 monthly users31 August 2026 — 24,860 monthly users1 September 2026 — 24,855 monthly users24,8556 August 20261 September 2026
15 measurements spanning 26 days, net -9,846. 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 21,591–36,411 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
1 Sept 2026, 10:0524,855-5
31 Aug 2026, 09:1224,860-280
30 Aug 2026, 07:0525,140+836
27 Aug 2026, 05:4524,304+33
26 Aug 2026, 06:0924,271-5,112
24 Aug 2026, 06:1329,383+3,697
21 Aug 2026, 02:2825,686+124
19 Aug 2026, 01:2425,562+324
18 Aug 2026, 01:3325,238+1,423
15 Aug 2026, 18:4023,815no change
15 Aug 2026, 18:1423,815+514
11 Aug 2026, 22:4223,301-786
10 Aug 2026, 20:0524,087-4,545
8 Aug 2026, 01:1728,632-6,069
6 Aug 2026, 08:2334,701first 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 9 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.

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

“TRIO Network” (@TRIONetworkdrop_bot), 24,855 monthly users as measured 1 September 2026. Telegram Register, tgregister.com/channel/TRIONetworkdrop_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.