Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳最全娱乐资源【杰尼龟】

Channel

深圳最全娱乐资源【杰尼龟】

@szylzy1

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

27,648subscribers

-23 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002200871867
TypeChannel
Username@szylzy1
Description🤙本群有全深圳最齐全的娱乐资源! 😎在深圳有这一个群就够了! 龟村客服热线: @szjngbot 聊天吹水群: @szjngcsb
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held68
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/szylzy1

Topic

Adult — 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 86% 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.

Observations

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.

Content that also appears on other registered channels

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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@szylzy1/23236 · this entry1 Oct 2026, 13:29 UTC@lotterynav/278082 Oct 2026, 15:58 UTC1.0026 hours
@szylzy1/24871 · this entry30 Oct 2026, 11:55 UTC@lotterynav/3047431 Oct 2026, 16:47 UTC1.0029 hours
@szylzy1/25449 · this entry11 Nov 2026, 07:54 UTC@lotterynav/3148811 Nov 2026, 16:09 UTC1.008.3 hours
@szylzy1/25657 · this entry16 Nov 2026, 09:03 UTC@lotterynav/3190216 Nov 2026, 14:30 UTC1.005.5 hours
@lotterynav/2676818 Sept 2026, 06:13 UTC@szylzy1/23236 · this entry1 Oct 2026, 13:29 UTC0.8813 days
@lotterynav/278082 Oct 2026, 15:58 UTC@szylzy1/23648 · this entry7 Oct 2026, 10:06 UTC0.885 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@lotterynav6 (6/6 hand-verifiable sample passed)0.9628 hoursthis entry (4–2)

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. 2 of the 2 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 206 comparable posts for this entry, running 6 August 2026 to 16 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_source, last confirmed 17 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.

Growth

25,18227,86726,524.527,6486 August 202616 November 2026
68 measurements spanning 102 days, net -23. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 24,779–28,270 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 68
Measured (UTC)SubscribersChange
16 Nov 2026, 22:1627,648-7
13 Nov 2026, 14:4927,655+61
11 Nov 2026, 01:2727,594+18
9 Nov 2026, 14:0927,576+96
8 Nov 2026, 03:1927,480+42
6 Nov 2026, 22:0727,438+3
5 Nov 2026, 20:5927,435-16
4 Nov 2026, 18:0127,451-19
3 Nov 2026, 16:3627,470+32
2 Nov 2026, 14:3027,438+32
1 Nov 2026, 14:4727,406+26
31 Oct 2026, 17:3527,380+34
30 Oct 2026, 17:2927,346+12
29 Oct 2026, 13:5127,334+9
28 Oct 2026, 12:5927,325+32
27 Oct 2026, 13:4027,293+61
26 Oct 2026, 13:5127,232+55
25 Oct 2026, 11:4527,177+25
24 Oct 2026, 14:2127,152+26
23 Oct 2026, 17:1727,126first reading

Engagement

561 posts held, back to 6 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 262 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.87%
avg views ÷ 27,648 subscribers
Avg views / post
241
188 posts measured
Reaction rate
0.248%
reactions ÷ views · ER floor
Posts in window
188
of 561 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 30 of 188 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held561 (6 August 2026 – 17 November 2026)
Views total45,246
Reactions total26
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 11:50 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.

What this channel posts

Photos
510
Videos
63
Links
139

Lifetime counters from Telegram’s own channel header, read 17 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.

Video runtime
33m 21s
Average length
11s

Measured directly from 181 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.

Reaction mix

108 reactions across 70 posts, in 5 distinct kinds. The most used accounts for 68.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7468.5%
👍2725.0%
💯32.78%
👏21.85%
🥰21.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 97 of the 561 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 108 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 561 most recent posts we hold, published 6 August 2026 to 17 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: 31 of 188 posts held from the last 30 days (16.5%) 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).

17 Nov 2026, 11:36 UTC21 viewsread 17 November 2026

