露娜红皮😍

Channel
走丢三角洲数据号
@ZDSJHNB6
On this record: Topic · Previous handles · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,142subscribers
+1 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003841085800 |
|---|---|
| Type | Channel |
| Username | @ZDSJHNB6 |
| Created | 2 March 2026 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/ZDSJHNB6 |
Topic
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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.
Previous handles
@ZDSJHNB6 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 15 August 2026 – 15 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 12:07 | 1,142 | +110 |
| 16 Nov 2026, 11:22 | 1,032 | no change |
| 16 Nov 2026, 10:47 | 1,032 | -118 |
| 15 Sept 2026, 08:01 | 1,150 | +13 |
| 11 Sept 2026, 12:39 | 1,137 | -6 |
| 6 Sept 2026, 21:22 | 1,143 | -3 |
| 1 Sept 2026, 23:15 | 1,146 | -4 |
| 30 Aug 2026, 03:14 | 1,150 | -4 |
| 26 Aug 2026, 20:53 | 1,154 | -1 |
| 23 Aug 2026, 12:46 | 1,155 | +6 |
| 20 Aug 2026, 01:06 | 1,149 | +9 |
| 16 Aug 2026, 17:23 | 1,140 | -1 |
| 15 Aug 2026, 11:00 | 1,141 | no change |
| 15 Aug 2026, 10:47 | 1,141 | first reading |
Engagement
14 posts held, back to 2 March 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 2 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 67.6%
- avg views ÷ 1,142 subscribers
- Avg views / post
- 772
- 5 posts measured
- Reaction rate
- 0.054%
- reactions ÷ views · ER floor
- Posts in window
- 5
- of 14 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 1 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 14 (2 March 2026 – 16 November 2026) |
| Views total | 3,861 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 11:22 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
14 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 71.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 10 | 71.4% | |
| ❤ | 4 | 28.6% |
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 6 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 14 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 March 2026 to 16 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.
Recent posts
Telegram’s own ‘edited’ marker: 3 of 5 posts held from the last 30 days (60.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).
三角洲数据号库存已拉满认准下单即可🔥 客服在线 持续售后中🫰 提号点我跳转 ❤️TG售后:@ZDNB661✅
三角洲数据号库存给你们拉满了认准走丢数据号即可😄
三角洲数据号上架库存了,质量下一单以后就会认准我们后续我们会降低价格提高质量给你们更高的体验🔥
开挂没号玩? 不敢用自己大号开挂? 害怕😨被封? 想体验皮肤? 想要游戏资产多的号? 想免费玩号? ❤️走丢高质量三角洲数据号源头自营✔️ ➡️😃😃退游号😃😃高质量号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 ➡️全网最质量最低价格 最强售后😒 🥇一年诚信经营,三年售后兜底🔥 😙😍😗😋😝🙃😜🤨😜 👍👍 ❤️主推-购买地址: https://shop.bromk.cn/shop/NRU90L5J 全网最质量最有性价比的三角洲数据号(对比全网价格)🔥 ❤️走丢数据号官方频道:https://t.me/ZDSJHNB6 ✅售后客服: @ZDNB661
👍2
❤️Sky内核重磅回归三角洲无延迟算法解密🔥 1.全图绘制雷达 2.全新无延迟坐标解密 3.不修改任何内存无10年1/3/7 4.进入游戏开启解密即可稳定奔放 5.陀螺仪触摸自瞄自选 真正的算法解密内核,绝不动内存,稳定航天绝密乱杀 物资显示,过滤高价值物资,精确寻包 自瞄枪枪锁直接化身洗头师傅(漏打)不日墙 进入游戏开启解密即可不遁地奔放 🥰卡网下单: 走丢.love https://816.jytos.cn/shop/K79M9WSS 欢迎各实力售卡批卡,诚招代理,利润充足(永不跑路) Sky对接码:ZDNB 816同商户对接就是核心代理利润拉满🔥 Sky官方频道:https://t.me/ZDSJZNB 👍客服售后: https://t.me/ZDNB661 24小时在线随时联系客服解决售后问题 (解密失败的直接一对一售后解决) ➡️点我查看白嫖最新dock解密内核卡密任务‼️
❤2👍2
Signed 走丢OvO
Photo, posted without a caption
👍2
Signed 走丢OvO
Photo, posted without a caption
👍2
Signed 走丢OvO
强制防录屏没办法
👍2
Signed 走丢OvO
Photo, posted without a caption
Signed 走丢OvO
真的肯定呀,主播太好用了,还有这个漏打
Signed 走丢OvO
Photo, posted without a caption
❤2
Signed 走丢OvO
Showing the 12 most recent of 14 posts we hold for @ZDSJHNB6. 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.
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 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.
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 19 November 2026 — this entry's latest reading, not the date you are reading this.
“走丢三角洲数据号” (@ZDSJHNB6), 1,142 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/ZDSJHNB6.
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.