Telegram RegisterThe public register of Telegram
Telegram profile photo for Trench Radar | Announcements

Channel

Trench Radar | Announcements

@trenchradar

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

7,369subscribers

-107 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002190048185
TypeChannel
Username@trenchradar
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/trenchradar

Growth

7,3697,4777,4237 August 2026 — 7,476 subscribers7 August 2026 — 7,476 subscribers8 August 2026 — 7,477 subscribers11 August 2026 — 7,464 subscribers14 August 2026 — 7,458 subscribers17 August 2026 — 7,440 subscribers21 August 2026 — 7,430 subscribers24 August 2026 — 7,428 subscribers27 August 2026 — 7,389 subscribers30 August 2026 — 7,373 subscribers2 September 2026 — 7,369 subscribers7 August 20262 September 2026
11 measurements spanning 26 days, net -107. 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 7,353–7,493 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 10:227,369-4
30 Aug 2026, 17:457,373-16
27 Aug 2026, 18:057,389-39
24 Aug 2026, 15:137,428-2
21 Aug 2026, 07:147,430-10
17 Aug 2026, 22:137,440-18
14 Aug 2026, 18:377,458-6
11 Aug 2026, 03:017,464-13
8 Aug 2026, 05:377,477+1
7 Aug 2026, 13:017,476no change
7 Aug 2026, 12:557,476first reading

Engagement

22 posts held, back to 15 April 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.48%
avg views ÷ 7,369 subscribers
Avg views / post
330
1 post measured
Reaction rate
2.73%
reactions ÷ views · ER floor
Posts in window
2
of 22 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 August 2026
Posts held22 (15 April 202526 August 2026)
Views total330
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 23:24 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

249 reactions across 19 posts, in 15 distinct kinds. The most used accounts for 41.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10241.0%
🔥9236.9%
👍176.83%
👏93.61%
🏆72.81%
❤‍🔥41.61%
🍾31.20%
💩31.20%
🤷31.20%
👎20.803%
🤝20.803%
🤮20.803%
💋10.402%
😁10.402%
🥰10.402%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 22 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 249 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 15 April 2025 to 26 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

26 Aug 2026, 00:21 UTC330 views9 reactionsread 28 August 2026
Photo

Been a while! Small quality of life update here. Having @TrenchScannerBot in your group chats will now scan tokens in the background as you share them, and will only alert you if a token has a particularly high cluster showing in a very short and non intrusive message. A lot of the terminals and scanners don’t have the sufficient algorithms to detect some shapes of bundling, especially with aged wallet behaviors an

🔥4🍾3👍2

11 May 2026, 03:53 UTC≈1,730 views11 reactionsread 28 August 2026
Photo

🎯 Cluster Viewer — now live on trench.bot Honest opener: the old bundle page on the site had been broken for a while. Clusters are the replacement, and they ship today — fully working, scanning every mint you throw at them. What Clusters do The system groups wallets that act together — buying in the same minute, funded from the same source, or matching across both — and scores each group from 0–100% across f

7🔥4

5 Dec 2025, 05:19 UTC≈3,860 views7 reactionsread 28 August 2026

Added basic support for all token2022 launches. Should be working just fine on @TrenchScannerBot Sorry for all the delay 🫡

🔥7

14 Nov 2025, 21:34 UTC≈4,530 views9 reactionsread 28 August 2026

Seeing many more token22 launches due to mayhem mode and pumpfun switching. We current don't have support for them (holder checks will always show 0%), but we'll be working on implementing that ASAP!

🔥53💋1

5 Nov 2025, 13:54 UTC≈4,850 views8 reactionsread 28 August 2026

Services will be going down for a little bit across everything. We've identified some critical data issue with one of our drives and we're working on fixing it right now. Sorry for all the delay!

7👍1

19 Oct 2025, 17:21 UTC≈4,770 views10 reactionsread 28 August 2026

We’ve been testing under load for the past 24 hours and we’ve found much more stable uptimes in the system so far. Additionally we’ve fixed a few small false positives flags for clusters so you should be seeing enhanced accuracy as well. If you have any issues with clusters failing to load for you please reach out @maroon280 for a fix!

7👍2👎1

18 Oct 2025, 06:33 UTC≈3,940 views5 reactionsread 28 August 2026

We’ll be temporarily pausing our cluster scanning for today while we do maintenance and scaling upgrades! Should be done in under 24 hours, there may be some downtime in the process but we’ll try to keep it as minimal as possible. Additionally, we’re also working on expanding our infrastructure to BNB, and we should be able to support it fairly soon!

5

28 Sept 2025, 04:52 UTC≈4,040 views15 reactionsread 28 August 2026
Photo

🧑‍💻 Creator Risk Profile in Clusters Due to a few requests, clusters now shows dev history and info like before! We initially didn't add this because we wanted the scanner to work on as many platforms as possible. However, a number of people requested this to be added back, and so we listened! You can now see the same full creator risk profile with each cluster scan. The only downside is that it only works with pum

8🔥5👏2

26 Sept 2025, 20:52 UTC≈3,170 views12 reactionsread 28 August 2026

After stress testing our new cluster systems under load and ensuring accuracy, we've decided to make it the primary scanning method. ⏳ Legacy Bundle Scanner Still Available For those of you who are stubborn and want the old trash: - Use /ob [ca] or /oldbundle [ca] - WARNING: Only works with pump.fun tokens - Still gets classifications wrong sometimes or misses real bundles ## 📈 What This Means - Default behavior:

🔥82👎1🥰1

26 Sept 2025, 01:18 UTC≈2,510 views11 reactionsread 28 August 2026
Photo

📦 Trench bundle intel is now inside every @RickBurpBot scan! From now on, whenever anyone runs a Rick scan in any Telegram group, you’ll see bundle data included. Click the 📦 and you’re instantly in a full Trench Radar scan. Rick runs the scan. Trench exposes the bundles. This means: ✔️ Bundle detection in every group and every scan that has Rick ✔️ One-click deep dives into full Trench analysis ⚠️ Tokens must be

🔥101

Showing the 12 most recent of 22 posts we hold for @trenchradar. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“Trench Radar | Announcements” (@trenchradar), 7,369 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/trenchradar.

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.