🍬🍬🍬今日出勤商-11月17日🍬🍬🍬 【600以下】:玲玲-南山区 | 雯雯-宝安区 | 正阳-南山区 | 姜姜-龙华区 | 皇室姐妹-光明区 | 陈兮 #抓龙筋-南山区 | 陈思琪-福田区 【600-800】:小e-南山区 | 卡西-宝安区 | 凌儿-南山区 【800-1200】:小雨-宝安区 | 维维-宝安区 | 点点-龙岗区 | 瑶瑶-宝安区 | 土豆-龙岗区 | 脱脱-南山区 【1200-1500】:宝儿-南山区 | 安妮-南山区 | 菲儿-南山区 | 小丸子-福田区 | 柚柚-南山区 | 伊依-南山区 | 悦悦-南山区 | 苡沫-南山区 | 蕊蕊-南山区 | 上官婉儿-南山区 | 玥玥-罗湖区 | 乔熙-南山区 | 桃子-福田区 | 锦汐-南山区 | 佳佳-龙岗区 | 橙子-龙华区 | 恬恬-南山区 | 小柏芝-南山区 | 甜妹兔-南山区 | 源源-南山区 | UU-南山区 | 牛奶-南山区 | 沐雅-南山区…

16 Nov 2026, 23:35 UTC11 viewsread 16 November 2026

🍬🍬🍬今日出勤商-11月17日🍬🍬🍬 【600以下】:玲玲-南山区 | 陈兮 #抓龙筋-南山区 | 陈思琪-福田区 【600-800】:凌儿-南山区 【800-1200】:点点-龙岗区 【1200-1500】:宝儿-南山区 | 菲儿-南山区 | 小丸子-福田区 | 柚柚-南山区 | 悦悦-南山区 | 苡沫-南山区 | 蕊蕊-南山区 | 上官婉儿-南山区 | 桃子-福田区 | 佳佳-龙岗区 | 橙子-龙华区 | 小柏芝-南山区 | 源源-南山区 | UU-南山区 | 小鱼-南山区 | 刘苡扉-南山区 | 护士-南山区 【1500以上】:王建国-南山区

16 Nov 2026, 16:28 UTC417 viewsread 17 November 2026
Photo

🆔 名字:刘富贵 📍 区域:#南山区 💰 价格:#1300P 🚀 私聊:@Lfg1314a 💬 报告:点击查看报告 🌍 定位:点击查看定位 💎 特色:#嫩妹 #舌吻 #胸推 #上门

16 Nov 2026, 11:31 UTC25 views0 reactionsread 16 November 2026

🍬🍬🍬今日出勤商-11月16日🍬🍬🍬 【600以下】:玲玲-南山区 | 娇娇-宝安区 | 雯雯-宝安区 | 正阳-南山区 | 糖糖-龙华区 | 姜姜-龙华区 | 朱朱-南山区 | 皇室姐妹-光明区 | 陈兮 #抓龙筋-南山区 | 陈思琪-福田区 【600-800】:小竹子-南山区 | 小e-南山区 | 凌儿-南山区 【800-1200】:点点-龙华区 | 小雨-宝安区 | 维维-宝安区 | 点点-龙岗区 | 土豆-龙岗区 | 脱脱-南山区 【1200-1500】:兰亭宝宝-南山区 | 宝儿-南山区 | 安妮-南山区 | 菲儿-南山区 | 小丸子-福田区 | 彤彤-南山区 | 柚柚-南山区 | 伊依-南山区 | 悦悦-南山区 | 刘富贵-南山区 | 苡沫-南山区 | 蕊蕊-南山区 | 上官婉儿-南山区 | 玥玥-罗湖区 | 桃子-福田区 | 锦汐-南山区 | 佳佳-龙岗区 | 橙子-龙华区 | 恬恬-南山区 | 沁沁-宝…

16 Nov 2026, 09:03 UTC457 viewsread 17 November 2026
Photo

🎰 杰尼龟(@jngsz)无标题‼️ 兑奖找唯一客服 @szjngbot 📮 参与条件: 🎫 加入-深圳杰尼龟修车 └ 🔑 发送口令﹝深圳杰尼龟﹞ 🎫 加入-深圳最全娱乐资源【杰尼龟】 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 冬日奶茶50 × 2 ⚠️ 抽奖说明: 1. 兑奖请联系 @szjngbot ,炸号者中奖作废。 2. 奖品自开奖时间起24小时内有效。 3. 胡乱恶意水群者取消领奖资格‼️ 📅 开奖日期:(北京时间) 2026年11月19日 19时19分00秒

16 Nov 2026, 08:36 UTC369 views2 reactionsread 17 November 2026
Photo

🆔 名字:悦悦 📍 区域:#南山区 💰 价格:#1300P 🚀 私聊:@Yy2005a 💬 报告:点击查看报告 🌍 定位:点击查看定位 💎 特色:#嫩妹 #69p #舌吻 #水中萧 #上门

