谁有他的包
👍4

Channel
@wddk889
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
15,858subscribers
-410 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002431758496 |
|---|---|
| Type | Channel |
| Username | @wddk889 |
| Description | 售后/反馈/合作/500一个月广告 @YUYUMGUI 闲聊群:https://t.me/wddk8866 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/wddk889 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 13:43 | 15,858 | -24 |
| 30 Aug 2026, 11:08 | 15,882 | -10 |
| 29 Aug 2026, 10:26 | 15,892 | -87 |
| 28 Aug 2026, 09:12 | 15,979 | -61 |
| 27 Aug 2026, 11:55 | 16,040 | -17 |
| 26 Aug 2026, 13:17 | 16,057 | -14 |
| 25 Aug 2026, 10:24 | 16,071 | -7 |
| 24 Aug 2026, 07:13 | 16,078 | -28 |
| 22 Aug 2026, 16:55 | 16,106 | -22 |
| 21 Aug 2026, 09:27 | 16,128 | -6 |
| 20 Aug 2026, 10:45 | 16,134 | -14 |
| 19 Aug 2026, 12:52 | 16,148 | -1 |
| 18 Aug 2026, 10:34 | 16,149 | -9 |
| 17 Aug 2026, 09:56 | 16,158 | -16 |
| 15 Aug 2026, 19:56 | 16,174 | -16 |
| 14 Aug 2026, 09:38 | 16,190 | -22 |
| 13 Aug 2026, 00:33 | 16,212 | -18 |
| 12 Aug 2026, 02:08 | 16,230 | -13 |
| 10 Aug 2026, 05:02 | 16,243 | -25 |
| 9 Aug 2026, 05:16 | 16,268 | first reading |
40 posts held, back to 27 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 43 pagesof 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 27 of 31 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 40 (27 July 2026 – 31 August 2026) |
| Views total | 24,410 |
| Reactions total | 165 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 16:33 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 31 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
197 reactions across 33 posts, in 12 distinct kinds. The most used accounts for 52.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 104 | 52.8% | |
| 🤣 | 30 | 15.2% | |
| ❤ | 26 | 13.2% | |
| 🤡 | 13 | 6.60% | |
| 🤮 | 9 | 4.57% | |
| 👎 | 6 | 3.05% | |
| 🔥 | 3 | 1.52% | |
| 🍌 | 2 | 1.02% | |
| 🌚 | 1 | 0.508% | |
| 👏 | 1 | 0.508% | |
| 🤬 | 1 | 0.508% | |
| 🥰 | 1 | 0.508% |
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 34 of the 40 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 197reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 27 July 2026 to 31 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.
谁有他的包
👍4
三角洲的udp解密开源 仅供开发使用
👍5
谁有他的包发我一下
👍3👎1
我看这几天也没有稳定的辅助先不回归了
👍4
😃😀😃 我真不想多说了 还是用了市面上最好看的一套源码 DV作者的源码握在手里跟传家宝一样卖都不卖,还市面上最好看的源码 我真不行了 真的有源码悬浮窗都不改一下吗? 我真笑不活了 赶紧避雷柠檬内部。 真没想到DV破解版能活到现在
👍4❤2
抖音直播间 56322024981 去直播间公平 扣无敌暴龙兽 抠十遍截图找我进内部群
👍3
No One(001)测试中! 已彻底定位10年, 问题正在解决+排除特定功能测试。
❤2
卡密随便输
👍8👎4
👿NO One 客户轮次测试进度反馈! 具体细节如图↑ ⚠️个别客户反馈814日的包,今个也没有10年,那就加测! 正好今天是我们自己人测的 ,今晚和明天让客户测! 不要着急 不差这一天 也是对你们负责。 等内测结束,确认没问题了,No one 就放包放补偿。
👍6❤1👎1
No one 昨日账号测试,今日在线反馈。 满24小时,无追无封。 等待开发那边进一步沟通,再确定具体推包时间和补偿方案。
👍3
统帅又又又又回归了=独角兽
👍10🤮9
喜欢搞恶趣味主播 冲别人直播的 进一下 每天还有不定时红包
Showing the 12 most recent of 40 posts we hold for @wddk889. 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 — 634,039 of 1,629,372entries 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.
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.
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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“JOJO官方频道” (@wddk889), 15,858 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/wddk889.
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.