咕咕嘎嘎~ 发财喽~
👍3
Signed 情话

Channel
@sllhnb
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7,654subscribers
+7,587 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1004423790588 |
|---|---|
| Type | Channel |
| Username | @sllhnb |
| Created | 2 September 2026 — measured — dated from the channel’s first post |
| First recorded | 3 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/sllhnb |
Gaming — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 23:07 | 7,654 | -46 |
| 2 Nov 2026, 21:10 | 7,700 | -181 |
| 30 Oct 2026, 20:28 | 7,881 | -269 |
| 28 Oct 2026, 02:30 | 8,150 | -216 |
| 25 Oct 2026, 12:55 | 8,366 | -266 |
| 22 Oct 2026, 10:59 | 8,632 | -402 |
| 19 Oct 2026, 06:07 | 9,034 | -344 |
| 16 Oct 2026, 10:04 | 9,378 | -292 |
| 13 Oct 2026, 03:49 | 9,670 | -605 |
| 8 Oct 2026, 18:20 | 10,275 | -185 |
| 4 Oct 2026, 10:00 | 10,460 | -38 |
| 25 Sept 2026, 20:39 | 10,498 | +10 |
| 17 Sept 2026, 12:37 | 10,488 | +15 |
| 15 Sept 2026, 11:36 | 10,473 | +4 |
| 13 Sept 2026, 17:19 | 10,469 | +13 |
| 12 Sept 2026, 00:40 | 10,456 | +40 |
| 9 Sept 2026, 14:59 | 10,416 | +2,305 |
| 4 Sept 2026, 17:19 | 8,111 | +8,044 |
| 3 Sept 2026, 10:45 | 67 | no change |
| 3 Sept 2026, 10:30 | 67 | first reading |
14 posts held, back to 2 September 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 7 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 14 (2 September 2026 – 5 November 2026) |
| Views total | 1,251 |
| Reactions total | 17 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 00:08 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 6 November 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.
25 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 96.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 24 | 96.0% | |
| 👀 | 1 | 4.00% |
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 9 of the 14 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 2 September 2026 to 5 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram’s own ‘edited’ marker: 0 of 7 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
咕咕嘎嘎~ 发财喽~
👍3
Signed 情话
三角洲说的新迷雾灰度测试?
👍3
Signed 情话
目前是漏信息才透视或者巨人观 我手上四个号有不同程度的迷雾效果
👍3
Signed 情话
迷雾解决方案转载 头部碰撞方案 利用游戏场景中的碰撞体积,让角色头部持续与场景物体发生接触。 可尝试的位置: 天花板 铁楼梯 水下顶部 其他能够持续保持头部接触的场景 部分角色技能可以辅助寻找碰撞位置: 银翼:开启飞行技能。 回响:使用听力针。 乌噜噜:开启大招。 据反馈,部分场景下通过头部与环境碰撞,可以使地图视野恢复正常。 断网重连升级方案 直接断开网络连接。 基础操作: 找到楼梯或其他场景物体,让角色头部持续保持碰撞接触。 选择银翼,开启飞行技能并飞至较高位置。 保持头部与场景物体接触的同时断开网络。 等待一段时间后重新连接网络。 据反馈,部分账号可能触发整局持续生效的视野恢复效果。 升级方法: 在角色头部持续接触场景物体的状态下进行断网重连,重新连接后视野可能恢复正常。 目前已有玩家使用旅人进行测试,并反馈存在类似效果。 白号配合跑刀方案 通过白号与大号组队,尝试改善迷雾异常情况。 操作步骤: 准备一个白号,进入机…
👍3
Signed 情话
貌似出了个新迷雾 我有个号不加密 但是只有对面漏信息(响枪 挨打 漏脚)才绘制 其余时间遁地 /换号正常 上赛季末那几天就已经这样了
👍3
Signed 情话
🌚
👍1
Signed 情话
小神里跑路注销这个群自动转给我了🤓
👍1
Signed 情话
自愿赞助链接 https://fkli.cc/kRCn 此自愿赞助就是字面意思的自愿赞助,并非是换名卖您卡密,不赞助不会影响您的正常使用
👍1
Signed 神里 绫华(煮叶工艺解密)
Sticker, posted without a caption
Signed 幻想曲大王
暗区已经提上日程了,三角洲各方面完善后开始更新暗区 除了这两个游戏还有没有别的游戏要玩?
Signed 神里 绫华(煮叶工艺解密)
大家多拉点人 这周内破1k发800红包
Signed 神里 绫华(煮叶工艺解密)
交流群加一加,点开频道头像点讨论就能进了
Signed 神里 绫华(煮叶工艺解密)
Showing the 12 most recent of 14 posts we hold for @sllhnb. 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.
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.
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.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“神里公益内核” (@sllhnb), 7,654 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/sllhnb.
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.