Channel
@ywzlj777
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
736subscribers
+25 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003984964171 |
|---|---|
| Type | Channel |
| Username | @ywzlj777 |
| Created | Between 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/ywzlj777 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 84% 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.
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 word for word 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 |
|---|---|---|---|
| @yiwutongzhi/1186 Aug 2026, 09:28 UTC | @ywzlj777/268 · this entry6 Aug 2026, 09:28 UTC | 1.00 | under a minute |
| @yiwutongzhi/1246 Aug 2026, 15:59 UTC | @ywzlj777/271 · this entry6 Aug 2026, 15:59 UTC | 1.00 | under a minute |
| @yiwutongzhi/1277 Aug 2026, 03:06 UTC | @ywzlj777/273 · this entry7 Aug 2026, 03:06 UTC | 1.00 | under a minute |
| @yiwutongzhi/1357 Aug 2026, 15:59 UTC | @ywzlj777/275 · this entry7 Aug 2026, 15:59 UTC | 1.00 | under a minute |
| @yiwutongzhi/1378 Aug 2026, 01:51 UTC | @ywzlj777/277 · this entry8 Aug 2026, 01:51 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @yiwutongzhi | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–0) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 31 July 2026 to 8 August 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.
Across the whole group of 2, the earliest publisher we hold is @yiwutongzhi. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 8 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 07:58 | 736 | -8 |
| 6 Sept 2026, 21:57 | 744 | -11 |
| 30 Aug 2026, 01:37 | 755 | -5 |
| 23 Aug 2026, 00:23 | 760 | -18 |
| 16 Aug 2026, 01:55 | 778 | +57 |
| 8 Aug 2026, 09:56 | 721 | +10 |
| 8 Aug 2026, 02:17 | 711 | first reading |
20 posts held, back to 31 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 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 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 20 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 July 2026 to 8 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.
🎉 义乌丝足抓龙筋 @ywzlj 免单活动 🎁 奖品清单 • 399套餐免单券 × 1 🛡️ 参与条件 • 加入 金华义乌福利社 • 加入 义乌福利社-在榜老师 • 加入 江浙沪精选探花 • 加入 福利社-公告频道 • 加入 义乌丝足抓龙筋-龟责潮喷-前高开发-sm • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10撒币 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-09 23:59:00 📜 抽奖说明 免单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告。 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
✨ 命运揭晓时刻 ✨ 义乌丝足抓龙筋 @ywzlj 免单活动 开奖了 抽奖人数：130，抽奖号数：623 1. ikarous【祝福57次】 中得：399套餐免单券 抽奖说明： 单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告 🔍 杜绝黑幕，点击查看本次开奖全程验证
🎉 义乌丝足抓龙筋 @ywzlj 免单活动 🎁 奖品清单 • 399套餐免单券 × 1 🛡️ 参与条件 • 加入 金华义乌福利社 • 加入 义乌福利社-在榜老师 • 加入 江浙沪精选探花 • 加入 福利社-公告频道 • 加入 义乌丝足抓龙筋-龟责潮喷-前高开发-sm • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10撒币 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-08 23:59:00 📜 抽奖说明 免单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告。 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
✨ 命运揭晓时刻 ✨ 义乌丝足抓龙筋 @ywzlj 免单活动 开奖了 抽奖人数：162，抽奖号数：473 1. 可爱的弟弟（i彤彤）【祝福12次】 中得：399套餐免单券 抽奖说明： 单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告 🔍 杜绝黑幕，点击查看本次开奖全程验证
【金华义乌福利社】 【评价时间】：2026-08-06 【老师名字】：义乌丝足抓龙筋 【验证留名】：-我不是雪王（没错！粒儿第一认定的狗） 【颜值】： 【身材】： 【服务】： 【态度】： 【过程描述】： 白嫖年年有 今天终于轮到我啊 都给我去抓龙筋 这老师按摩的是真舒服啊 特别是按被那会儿 给我以为牛马生活变得僵硬的腰都揉开了 热热的精油抹在背上在加上老师的手法按摩 真的好舒服 索拉的spa跟这比都差点意思啊 按完背正面的手法也是非常之哇塞 感觉在经历了几起几落之后我的小雪王都变大了一些 在今天的大战之后来这么一下按摩真的给我按爽了啊 下次再出击之前还得来按按 让我变成桩机
❤1
🎉 义乌丝足抓龙筋 @ywzlj 免单活动 🎁 奖品清单 • 399套餐免单券 × 1 🛡️ 参与条件 • 加入 金华义乌福利社 • 加入 义乌福利社-在榜老师 • 加入 江浙沪精选探花 • 加入 福利社-公告频道 • 加入 义乌丝足抓龙筋-龟责潮喷-前高开发-sm • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10撒币 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-07 23:59:00 📜 抽奖说明 单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
✨ 命运揭晓时刻 ✨ 义乌丝足抓龙筋 @ywzlj 免单活动 开奖了 抽奖人数：138，抽奖号数：417 1. 阔澜（dylan）【祝福55次】 中得：399套餐免单券 抽奖说明： 免单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告 🔍 杜绝黑幕，点击查看本次开奖全程验证
🎉 义乌丝足抓龙筋 @ywzlj 免单活动 🎁 奖品清单 • 399套餐免单券 × 1 🛡️ 参与条件 • 加入 金华义乌福利社 • 加入 义乌福利社-在榜老师 • 加入 江浙沪精选探花 • 加入 福利社-公告频道 • 加入 义乌丝足抓龙筋-龟责潮喷-前高开发-sm • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10撒币 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-06 23:59:00 📜 抽奖说明 单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
✨ 命运揭晓时刻 ✨ 义乌丝足抓龙筋 @ywzlj 免单活动 开奖了 抽奖人数：170，抽奖号数：398 1. 泽塔贝利亚黄昏 中得：399套餐免单券 抽奖说明： 免单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告。 🔍 杜绝黑幕，点击查看本次开奖全程验证
【金华义乌福利社】 【评价时间】：2026-08-04 【老师名字】：义乌丝足抓龙筋 【验证留名】：匿名 【颜值】： 【身材】：老师说b＋，我感觉有c 【服务】： 【态度】： 【过程描述】： 刚中了个白嫖券，第二天就联系了时间，地址很好找，进门看到老师一身人妻装扮，大胸诱惑着我，洗澡后就是开始服务，穿着什么红外线的东西就是头部按摩，腿部按摩，胸部按摩都有，接着前列腺按摩，我不太喜欢就不要了，直接到抓龙筋，很奇妙的体验，没体验的可以试试，然后老师和我一边聊天一边抓，可惜老师只让我摸腿，只能看着大胸心里yy了，后面就是做完服务拿着老师的水就跑路了
🎉 义乌丝足抓龙筋 @ywzlj 免单活动 🎁 奖品清单 • 399套餐免单券 × 1 🛡️ 参与条件 • 加入 金华义乌福利社 • 加入 义乌福利社-在榜老师 • 加入 江浙沪精选探花 • 加入 福利社-公告频道 • 加入 义乌丝足抓龙筋-龟责潮喷-前高开发-sm • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10撒币 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-05 23:59:00 📜 抽奖说明 免单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告 ✨ 愿命运之剑指引你们前行，直至胜利之光照耀每一个人。
✨ 命运揭晓时刻 ✨ 义乌丝足抓龙筋 @ywzlj 免单活动！ 开奖了 抽奖人数：157，抽奖号数：452 1. -我不是雪王【祝福20次】 中得：399套餐免单券 抽奖说明： 免单奖券有效期3天，不得转让，过期作废，中奖后出击需写反馈报告。 🔍 杜绝黑幕，点击查看本次开奖全程验证
Showing the 12 most recent of 20 posts we hold for @ywzlj777. 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.
Named by 2 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“义乌丝足抓龙筋-龟责潮喷-前高开发-sm” (@ywzlj777), 736 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/ywzlj777.
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.