Telegram RegisterThe public register of Telegram
Telegram profile photo for DETECTOR AI BOT

Channel

DETECTOR AI BOT

@DetectorChanel

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

122subscribers

-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-1002117475750
TypeChannel
Username@DetectorChanel
Created6 March 2024measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/DetectorChanel

Growth

1221241237 August 2026 — 124 subscribers9 August 2026 — 124 subscribers15 August 2026 — 122 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, 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 122–124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 16:04122-2
9 Aug 2026, 03:02124no change
7 Aug 2026, 12:27124first reading

Engagement

2 posts held, back to 6 March 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 29 April 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

29 Apr 2024, 13:28 UTC≈1,020 views0 reactionsread 9 August 2026

🎁 Detector Bot - Free signals (+60s) 🎁 You can enjoy free alpha signals with our free tier group which come with a 60s delay. 🔥LIQUIDITY BURN DETECTOR: https://t.me/LiquidityBurn 🎯SNIPE DETECTOR: https://t.me/SnipeDetector 💻PRE-APPROVAL DETECTOR: https://t.me/PreApproval Join this group with the link above 👆

Showing the 2 most recent of 2 posts we hold for @DetectorChanel. 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“DETECTOR AI BOT” (@DetectorChanel), 122 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/DetectorChanel.

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.