Channel
@ScopexAI
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
112subscribers
-2 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002100668227 |
|---|---|
| Type | Channel |
| Username | @ScopexAI |
| Created | 27 January 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 11 September 2026 |
| On Telegram | t.me/ScopexAI |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 19:09 | 112 | -2 |
| 13 Aug 2026, 10:05 | 114 | no change |
| 12 Aug 2026, 17:33 | 114 | first reading |
10 posts held, back to 27 January 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 10 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
ScopexAI is being protected by @Safeguard Click below to verify you're human
RENOUNCE https://etherscan.io/tx/0xec05c997ed973d2a893ad9ef9e6ad72830698a9cc1b68b75c4cc506dddf14be3
LP LOCKED https://app.uncx.network/amm/uni-v2/pair/0xbF7cEdCd4c0e7aFA77c4EE71A3CF153fBDFc4821
Official $SCOPEX Contract : 0x6fc16de36e040e0c7d1a70d039ef701516516b32
Completion of Sniper Bot Series V.1.0 Development Great news, ScopexAI enthusiasts! We are thrilled to announce that the development of the Scopex Sniper Bot Series V.1.0 has been successfully completed. 👉Key Highlights of V.1.0: • User-Friendly Interface: Designed for ease of use, making wallet creation straightforward for both new and experienced traders. We’re committed to delivering the best in crypto tradin…
https://x.com/scopexcoin/status/1752114337580458038
Step into a new era with ScopeXAI! Beyond being a mere platform, it signifies a transformative shift towards a smarter, more streamlined, and ultimately more profitable landscape in crypto trading. Within our ecosystem , you'll find: - ScopeX Sniper Bot & App - ScopeX Scanner Bot - ScopeX Buy Bot - ScopeX Revenue-SharingModel This innovative model isn't just about transaction fees and advertising revenues; it's a c…
Channel created
Showing the 10 most recent of 10 posts we hold for @ScopexAI. 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.
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.
@ScopexAI named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“ScopexAI” (@ScopexAI), 112 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/ScopexAI.
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.