❤2

16 Nov 2026, 06:00 UTC418 viewsread 17 November 2026
Photo

🆔 名字:王建国 📍 区域:#南山区 💰 价格:#1500P 🚀 私聊:@Wjg888a 💬 报告:点击查看报告 🌍 定位:点击查看定位 💎 特色:#嫩妹 #舌吻 #69p

15 Nov 2026, 23:26 UTC10 viewsread 15 November 2026

🍬🍬🍬今日出勤商-11月16日🍬🍬🍬 【600以下】:玲玲-南山区 | 朱朱-南山区 | 陈兮 #抓龙筋-南山区 | 陈思琪-福田区 【600-800】:凌儿-南山区 【800-1200】:小雨-宝安区 | 维维-宝安区 | 点点-龙岗区 【1200-1500】:宝儿-南山区 | 菲儿-南山区 | 小丸子-福田区 | 柚柚-南山区 | 刘富贵-南山区 | 苡沫-南山区 | 蕊蕊-南山区 | 上官婉儿-南山区 | 玥玥-罗湖区 | 桃子-福田区 | 佳佳-龙岗区 | 沁沁-宝安区 | 源源-南山区 | UU-南山区 | 小鱼-南山区 | 刘苡扉-南山区 | 护士-南山区

15 Nov 2026, 11:24 UTC36 viewsread 15 November 2026

🍬🍬🍬今日出勤商-11月15日🍬🍬🍬 【600以下】:玲玲-南山区 | 雯雯-宝安区 | 正阳-南山区 | 姜姜-龙华区 | 木木-罗湖区 | 朱朱-南山区 | 皇室姐妹-光明区 | 陈兮 #抓龙筋-南山区 | 陈思琪-福田区 【600-800】:小e-南山区 | 凌儿-南山区 | 媚儿-南山区 【800-1200】:豆豆-宝安区 | 点点-龙华区 | 小雨-宝安区 | 维维-宝安区 | 点点-龙岗区 | 小希-福田区 | 土豆-龙岗区 | 北北-龙岗区 | 脱脱-南山区 | 晚晚-龙岗区 【1200-1500】:宝儿-南山区 | 安妮-南山区 | 水咲泷拉-南山区 | 小丸子-福田区 | 彤彤-南山区 | 柚柚-南山区 | 小冉-南山区 | 伊依-南山区 | 栖月-龙岗区 | 悦悦-南山区 | 刘富贵-南山区 | 苡沫-南山区 | 蕊蕊-南山区 | 美希-南山区 | 上官婉儿-南山区 | 乔熙-南山区 | 依依-南山…

15 Nov 2026, 10:24 UTC16 viewsread 15 November 2026

🍬🍬🍬今日出勤商-11月15日🍬🍬🍬 【600以下】:玲玲-南山区 | 雯雯-宝安区 | 正阳-南山区 | 姜姜-龙华区 | 木木-罗湖区 | 朱朱-南山区 | 皇室姐妹-光明区 | 陈兮 #抓龙筋-南山区 | 陈思琪-福田区 【600-800】:小e-南山区 | 凌儿-南山区 | 媚儿-南山区 【800-1200】:豆豆-宝安区 | 点点-龙华区 | 小雨-宝安区 | 维维-宝安区 | 点点-龙岗区 | 小希-福田区 | 土豆-龙岗区 | 北北-龙岗区 | 脱脱-南山区 | 晚晚-龙岗区 【1200-1500】:宝儿-南山区 | 安妮-南山区 | 水咲泷拉-南山区 | 小丸子-福田区 | 彤彤-南山区 | 柚柚-南山区 | 小冉-南山区 | 伊依-南山区 | 栖月-龙岗区 | 悦悦-南山区 | 刘富贵-南山区 | 苡沫-南山区 | 蕊蕊-南山区 | 美希-南山区 | 上官婉儿-南山区 | 乔熙-南山区 | 依依-南山…

15 Nov 2026, 09:45 UTC584 views1 reactionsread 17 November 2026
Photo

🆔 名字:小希 📍 区域:#福田区 💰 价格:#998P 🚀 私聊:@fugeliu 💬 报告:点击查看报告 🌍 定位:点击查看定位 💎 特色:#嫩妹 #蛇吻 #69p #回笼 #上门

