话术大群已经恢复 : @xinhaihuashu 新海唯一聊天大群: @xinhai 业务员: @paimian @qqq33 @qqq55
❤1

Channel
@dongfang888888888
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,226subscribers
-38 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001833745603 |
|---|---|
| Type | Channel |
| Username | @dongfang888888888 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/dongfang888888888 |
Hacking & security — 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 82% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 03:36 | 1,226 | -4 |
| 14 Sept 2026, 18:21 | 1,230 | -11 |
| 11 Sept 2026, 06:18 | 1,241 | -8 |
| 6 Sept 2026, 09:56 | 1,249 | -5 |
| 1 Sept 2026, 23:54 | 1,254 | +2 |
| 30 Aug 2026, 09:12 | 1,252 | +2 |
| 27 Aug 2026, 06:17 | 1,250 | -3 |
| 23 Aug 2026, 22:17 | 1,253 | -5 |
| 20 Aug 2026, 11:55 | 1,258 | -4 |
| 17 Aug 2026, 17:07 | 1,262 | -1 |
| 14 Aug 2026, 21:47 | 1,263 | +3 |
| 11 Aug 2026, 18:24 | 1,260 | -5 |
| 8 Aug 2026, 08:46 | 1,265 | +1 |
| 7 Aug 2026, 11:18 | 1,264 | first reading |
12 posts held, back to 9 May 2024 — 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 12 October 2025. An engagement rate over an empty window would be a number about nothing.
46 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 60.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 28 | 60.9% | |
| 👍 | 8 | 17.4% | |
| 👏 | 4 | 8.70% | |
| 👌 | 2 | 4.35% | |
| 🔥 | 2 | 4.35% | |
| 🥰 | 2 | 4.35% |
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 11 of the 12 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 9 May 2024 to 12 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
话术大群已经恢复 : @xinhaihuashu 新海唯一聊天大群: @xinhai 业务员: @paimian @qqq33 @qqq55
❤1
诚信千秋万代,人走钱还在 无人扶你凌云志,我司送你万两金 恭喜新中介边角料结账成功,支持全网担保专群专押 😀😀😀😀 排面 @paimian 😀😀😀😀 老表 @qqq33 😀😀😀😀 龙哥 @svip466 😀😀😀😀 星哥 @qqq55 😀😀😀😀 小金 @xinhai333
❤4
全网劳务上押20000U 欢迎中介合作 上车等于99.9%收钱。 有人发资料预约位置 缅甸公司大量要人,价格不是最高,但是最靠谱。 新海劳务总群: @xinhai 新海劳务二群: @xinhailaowu 中介对接:排面 @paimian 中介对接:龙哥 @koukuan 中介对接:老表 @qqq33 求职联系人事土豆 @xinhai3 新海公司直招招聘群: @xinhaizp 结账信誉截图: @TKJTXY 劳务中介话术: @laowuhuashu 东南亚大事件: @xinhaib 资源共享搜索: @xinhaiz 福利视频导航: @xinhaid
❤3👍1
东方集团所有大群打包出售给我们新海,所有以前业务和我们无关,大量收出国人头 全网劳务上押20000U 欢迎中介合作 上人联系: @paimian @TKJTLG 新海商贸永久聊天群: @xinhai 新海商贸结账信誉群: @TKJTXY 所有交易支持专群专押 上车等于99.9%收钱。 有人发资料预约位置
❤5👍3
Photo, posted without a caption
❤2
建设测卡,空转499000(给其他人直接转账49万看提示余额不足还是什么) 不要钱包充值,不要龙支付充值,不要空充 会分级。其他卡验卡方式不变互相通知
❤4
更新验卡教程完毕,更新了市面上常见地区银行,有其他银行资料可以补充给 @VIPDFJT 大家一起把验卡频道补充完整 大家一起做大做强 最主要得方便大家验卡
❤6👍4👏4👌2🔥2🥰2
方法1:微信搜索拼多多-进入-搜索黄金 筛选—价格选择49999购买 然后选择测试的银行卡付款即可 余额不足为正常 方法2:方法:微信-我的-服务-理财通余额+ -立即转入-空充49999 ‼️‼️禁止微信/支付宝/拼多多空冲
❤2
#顺德农商 模版
#深圳农商
#绍兴银行 (要看非柜面)模版
#河北银行
❤1
Showing the 12 most recent of 12 posts we hold for @dongfang888888888. 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.
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 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.
@dongfang888888888 named 7 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“新海商贸-卡商验卡教程” (@dongfang888888888), 1,226 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/dongfang888888888.
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.