Channel
@AveETHTokenScanner_cn
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
534subscribers
-9 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002139302901 |
|---|---|
| Type | Channel |
| Username | @AveETHTokenScanner_cn |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/AveETHTokenScanner_cn |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 03:01 | 534 | -1 |
| 11 Sept 2026, 04:37 | 535 | -3 |
| 2 Sept 2026, 00:06 | 538 | +1 |
| 26 Aug 2026, 08:47 | 537 | -6 |
| 17 Aug 2026, 19:45 | 543 | no change |
| 17 Aug 2026, 19:30 | 543 | first reading |
20 posts held, back to 17 August 2026 — 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 20 posts for this entry, the most recent from 17 August 2026. An engagement rate over an empty window would be a number about nothing.
💠 ERC-20 新币部署 💠 代币: Robotics (Robotics) 合约: 0x6995ed3428678c6233dda673eeb289dca91a896f 总量: 1,000,000,000 (精度: 18) 持有人: 10 🐸🐸 |_0x2628...0316e2 99.4536% |_0x0000...00dead 0.3042% |_0x66f9...2a1c33 0.22% |_0x9295...da8d7a 0.01471% |_0x159d...73c24a 0.005018% 检测 | 网站 | 下载 | 社区 | Twitter
💠 ERC-20 新币开盘 💠 代币: SaveEF (Save Ethereum Foundation) 合约: 0xe6b6f542d5fbf975a5c2841fc81b835770ccbd6f LP: 0x008b88a0113cccbf7c610389fb7456dc7fa182c5 开盘价: $0.0{4}7095 市值: $7.13K 交易对: 99.51M SaveEF / 0.02 WETH Dex: Uniswapv3 流动性: $7.10K 狙击人: 2 抢购人: 0 持有人: 5 🐸 |_0x008b...a182c5 99.5064% |_0x4194...87ee5d 0.2474% |_0x94fc...0e78f9 0.2461% |_0xe6b6...ccbd6f 0% |_0x0000...000000 0% LP 持有人: 0 检测: 分数: 0…
💠 ERC-20 新币部署 💠 代币: SaveEF (Save Ethereum Foundation) 合约: 0xe6b6f542d5fbf975a5c2841fc81b835770ccbd6f 总量: 100,000,000 (精度: 18) 持有人: 3 🐸 |_0x008b...a182c5 100% |_0xe6b6...ccbd6f 0% |_0x0000...000000 0% 检测 | 网站 | 下载 | 社区 | Twitter
💠 ERC-20 新币开盘 💠 代币: USWR (United States Water Reserve) 合约: 0xf8d2fd8f3e81ff8e3fefedecda0f69e75e4eabb9 LP: 0x94b3ce660f98b17b9c418d45c2e821a3400e1956 开盘价: $0.0{7}4013 市值: $40.30 交易对: 948.82M USWR / 0.02 WETH Dex: Uniswapv2 流动性: $76.41 狙击人: 1 抢购人: 0 持有人: 5 🐸 |_0x94b3...0e1956 94.8818% |_0xbc82...d7e3a3 5% |_0x7b4e...6b01cb 0.1182% |_0xf8d2...4eabb9 0% |_0x0000...000000 0% LP 持有人: 0 检测: 分数: 0(🟢低风险…
💠 ERC-20 新币部署 💠 代币: USWR (United States Water Reserve) 合约: 0xf8d2fd8f3e81ff8e3fefedecda0f69e75e4eabb9 总量: 1,000,000,000 (精度: 9) 持有人: 4 🐸 |_0x94b3...0e1956 95% |_0xbc82...d7e3a3 5% |_0xf8d2...4eabb9 0% |_0x0000...000000 0% 检测 | 网站 | 下载 | 社区 | Twitter
💠 ERC-20 新币开盘 💠 代币: SWK (Sapphire Wisdom Kingdom) 合约: 0x0476f075b9d18a8672190ecae77f48d3b6359856 LP: 0xc59d5b508b9f14bb34a62bef9873be3cfc8ff5d8 开盘价: $0.0{11}7505 市值: $4.18K 交易对: 508000000.00M SWK / 2.00 WETH Dex: Uniswapv2 流动性: $3.81K 狙击人: 6 抢购人: 0 持有人: 9 🐸 |_0xc59d...8ff5d8 95.3276% |_0x6a48...20bf84 1.4149% |_0xe7d9...b92a2f 1.1711% |_0x8782...c52921 0.9919% |_0x7492...d0f1bd 0.597% LP 持有人: 0…
💠 ERC-20 新币开盘 💠 代币: FWAIR (FWAir) 合约: 0x2e98878e042515e5ef3465d6825c14794f819f7c LP: 0x4413985bd51f78df5a2b0915d322d874de0d1b70875e78486eeb447b99f60bf5 开盘价: $0.9659 市值: $9.66K 交易对: 9.91K FWAIR / 0.05 WETH Dex: Uniswapv4 流动性: $9.66K 狙击人: 5 抢购人: 0 持有人: 9 🐸 |_0x0000...e08a90 99.0994% |_0x0ad3...3be75c 0.2528% |_0x8a30...794137 0.1953% |_0x857d...abb7b7 0.1926% |_0x70b5...591f83 0.1541% LP 持有人: 0 检…
💠 ERC-20 新币部署 💠 代币: SWK (Sapphire Wisdom Kingdom) 合约: 0x0476f075b9d18a8672190ecae77f48d3b6359856 总量: 508,000,000,000,000 (精度: 18) 持有人: 3 🐸 |_0xc59d...8ff5d8 100% |_0x8260...7402d5 0% |_0x0000...000000 0% 检测 | 网站 | 下载 | 社区 | Twitter
💠 ERC-20 新币开盘 💠 代币: LMT (Lockheed Martin Corporation) 合约: 0x5db2976a60353df23c432aa4be8f54f57d1c8a2a LP: 0xf1220b2944ff024527294b254b6a18693dc9997f 开盘价: $0.0{11}4781 市值: $2.87K 交易对: 597989741.46M LMT / 1.50 WETH Dex: Uniswapv2 流动性: $5.73K 狙击人: 1 抢购人: 0 持有人: 4 🐸 |_0xf122...c9997f 99.9983% |_0x7b4e...6b01cb 0.001715% |_0x0000...000000 0% |_0xd977...f34bed 0% LP 持有人: 0 检测: 分数: 0(🟢低风险) |_LP 锁定: 0%|合约弃权…
💠 ERC-20 新币部署 💠 代币: LMT (Lockheed Martin Corporation) 合约: 0x5db2976a60353df23c432aa4be8f54f57d1c8a2a 总量: 598,000,000,000,000 (精度: 18) 持有人: 3 🐸 |_0xf122...c9997f 100% |_0x0000...000000 0% |_0xd977...f34bed 0% 检测 | 网站 | 下载 | 社区 | Twitter
💠 ERC-20 新币部署 💠 代币: EARTHDAY (Happy Earth Day) 合约: 0x27c87be41d654f64d9d57b3b5bca3095243780d6 总量: 420,690,000,000 (精度: 9) 持有人: 91 🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸 |_0x21a9...27c006 91.3033% |_0x47b4...4e0be5 3.0214% |_0xbae7...a39139 1.1558% |_0x27c8...3780d6 0.9269% |_0x0000...0088b8 0.6001% 检测 | 网站 | 下载 | 社区 | Twitter
💠 ERC-20 新币部署 💠 代币: SWISS (Knife) 合约: 0xd9c9341b5d17414ec7f0c7b4ef14f1a67130b90c 总量: 1,000,000,000 (精度: 18) 持有人: 407 🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸 |_0x40fd...0506c1 70.339% |_0xd9c9...30b90c 2.8624% |_0xc7a3...d731e9 1.7434% |_0xa12a...57e07a 1.3228% |_0x2efb...357200 1.1574% 检测 | 网站 | 下载 | 社区 | Twitter
Showing the 12 most recent of 20 posts we hold for @AveETHTokenScanner_cn. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Ave新币监控ETH” (@AveETHTokenScanner_cn), 534 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/AveETHTokenScanner_cn.
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.