转区端口稳定奔放 赞助自助投喂地址:https://xx.youxi186.com/shop/xunlian 反馈加时送卡
❤10🤯2👎1
Signed 眷頋(已饿死)

Channel
@slboos
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
36,930subscribers
-1,360 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002061061953 |
|---|---|
| Type | Channel |
| Username | @slboos |
| Description | 所有产品均来自于互联网 只用于交流研究 严禁用于一切非法业务! 请自觉遵守中华人民共和国法律 一切法律责任与本人无关! |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/slboos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 19:47 | 36,930 | -87 |
| 21 Aug 2026, 10:38 | 37,017 | -77 |
| 20 Aug 2026, 09:34 | 37,094 | -37 |
| 19 Aug 2026, 09:52 | 37,131 | -112 |
| 18 Aug 2026, 09:33 | 37,243 | -120 |
| 17 Aug 2026, 13:07 | 37,363 | -142 |
| 16 Aug 2026, 08:17 | 37,505 | -108 |
| 14 Aug 2026, 21:07 | 37,613 | -125 |
| 13 Aug 2026, 14:08 | 37,738 | -43 |
| 12 Aug 2026, 16:34 | 37,781 | -111 |
| 11 Aug 2026, 18:06 | 37,892 | -50 |
| 10 Aug 2026, 19:18 | 37,942 | -104 |
| 9 Aug 2026, 17:51 | 38,046 | -124 |
| 8 Aug 2026, 18:01 | 38,170 | -108 |
| 7 Aug 2026, 17:31 | 38,278 | -12 |
| 7 Aug 2026, 13:02 | 38,290 | first reading |
20 posts held, back to 22 January 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 35 pagesof 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 9 October 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 23 August 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.
217 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 61.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 133 | 61.3% | |
| ❤ | 67 | 30.9% | |
| 😱 | 6 | 2.76% | |
| 👎 | 4 | 1.84% | |
| 🥰 | 3 | 1.38% | |
| 👏 | 2 | 0.922% | |
| 🤯 | 2 | 0.922% |
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 16 of the 20 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 217reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 22 January 2025 to 9 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
转区端口稳定奔放 赞助自助投喂地址:https://xx.youxi186.com/shop/xunlian 反馈加时送卡
❤10🤯2👎1
Signed 眷頋(已饿死)
q区收把传世武器代价滴,传家宝勿扰 @juangunb
❤1
Signed 眷頋(已饿死)
Q区收一把尾刺,带价来,合适直接秒,走闲鱼 @xiaob537
❤1
Signed 。
复活半火端口 无视举报禁网 无视禁网标记的37天 禁止使用注入追踪/CA内存/遍历功能/ 支持内核/内核追/改文件/直装 支持基质功能(oe的内核追可以用) 半火端口禁止使用注入追踪 第一次使用规则那里点击小闹钟更新 端口账密:juangu10086 公益官方频道:https://t.me/zpgcnm 公益交流群:https://t.me/+VB5hCuTuyhU4MDM1 反馈: @xldwbot 持续反馈等于一直公益
👍42❤20👏2🥰1
Signed 眷頋(已饿死)
通知:所有人把手机日历调到9月30号,明天开始放国庆
👍14😱6❤2
Signed 眷頋(已饿死)
训练和平端口 pinned Deleted message
训练和平端口 pinned Deleted message
1.数据包过期 请调整本地时间,跟随网络时间 2.没有悬浮窗 请刷入驱动,MT以root执行驱动脚本!! 3.系统错误 卡密不要带空格以及不要带回车 4.一直检测更新 请授权root权限,随机生成的包要重新给root!! 5.对局内被踢 这是新加的行为检测,请配合自瞄使用即可规避,自瞄很安全!标注个危险是人为危险,而不是功能危险!会演戏随便使用! 6.点击不动悬浮窗 请不要随便修改分辨率 7.绘制会闪 请关闭内存拓展 8.绘制卡顿 请使用qx或者dev驱动,hook本来就卡,如果你使用的就是dev或者qx请关闭内存拓展!! 9.严禁使用多类模块 自行排查 目前已知大部分使用 tricky-store模块,tricky-store模块会hook游戏libc内存函数,被游戏检测到会三方十年 10.驱动选择 首选RT dev驱动,安全性最高。 OE内置驱动请先测试是否稳定,稳定在进行长期使用
❤12👍11🥰1
Signed 眷頋(已饿死)
赞助端口卡网: https://shop.xuanlingka.com/shop/xunlian 😀投放广告/项目合作/端口搭建联系: @juangubot 🥰端口反馈: @xldwbot 没有=关闭公益 🥰公益点击:https://t.me/ZPGCNM/10053
👍8❤2👎2
Signed 眷頋(已饿死)
训练和平端口 pinned Deleted message
赞助端口卡网: https://shop.xuanlingka.com/shop/xunlian 😀投放广告/项目合作/端口搭建联系: @juangubot 🥰端口反馈: @xldwbot 没有=关闭公益 🥰公益点击:https://t.me/ZPGCNM/10053
👍4❤3
Signed 眷頋(已饿死)
😀高级😆搜索群 全网独一无二的搜索群无敌多资源 你想看的应有尽有 https://t.me/+VB5hCuTuyhU4MDM1 我们这个搜索群特点是 反应快没有延迟 资源多不卡顿
👍10
Signed 眷頋(已饿死)
Showing the 12 most recent of 20 posts we hold for @slboos. 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.
Citation-graph rank — 154,125 of 1,584,486entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“训练和平端口” (@slboos), 36,930 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/slboos.
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.