❤1

15 Nov 2026, 09:18 UTC23 viewsread 15 November 2026

🍬🍬🍬今日出勤商-11月15日🍬🍬🍬 【600以下】:玲玲-南山区 | 雯雯-宝安区 | 正阳-南山区 | 姜姜-龙华区 | 木木-罗湖区 | 朱朱-南山区 | 皇室姐妹-光明区 | 陈兮 #抓龙筋-南山区 | 陈思琪-福田区 【600-800】:小e-南山区 | 凌儿-南山区 | 媚儿-南山区 【800-1200】:豆豆-宝安区 | 点点-龙华区 | 小雨-宝安区 | 维维-宝安区 | 点点-龙岗区 | 土豆-龙岗区 | 北北-龙岗区 | 脱脱-南山区 | 晚晚-龙岗区 【1200-1500】:宝儿-南山区 | 水咲泷拉-南山区 | 小丸子-福田区 | 彤彤-南山区 | 柚柚-南山区 | 小冉-南山区 | 伊依-南山区 | 栖月-龙岗区 | 悦悦-南山区 | 刘富贵-南山区 | 苡沫-南山区 | 蕊蕊-南山区 | 美希-南山区 | 上官婉儿-南山区 | 乔熙-南山区 | 依依-南山区 | 桃子-福田区 | 锦汐-南山…

Showing the 12 most recent of 561 posts we hold for @szylzy1. 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.

Posts edited after publishing

@szylzy1 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
20 August 2026
Most recent edit
20 August 2026

Posts recorded as deleted after publishing

We recorded 84 posts on @szylzy1 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.

First seen missing
8 August 2026
Most recent seen missing
15 November 2026
Median time before seen missing
12 hours
Seen missing in the last 30 days
38

Forward network

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 22 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.

Names

Channels on the register whose handles appear in this channel's posts.

深圳杰尼龟修车
@jngsz · 39,445
8 posts
肥仔甄选(只做精品)
@SZfeizai · 8,563
7 posts
深圳库洛米嫩妹丝足抓龙筋SM⭕️
@szklmgp · 2,686
6 posts
深圳高端水疗会所 00后专场
@dsx26149 · 15,961
3 posts
深圳修车觅蚌交流群
@dsx6291 · 1,416
3 posts
荷花:深圳会所推荐官
@SZYY5683 · 5,322
3 posts
深圳皇家小妖精.小E持证抓龙筋半裸(收女徒)
@xiaoe99988 · 5,238
3 posts
深圳皇家小妖精持证抓龙筋群
@xiaoe999888 · 2,022
3 posts
深圳美少女-丝足 SM频道 深圳丝足 深圳SM
@aisizukong · 15,045
2 posts
南山 初音· あんじ 疗愈私密抓龙筋SPA
@ggs66633 · 12,632
2 posts
南山简悦 & 私享半裸抓龙筋高端SPA
@Joy52088 · 7,188
2 posts
玲玲印度密宗威龙猛探抓龙筋
@lingling9666 · 1,488
2 posts
南山 思欲 疗愈半裸抓龙筋SPA
@Lxzlj52000 · 5,987
2 posts
少女屋素人学生频道
@miaonv1 · 2,706
2 posts
深圳美少女丝足 SM 交流群
@shenzhenmeishaonvsizu · 6,284
2 posts
深圳会所《丝足嫩妹毒龙高端会所》
@SZ7889495 · 2,020
2 posts
深圳会所《丝足嫩妹毒龙高端会所》
@SZ888123 · 532
2 posts
足艺频道2.0
@szklmmldzy · 5,573
2 posts
初见·疗愈半裸抓龙筋
@szlhrispa · 13,045
2 posts
深圳福田美乐蒂抓龙筋丝足SM
@szmldpd · 6,980
2 posts
深圳94/95会所选妃
@wsjbxi · 2,184
2 posts
南山 姬子 · 启行っぽい 嫩妹抓龙筋SPA
@wtqq168 · 7,786
2 posts
龙岗中心城-瑶瑶-半裸丝足抓龙筋
@yao1389 · 2,164
2 posts
南山樱花🌸境·疗愈セクシー抓龙筋SPA
@yhuajzlj88 · 8,373
2 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“深圳最全娱乐资源【杰尼龟】” (@szylzy1), 27,648 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/szylzy1.

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.