新鲜吃瓜速看,相关讨论链接如下: Pro Max Ultra版本03 https://notes.realme.com/s/JAQUUJG0x1D0_1 Pro Max Ultra版本03.1 https://notes.realme.com/s/lflwNauTzEbh_1 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
🤓1

Channel
@Jsoo666
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
2,955subscribers
+8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003783537464 |
|---|---|
| Type | Channel |
| Username | @Jsoo666 |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/Jsoo666 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 08:36 | 2,955 | +9 |
| 7 Aug 2026, 23:08 | 2,946 | -1 |
| 7 Aug 2026, 20:02 | 2,947 | no change |
| 7 Aug 2026, 19:32 | 2,947 | first reading |
20 posts held, back to 6 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 1 pageof 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. It is computed over the 4 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 July 2026 |
|---|---|
| Posts held | 20 (6 July 2026 – 30 July 2026) |
| Views total | 11,968 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 20:02 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.
25 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 36.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 36.0% | |
| 👍 | 4 | 16.0% | |
| 😁 | 2 | 8.00% | |
| 😎 | 2 | 8.00% | |
| 🤔 | 2 | 8.00% | |
| 🌭 | 1 | 4.00% | |
| 🍌 | 1 | 4.00% | |
| 🔥 | 1 | 4.00% | |
| 😱 | 1 | 4.00% | |
| 🤓 | 1 | 4.00% | |
| 🤣 | 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 12 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 25reactions 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 6 July 2026 to 30 July 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.
新鲜吃瓜速看,相关讨论链接如下: Pro Max Ultra版本03 https://notes.realme.com/s/JAQUUJG0x1D0_1 Pro Max Ultra版本03.1 https://notes.realme.com/s/lflwNauTzEbh_1 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
🤓1
新鲜吃瓜速看,相关讨论链接如下: Pro Max Ultra版本01 https://notes.realme.com/s/rxc8G1VRVs9Y_1 Pro Max Ultra版本02 https://notes.realme.com/s/FC0cFjJJVSCv_1 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
❤1
🍉 后续来了|剧情迎来反转? 就在双方争论持续发酵之际,事件又出现了新进展。 FK 在聊天中表示: “野草地还能给我开个白名单吗?其实看不看无所谓,主要是想集个邮。不能因为这个事情,就不给开了吧。” 该发言一出,不少围观群友直呼剧情反转。前脚还在激烈开喷,后脚却主动询问是否还能申请白名单,引发群内一片调侃,相关聊天截图也迅速传播。 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜
😁2😎2
🍉 FK、初恋公开对线 野草地删号事件持续发酵后,有频道发文称,野草地因外部压力删号,并提到疑似事件起因之一或与有人在相关群内发布其他 Emby 服 AFF 邀请链接有关。 随后,FK 在聊天中连续发表言论,并进行了较大范围的地图炮,引发群内热议。部分围观群友认为,其发言情绪较为激烈,攻击范围也相对较广。 对此,初恋 出面回应,否认曾针对 FK,并表示: “我什么时候挂过你?什么时候骂过你?别人骂你,跟我有什么关系?如果真是我在频道挂你、骂你,你直接拿出来。” FK 随后回应称,自己在腐竹明确表示不能发送 AFF 后便已停止发送,同时质疑开号流程拖延,称 “8-9号一直不给开号,像遛狗一样。” 对于“发布 AFF 就是在压力野草地”的说法,FK 表示并不认可,并回应: “发个 AFF 就叫压力?我什么时候攻击野草地了?我骂的是那些骂我的人,不是野草地。” 目前,双方仍各执一词,争论仍在持续。至于野草地删号的具体原…
❤1
新鲜吃瓜速看,相关讨论链接如下: https://t.me/guyushijie666/844 https://t.me/Jsoo8888/181983 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
新鲜吃瓜速看,相关讨论链接如下: https://telegram.me/MikudesuChannels/545 https://telegram.me/embytg/619 https://telegram.me/SureRipe/108 https://telegram.me/lezi111123/88 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
新鲜吃瓜速看,相关讨论链接如下: https://t.me/ShardCatDen/594679 https://t.me/SureRipe/107 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
新鲜吃瓜速看,相关讨论链接如下: https://t.me/IrisEmby_Group/454872 https://t.me/mobaishishuaige/904480 https://t.me/SureRipe/104 https://t.me/SureRipe/106 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
新鲜吃瓜速看,相关讨论链接如下: https://t.me/SureRipe/100 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
新鲜吃瓜速看,相关讨论链接如下: https://t.me/IrisEmby_Group/452385 https://t.me/IrisEmby_Group/452707 https://t.me/IrisEmby_Group/452874 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
新鲜吃瓜速看,相关讨论链接如下: https://t.me/ycdchannel/47002 https://t.me/ycdchannel/47941 https://t.me/ycdchannel/47956 https://t.me/ycdgroup/24 https://t.me/ycdchannel/49297 https://t.me/ycdchannel/49341 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
❤2🤔2
新鲜吃瓜速看,相关讨论链接如下: https://t.me/ShardCatDen/585027 https://t.me/Playfragments/679 https://t.me/IrisEmby_Group/451382 https://t.me/IrisEmby_Group/451539 https://t.me/embytg/569 📢 分享频道:@Jsoo888 🍉 吃瓜频道:@Jsoo666 👥 交流群:@Jsoo8888 📩 联系方式:@Jsoo888_bot ☁️ 想看资讯常驻分享,偏爱热闹移步吃瓜。
👍2🔥1
Showing the 12 most recent of 20 posts we hold for @Jsoo666. 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 — 414,932 of 1,176,613entries 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.
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 2 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.
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.
@Jsoo666 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.
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.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“吃瓜前线” (@Jsoo666), 2,955 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Jsoo666.
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.