1 Aug 2026, 05:55 UTC84 views7 reactionsread 7 August 2026
Photo
破案了，黄片哥在 IFS 前两天单人起八是因为它上周来试图扫荡萝天王地盘失败用掉了太多八炸 虽然 totoro625 把一切手段都用上了甚至当场狂扫描激活薯条来补仓，但还是没能把支点打下来 你龙猫也是个一直待上海群里的老登了，难道以为魔绿会感谢你打掉几个蓝八吗？魔绿只会记住你害得它们又少了十个坡，再来再删
🤣6😁1
Channel
萝天王皇家格斗学院。～绝赞爆揍魔绿中～
@ENLoot
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
225subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001491892031 |
|---|---|
| Type | Channel |
| Username | @ENLoot |
| Description | 在？魔绿孤儿进来挨锤 本频道基于实用主义，讨论分享如何有效打击魔绿作弊玩家及相关支持者，带有主观与偏见 本频道所提及的Enlightened、Resistance、Agent、“启蒙军”、“绿军”、“蓝军”、“抵抗军”、“特工”均为在线手游Ingress中的虚拟元素内容和游戏设定，与现实世界无任何关联，不组织和讨论任何现实世界中与游戏内容无关或是违反当地法律法规的活动 |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ENLoot |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 07:32 | 225 | no change |
| 7 Aug 2026, 07:18 | 225 | first reading |
Engagement
4 posts held, back to 16 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 · 30 days
- 68.4%
- avg views ÷ 225 subscribers
- Avg views / post
- 154
- 4 posts measured
- Reaction rate
- 3.04%
- reactions ÷ views · ER floor
- Posts in window
- 4
- of 4 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 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 August 2026 |
|---|---|
| Posts held | 4 (16 July 2026 – 1 August 2026) |
| Views total | 616 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 07:32 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.
What this channel posts
- Photos
- ≈2,010
- Videos
- ≈41
- Links
- ≈438
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
7 reactions across 1 post, in 2 distinct kinds. The most used accounts for 85.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 6 | 85.7% | |
| 😁 | 1 | 14.3% |
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 2 of the 4 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 16 July 2026 to 1 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
27 Jul 2026, 10:15 UTC146 views0 reactionsread 7 August 2026
Photo
见过连field，见过连多重，见过连高级复杂多重，那你见过切小号切到轨迹都能连出field的吗？ 无论台风还是酷暑，123都一如既往的用无数个小号为浦西绿军撑起一片天；从淮海中路到南京西路，从雕塑公园到复兴公园……这无缝衔接的掏手机大作战别说它玩得累，我光看地图都看累了，哪哪都是它，简直无处不在。还有xma的时候估计就摆一架子十台手机开连点器摁冲电 但是2026了，没人买这破游戏的账号，戴老板练这么多号毫无收益，还开小号去青浦IFS也够闲的。但问题是练成16级还是因为怕被封号甚至连床坡都不敢升，整天装观光游客街溜子，又不氪金，该暴死照样暴死
17 Jul 2026, 12:52 UTC204 viewsread 7 August 2026
玉带桥三个字让人不禁想起…… https://t.me/ShenjingRain/896
16 Jul 2026, 04:35 UTC182 viewsread 7 August 2026
Photo
随着两位蓝军玩家被色魔骚扰和网上侮辱+绿水雨知情不报纵容包庇而逼退游后，色魔是越来越嚣张了，都在工作日来我这报到了 但它害怕被举报而不敢现场掏桶，晒着36度的阳光炸了两小时也没炸下来，毒个坡就逃走了，按绿水雨的话来说：这人怎么这么废 按照惯例，送它十个假坡飞天~ 其实玩家不用害怕这种嘴上黄腔+线下跟踪骚扰的变态，如果打坡时遇到攻击性冒犯和恶意尾随，很容易让它承担代价，我就简单提示一下： 1. 在正常的工作时间出门以违反治安管理处罚法的方式攻击其他人，或侵犯他人名誉权，公司需要承担连带责任 2. telegram 社群和频道消息，都可以在上海的各大公证处正常进行证据保全工作作为中国大陆诉讼案件的证据用 3. 如果它对你实施暴力行为，一巴掌至少可赔一狗，考虑到它骑电动车容易逃窜，你可以直接抢下其手机后报警 剩下的司法流程走一遍就熟悉了
Showing the 4 most recent of 4 posts we hold for @ENLoot. 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
Citation-graph rank — 393,275 of 1,183,361entries 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.
Forward network
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.
Mentions
Named by 6 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“萝天王皇家格斗学院。～绝赞爆揍魔绿中～” (@ENLoot), 225 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/ENLoot.
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.