Channel
@jielongjs
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004463701137 |
|---|---|
| Type | Channel |
| Username | @jielongjs |
| Created | 2 August 2026 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jielongjs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 05:48 | 2 | no change |
| 8 Aug 2026, 15:30 | 2 | first reading |
7 posts held, back to 2 August 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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 7 (2 August 2026 – 5 August 2026) |
| Views total | 139 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 05:48 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 14 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.
## 公平性说明文案 关于红包扫雷金额分配的公平性说明 本机器人所有红包金额的分配均基于以下透明机制，确保绝对公平： 1. 随机切割法分配金额 每轮红包在创建时，系统使用"随机切割法"将总金额随机分成 5 份。具体做法是在 0~1 之间生成 4 个随机点，将总金额按比例切割。该算法保证：每一份金额完全随机、互不关联、且 5 份之和精确等于总金额。任何人均无法预知或操控某一份的具体金额。 2. 雷值仅与分位有关 是否"中雷"仅取决于领取金额的小数点后最后一位（即"分"位，例如 1.23 的尾数为 3）是否等于发包人设定的雷值（0-9）。尾数由随机切割自然产生，不可预测亦不可操控。 3. 抢包时纯随机选取 用户点击"领取红包"时，系统从剩余未领取的包中完全随机分配一份，不做任何倾向于某人的筛选。抢到雷包还是安全包，全凭运气。 4. 假用户与真人一视同仁 假用户同样走以上全部流程，无任何特殊待遇或作弊逻辑，仅作为活跃气氛的参…
扫雷有关用户领取红包金额随机分配的代码
扫雷有关雷值判定的代码
扫雷＆接龙有关领取金额的代码
红包扫雷玩法 红包命令 hbsl 10u 4 用户发出的红包个数固定为5个，发出10u，5个包，中雷尾数是4 若用户领取金额为0.04，则给发包者赔付发出金额的1.85倍，也就是18.5u
红包接龙玩法 发出的红包金额随机公平分配，参与者不足不会显示金额大小 参与者人数=红包个数时机器人显示领取金额，由金额最小的参与者自动发放下一个红包
Channel created
Showing the 7 most recent of 7 posts we hold for @jielongjs. 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 — 438,418 of 1,481,217entries 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“红包扫雷及红包接龙玩法” (@jielongjs), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/jielongjs.
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.