🚨 【突发|野草地群组没了】 野草地群组目前已无法访问,具体情况暂不明。 暂无官方公告,原因未知。 是解散、封禁还是临时调整,目前均无法确认。 📌 后续情况,持续关注。 💬 来源:谷雨影讯社 📢 分享频道:@Jsoo888 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo666_bot ☁️ 怕错过就常驻,圈内有资讯 · 时时有吃瓜

Channel
領域展開
@Jsoo888
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
8,580subscribers
+260 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002579673373 |
|---|---|
| Type | Channel |
| Username | @Jsoo888 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/Jsoo888 |
Topic
Film & TV — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 18:58 | 8,580 | +32 |
| 12 Sept 2026, 11:59 | 8,548 | +72 |
| 30 Aug 2026, 20:18 | 8,476 | -5 |
| 28 Aug 2026, 03:38 | 8,481 | -7 |
| 24 Aug 2026, 21:44 | 8,488 | +5 |
| 20 Aug 2026, 22:24 | 8,483 | +93 |
| 17 Aug 2026, 12:03 | 8,390 | +30 |
| 14 Aug 2026, 05:08 | 8,360 | +21 |
| 10 Aug 2026, 20:32 | 8,339 | +20 |
| 8 Aug 2026, 04:52 | 8,319 | -1 |
| 7 Aug 2026, 19:31 | 8,320 | no change |
| 7 Aug 2026, 19:18 | 8,320 | first reading |
Engagement
50 posts held, back to 22 July 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 24 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 15.8%
- avg views ÷ 8,580 subscribers
- Avg views / post
- 1,360
- 3 posts measured
- Reaction rate
- 0.134%
- reactions ÷ views · ER floor
- Posts in window
- 3
- of 50 held
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. It is computed over the 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 50 (22 July 2026 – 28 August 2026) |
| Views total | 4,068 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 17:17 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.
Reaction mix
143 reactions across 27 posts, in 12 distinct kinds. The most used accounts for 30.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 44 | 30.8% | |
| ❤ | 41 | 28.7% | |
| 🤣 | 30 | 21.0% | |
| 👏 | 10 | 6.99% | |
| 🎉 | 4 | 2.80% | |
| 🦄 | 4 | 2.80% | |
| 🔥 | 2 | 1.40% | |
| 😁 | 2 | 1.40% | |
| 😭 | 2 | 1.40% | |
| 🫡 | 2 | 1.40% | |
| 🍌 | 1 | 0.699% | |
| 😱 | 1 | 0.699% |
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 33 of the 50 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 143 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 50 most recent posts we hold, published 22 July 2026 to 28 August 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.
Recent posts
尊敬的 ntRRR 公益服用户: 时隔一年有余,ntRRR 公益服于今日重新开放邀请。 即日起,现有用户可向 @ntRRR_bot 发送 /redeemgiftcard 消耗 200 积分兑换邀请码(24 小时有效期),并将邀请码分享给希望加入 ntRRR 的朋友。 受服务器用户数量上限影响,本次开放名额有限,满额即止,先到先得。 系统将记录邀请人与受邀人之间的邀请关系。请将邀请码留给确有观影需求,并愿意共同维护良好使用环境的朋友。 感谢您一直以来对 ntRRR 的支持与认可。愿您出入平安、好运常伴! ntRRR Team @ntRRR_News
❤1
我能飞! 📢 分享频道:@Jsoo888 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo666_bot ☁️ 怕错过就常驻,圈内有资讯 · 时时有吃瓜
❤2👍1
領域展開 pinned a photo
💐💐💐开奖了💐💐💐 🎋夏天emby七夕活动 开奖了! 本期总参与人数: 525 1- 情 劫 获得:现金红包79.9元 谨祝中奖用户大吉大利万事顺意
❤1
不知道的还以为抽套套呢🤣
領域展開 pinned Deleted message
🎰 🎋夏天emby七夕活动 📮 抽奖条件: 🎫 加入-夏天 🎫 加入-EplayerX官方交流群 🎫 加入-領域展開 🎫 加入-集邮者,集合! 🎁 奖品内容: 现金红包79.9元 × 1 💡 活动说明: 🌈主题:您的甜蜜我买单! 🌈抽现金红包79.9元🌸! 七夕佳节由夏天10元硬盘服,助力您安全发挥+超长发挥😍 🌈夏天为您赞助安全套16只。 🔥另外在夏天买播epx播放器送emby哟! 防止脚本: 中奖用户需要在开奖前至少购买夏天0.66元的体验卡。并提前将订单截图发送至夏天频道私聊。否则中奖也不予兑奖。 8月11日之后购买的凭证均有效。播放器/天/月/年卡凭证均可以。中奖用户请在开奖后2小时内截图私聊夏天频道兑奖! 📅 开奖日期:(UTC+8) 2026年08月20日 21时21分21秒
領域展開 pinned Deleted message
🎉 瞬影 PRO & 瞬影 VIP|七夕特别活动 抽奖活动已开始! ━━━━━━━━━━━━━━ 截止时间: 2026年8月19日 20:02:27 UTC+8 🎁 奖品 · 瞬影PRO季卡 (开奖后卡密24小时有效) x3 · 瞬影VIP季卡 (开奖后24小时有效) x3 发布群组 · 瞬影EMBY交流群 参与要求 · 订阅 瞬影EMBY交流群 🔑 口令:瞬影七夕特别活动 活动详情 🎁 【七夕限时优惠】 🔥 季卡 / 年卡|77折 ⚡️ 瞬影 PRO 白名单|¥888 👑 瞬影 VIP + 瞬影 PRO 双白|¥1199 每邀请 5 位好友参与,提高中奖机率!
❤1
🚨 【Lunaris 告别说明】 Lunaris 决定,就在这个月底结束这一段旅程。 一路走来,很多事情已经交给了 AI,但真正做起来才发现,即使有了 AI,依然有许多细节需要一点点手动处理。 而 Lunaris 本身,确实是个有些懒的人。 慢慢地,他也意识到,这份“工作”或许并不适合自己。它没有带来想象中的快乐,反而渐渐变成了一件需要完成的事情。 所以,这一次,就到这里吧。 感谢一路以来遇见的每一个人,也感谢大家曾经陪 Lunaris 走过这一段路。 🌙 Lunaris 要离开了。 但夜空不会因此熄灭。 月亮离开以后,依然会有许多星星与你们同在。 愿大家往后的日子里,都能找到属于自己的那一片星空。 ✨ 💬来源:Lunaris 📢 分享频道:@Jsoo888 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo666_bot ☁️ 怕错过就常驻,圈内有资讯 · 时时有吃瓜
🍌1😭1
🎬 PanSave|网盘媒体自动化管理平台 自部署于 NAS · 家用服务器 · 云主机,打通 Telegram、榜单、豆瓣、Emby 与网盘,实现扫描、追更、求片、转存、补集、通知全流程自动化。 🔗 交流群: https://t.me/+E1aPeVBA2C01ODY1 📢 分享频道:@Jsoo888 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo666_bot ☁️ 怕错过就常驻,圈内有资讯 · 时时有吃瓜
❤1
Showing the 12 most recent of 50 posts we hold for @Jsoo888. 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.
Posts edited after publishing
@Jsoo888 edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 12 August 2026
- Most recent edit
- 18 August 2026
Forward network
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.
Mentions
Named by 3 registered channels — 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.
@Jsoo8888 · 6,78639 posts吃瓜前线
@Jsoo666 · 2,94119 posts茶百道
@Chapanda1 · 3,7726 posts垃圾存档
@embytg · 2,8343 posts小声逼逼
@me888888888888 · 50,3292 posts墨云阁通知频道
@moyungeyydsyyds · 13,7912 postsntRRR News
@ntRRR_News · 2,7332 posts保熟瓜棚🍉
@SureRipe · 2,8322 postsAlphaTV通知频道
@AlphaTVOverseaChannel · 11,5811 post未知艺术家™
@bittermoontv · 5,5561 postOnyra
@embysuper · 3,2621 postEplayerX官方交流群
@EplayerXGroup · 9,1021 postGousen(EOOS 公益版)
@Gousen3 · 4,9851 post坤的🐔圈
@iKunloveee · 5251 post𝙻𝚒𝚋𝚛𝚊𝕏 𝙲𝚑𝚊𝚗𝚗𝚎𝚕
@inlogout · 2,7561 post非越媒体库 Chat
@lilililililiiilllll · 10,3411 post临境 Liminal
@Liminal_Emby · 8,6891 postNayovo
@nayovoy · 5,0041 post集邮者,集合!
@Petrichor_Embys_channel · 8,4211 post集邮者联盟
@Petrichor_Embys_chat · 6,2721 post星星的 Emby & 机场指南
@StarsNavigation · 13,3791 post瞬影EMBY交流群
@syemby · 5,7751 post小王的Emby二手交易网
@wEsq88GT1erk4MzNl · 1,5001 post柚子酱-(满1W人抽魔法猫家的 JK)
@youzi_max · 3,4671 post
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.
Handles this channel named that no longer answer
- Dead references
- 4
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 2
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@Jsoo888 named 4 handles 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 5 posts, 21 August 2026 – 26 August 2026 · confirmed gone 27 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 2 posts, 8 August 2026 – 9 August 2026 · confirmed gone 15 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 8 August 2026 – 10 August 2026
named in 2 posts, 8 August 2026 – 10 August 2026
Cite this entry
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“領域展開” (@Jsoo888), 8,580 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Jsoo888.
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.