名字:#诗涵 身高:155 位置:#义乌 #福田 课费:#800p #1600pp 联系:@shihanm67890 标签:#嫩妹 #舌吻 #六九
❤2🔥1

Channel
@yiwuzhiyuanzhe
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
31,195subscribers
+13,526 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002471758486 |
|---|---|
| Type | Channel |
| Username | @yiwuzhiyuanzhe |
| Description | 联系管理 @Yiwudhangmaobot 义乌主群 @yiwuhui 老师报告 @yiwubaogao |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 58 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/yiwuzhiyuanzhe |
Giveaways & airdrops — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @ywsm2/2616 Aug 2026, 10:55 UTC | @yiwuzhiyuanzhe/4905 · this entry16 Aug 2026, 10:55 UTC | 1.00 | under a minute |
| @ywsm2/16261 Nov 2026, 15:22 UTC | @yiwuzhiyuanzhe/6370 · this entry1 Nov 2026, 15:22 UTC | 1.00 | under a minute |
| @ywsm2/16622 Nov 2026, 06:06 UTC | @yiwuzhiyuanzhe/6377 · this entry2 Nov 2026, 06:06 UTC | 1.00 | under a minute |
| @ywsm2/16642 Nov 2026, 06:24 UTC | @yiwuzhiyuanzhe/6379 · this entry2 Nov 2026, 06:24 UTC | 1.00 | under a minute |
| @yiwuzhiyuanzhe/6392 · this entry2 Nov 2026, 12:44 UTC | @ywsm2/16812 Nov 2026, 12:45 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ywsm2 | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 141 comparable posts for this entry, running 13 August 2026 to 3 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the key clone_source, last confirmed 18 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 13:48 | 31,195 | +477 |
| 14 Nov 2026, 11:17 | 30,718 | +654 |
| 11 Nov 2026, 09:40 | 30,064 | +357 |
| 9 Nov 2026, 14:51 | 29,707 | +207 |
| 8 Nov 2026, 05:20 | 29,500 | +258 |
| 6 Nov 2026, 23:08 | 29,242 | +122 |
| 6 Nov 2026, 00:11 | 29,120 | +175 |
| 4 Nov 2026, 22:19 | 28,945 | +211 |
| 4 Nov 2026, 01:29 | 28,734 | +141 |
| 3 Nov 2026, 03:20 | 28,593 | +149 |
| 2 Nov 2026, 06:10 | 28,444 | +175 |
| 1 Nov 2026, 07:06 | 28,269 | +228 |
| 31 Oct 2026, 05:20 | 28,041 | +161 |
| 30 Oct 2026, 06:07 | 27,880 | +185 |
| 29 Oct 2026, 06:44 | 27,695 | +299 |
| 28 Oct 2026, 03:14 | 27,396 | +196 |
| 27 Oct 2026, 06:11 | 27,200 | +174 |
| 26 Oct 2026, 03:56 | 27,026 | +235 |
| 25 Oct 2026, 03:57 | 26,791 | +306 |
| 24 Oct 2026, 03:20 | 26,485 | first reading |
261 posts held, back to 13 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 116 pages of 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 26 of 118 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 November 2026 |
|---|---|
| Posts held | 261 (13 August 2026 – 8 November 2026) |
| Views total | 54,552 |
| Reactions total | 21 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 03:53 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 18 November 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 67 videos 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.
54 reactions across 44 posts, in 4 distinct kinds. The most used accounts for 88.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 48 | 88.9% | |
| 👍 | 3 | 5.56% | |
| 👏 | 2 | 3.70% | |
| 🔥 | 1 | 1.85% |
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 66 of the 261 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 261 most recent posts we hold, published 13 August 2026 to 8 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.
Telegram’s own ‘edited’ marker: 5 of 118 posts held from the last 30 days (4.24%) 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).
名字:#诗涵 身高:155 位置:#义乌 #福田 课费:#800p #1600pp 联系:@shihanm67890 标签:#嫩妹 #舌吻 #六九
❤2🔥1
名字:#噜噜 身高:160 位置:#义乌 课费:#1000p #1800pp 联系:@luluya777 标签:#嫩妹 #舌吻 #六九
名字:#小蛇 身高:163 位置:#义乌 #福田 课费:#700p 联系:@xiaoshe008 标签:#嫩妹 #舌吻 #吞精 #颜射 #口爆 #SM 工兵一名下午两点发放
❤2👍1
瑶瑶 @daiyaoyao181818 今日优惠 P优惠100 ×2 PP优惠200 ×2 需要私信老师
小美 @xiaomei32151 今日优惠 通用优惠券200元×2 私信老师领取
✨ 命运揭晓时刻 ✨ 可可优惠券福利 开奖了 抽奖人数:33,抽奖号数:50 1. DavidJohnson 中得:100优惠券(优惠后仅300p) 抽奖说明: 禁止注水!! 优惠券有效期7天。 半价、白嫖有效期5天。 必须出报告,不出报告永久取消中奖资格! (超过中奖实效约课老师有权取消中奖名额、老师原因可延续!) 中奖联系 @lulu1314aa 🔍 杜绝黑幕,点击查看本次开奖全程验证
名字:#葱花宝宝 身高:163 位置:#义乌 课费:#800p #1600pp 联系:@Tthaoke 标签:#嫩妹 #六九 #舌吻
❤1
名字:#安然 身高:168 位置:#义乌 课费:#800p #1500pp 联系: @anran60 标签:#嫩妹 #六九 #舌吻 工兵两名下午两点发放
❤1
🔴义乌首家高端莞式海选SPA🔴 新项目新团队励志走向义乌巅峰spa店 💯义乌旗舰店💯网红店 SPA🔵聘各店之红牌,铸就本店巅峰颜值,实体口碑店(颜控首选)👍 ✈️✈️海选(60分钟全裸,全裸) 【服务模式】全裸 全场海选模式:每天出勤10➕👙各类高颜值,极品嫩菜,带您体验前所未有的视觉盛宴🫠 🔮 主打高颜值🔮服务一流。 💰新店开业特价 3️⃣9️⃣9️⃣ 🎼劲爆来袭 🎼劲爆来袭 ♥️独立浴室✨私密性强✨高质量服务 😀致力打造SPA届的巅峰、理想天堂圣地🖤 【温馨提示】 ♥️无套路、不办卡、没有任何隐形消费! 先体验后买单,用心做口碑♥️ 性价比天花板,五星级享受,灵魂最终的归宿☂️ 💯安全💯稳定💯可靠 电话:17879310387 预约电报:@Axmyydskk 机器人双向:@ximujiqiren_bot QQ:2782321084 欢迎进入交流群:https://…
❤1
✨ 命运揭晓时刻 ✨ 小师妹半价活动 开奖了 抽奖人数:239,抽奖号数:440 1. 仓鼠(i小师妹)【祝福53次】 中得:单p半价卷 抽奖说明: 禁止注水!! 优惠券有效期7天。 半价、白嫖有效期5天。 必须出报告,不出报告永久取消中奖资格! (超过中奖实效约课老师有权取消中奖名额、老师原因可延续!) 中奖联系 @xiaoyiyimm66 🔍 杜绝黑幕,点击查看本次开奖全程验证
泡芙 @paofu66689 今日优惠 单p优惠两张 需要私信老师
七七 @qiqi77788999 今日优惠 单p优惠两张!
❤1
Showing the 12 most recent of 261 posts we hold for @yiwuzhiyuanzhe. 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.
We recorded 4 posts on @yiwuzhiyuanzhe as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 16 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.
@yiwuzhiyuanzhe named 1 handle 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“义乌商贸协会榜单” (@yiwuzhiyuanzhe), 31,195 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/yiwuzhiyuanzhe.
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.