基础资料。 Member counts for @letst0p are recorded daily from Telegram's public page. Post activity, views, a trust score, and lookalike checks are added once the collector completes its first full read, usually within days.
最近发帖
带有收集指标的公开发帖信任信号
混合信号 64Confidence low: read from Telegram's public preview pages (12 recent posts with views spanning 63 days); forwarding, reactions and growth checks are added after a full read. Scores start at 60 and move with each signal; nothing scores 100.
- Views exceed the member count (1.3 per member): posts are forwarded widely or the audience has shrunk
- Views vary naturally across posts (spread 0.44) (+5)
关键事实
| 句柄 | @letst0p |
| 类型 | Telegram channel |
| 成员 | 10,570 |
| 官方的 | LETSTOP (STOP) |
| 每日发帖数 | 0.3 |
| 每个订阅者的浏览次数 | 1.62 |
| 信任分数 | 64 / 100, 混合信号, 低 confidence |
| 相似句柄 | 0 |
| 跟踪自 | 2026-09-06 |
类似社区
规模接近LETSTOP is a crypto Telegram channel with 10,570 members, ranked 884 of 7,365 indexed communities by size and 300 among channels. It posts about 0.3 times a day. Recent posts average 17,158 views, 1.62 per subscriber. Its trust score is 64 of 100 (mixed signals). It is the community listed on CoinGecko for LETSTOP (STOP), market cap rank 4993.
Source: Telegram's public data for @letst0p, collected by TGMetrics. Figures as of 2026-09-06. See the 方法论.
常见问题
Is @letst0p 官方 LETSTOP Telegram?
Yes. It is the Telegram community listed for LETSTOP (STOP) on CoinGecko, market cap rank 4993.
我如何验证官方链接?
打开项目自己的网站 或其 CoinGecko 列表 and follow the Telegram link from there. Official handles never ask for seed phrases or wallet connections in chat.
信任分数如何计算?
Every community starts at 60 and each signal moves it by a stated weight, measured against communities of similar size in this index. Channels are scored on views per subscriber, how much views vary across posts, whether views keep growing after posting, forwards and reactions per view, growth smoothness, who forwards it, and age. Thin data caps the score and lowers confidence; nothing scores 100.
多久更新一次?
成员数至少每天快照一次,活跃频道则每小时快照一次。发布指标在发布后1小时、24小时和7天时重新读取。