Telegram RegisterThe public register of Telegram

Channel

Tron Trending by Suntron

@tronbots

2 usernames

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

431subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002203324330
TypeChannel
Usernames@tronbots @tronscanner
Created27 August 2024measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/tronbots

Growth

4314334327 Aug 2026, 13:15 — 433 subscribers7 Aug 2026, 13:34 — 433 subscribers8 Aug 2026, 05:17 — 433 subscribers8 Aug 2026, 09:15 — 432 subscribers8 Aug 2026, 12:35 — 431 subscribers7 Aug 2026, 13:158 Aug 2026, 12:35
5 measurements taken within a single day, net -2. 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 431–433 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:35431-1
8 Aug 2026, 09:15432-1
8 Aug 2026, 05:17433no change
7 Aug 2026, 13:34433no change
7 Aug 2026, 13:15433first reading

Engagement

2 posts held, back to 27 August 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 6 September 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Sept 2024, 13:43 UTC≈7,240 viewsread 8 August 2026

🔴 @tronbots 🥇- $SUNDOG 6.68% 🥈- $SUNWUKONG 37.19% 🥉- $Neiro 21422.73% ———————————— 4️⃣- $FOFAR 51.11% 5️⃣- $SUNCAT 45.55% 6️⃣- $TBULL 157.35% 7️⃣- $BULL -1.08% 8️⃣- $DOGGYSAN -5.37% 9️⃣- $KPEPE 1562.38% 🔟- $ROCK 31.99% ———————————— 🔢- $MWD -3.46% 🔢- $BIAO 69.85% 🔢- $KIDDO 193.54% 🔢- $SunKitty 145.47% 🔢- $ELONWUKONG -78.73% ℹ️ Trending data is automatically updated by @SunTronTrendingBot every 30 seconds . updated a

Showing the 2 most recent of 2 posts we hold for @tronbots. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

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

“Tron Trending by Suntron” (@tronbots), 431 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/tronbots.

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.