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

Channel

Trench Radar | Announcements

@trenchradar

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,104subscribers

-372 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
Descriptionhttps://x.com/TrenchRadar | made by @maroon280
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 live14 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/trenchradar

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 67% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

7,1047,4777,290.57 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 September 2026 — 7,335 subscribers12 September 2026 — 7,321 subscribers15 September 2026 — 7,303 subscribers27 September 2026 — 7,264 subscribers5 October 2026 — 7,246 subscribers12 October 2026 — 7,220 subscribers15 October 2026 — 7,210 subscribers18 October 2026 — 7,197 subscribers21 October 2026 — 7,195 subscribers24 October 2026 — 7,184 subscribers27 October 2026 — 7,175 subscribers30 October 2026 — 7,165 subscribers2 November 2026 — 7,152 subscribers5 November 2026 — 7,139 subscribers9 November 2026 — 7,119 subscribers14 November 2026 — 7,104 subscribers7 August 202614 November 2026
27 measurements spanning 99 days, net -372. 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,048–7,533 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
14 Nov 2026, 07:507,104-15
9 Nov 2026, 10:597,119-20
5 Nov 2026, 15:497,139-13
2 Nov 2026, 19:577,152-13
30 Oct 2026, 15:287,165-10
27 Oct 2026, 20:567,175-9
24 Oct 2026, 16:177,184-11
21 Oct 2026, 15:567,195-2
18 Oct 2026, 13:457,197-13
15 Oct 2026, 09:017,210-10
12 Oct 2026, 14:067,220-26
5 Oct 2026, 17:577,246-18
27 Sept 2026, 23:367,264-39
15 Sept 2026, 17:007,303-18
12 Sept 2026, 02:587,321-14
7 Sept 2026, 20:187,335-34
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,428first reading

Engagement

28 posts held, back to 15 April 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 40 pages of 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 28 posts for this entry, the most recent from 13 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
20
Links
39

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

309 reactions across 24 posts, in 16 distinct kinds. The most used accounts for 40.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥12640.8%
❤12239.5%
👍196.15%
👏92.91%
🏆72.27%
❤‍🔥41.29%
👎41.29%
🍾30.971%
💩30.971%
🤷30.971%
🙏20.647%
🤝20.647%
🤮20.647%
💋10.324%
😁10.324%
🥰10.324%

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 24 of the 28 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 309 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 28 most recent posts we hold, published 15 April 2025 to 13 September 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

13 Sept 2026, 11:18 UTC997 views13 reactionsread 18 November 2026
Photo

not sure what to buy? the bot also digs in with an AI agent thru the token's twitter, sites (actually SEES them to avoid vibecoded slop), checks pump fun and fomo thesis/callouts, reads thru their twitter & the overall narrative & spots weak points in the narratives so you're not blindsided.

❤9🔥4

13 Sept 2026, 11:15 UTC912 views14 reactionsread 18 November 2026
Photo

believe me when i say we're cooking. blue dots = potential re-entries first green = posted call in the channel. both just from the past 12 hours. today is a good day. keep an eye out on this notification channel. i will literally be opening this to approximately ~50 ish seats AT MOST to not dilute the edge.

🔥9❤3🙏2

10 Sept 2026, 01:03 UTC893 views10 reactionsread 18 November 2026
Photo

actual alerts from the telegram channel in the past day. very good numbers for what an otherwise was a very bad day with everything going down. invites soon.

🔥8❤2

8 Sept 2026, 09:04 UTC978 views10 reactionsread 18 November 2026
Photo

sneak peak 👀 so far we’ve achieved a stable ~40% 2x hit rate, including various runners posted below. 👇 Stats overview for the past 3 days of calls: Total of 350 calls, roughly ~5 calls an hour: 1. 142 reached 2x (40%) 2. 82 cleared 3x (23%) 3. 10 were breakouts, going from 10x all the way up to ~100x (~3%, easier if you have an eye for narratives) And those are just the outcomes within three hours of the alert, …

🔥6❤4

4 Sept 2026, 22:16 UTC989 views12 reactionsread 18 November 2026
Photo

Robinhood Chain has been gathering quite a bit of volume + opportunities in the past month or so. I normally don't try to chase around chains until they've been proven winners and sustained for a while, as I always build my own infrastructure when it comes to any web3 stuff. So, I'm happy to announce we're working on free tools for RH as well, coming within this month as early access. Unlike bundle tools, this one …

🔥6❤2👍2👎2

26 Aug 2026, 00:21 UTC≈1,150 views10 reactionsread 18 November 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…

🔥5🍾3👍2

11 May 2026, 03:53 UTC≈2,410 views11 reactionsread 18 November 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≈4,180 views7 reactionsread 18 November 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,820 views9 reactionsread 18 November 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!

🔥5❤3💋1

Showing the 12 most recent of 28 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Trench Radar | Announcements” (@trenchradar), 7,104 subscribers as measured 14 November 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.