Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳.取餐区

Channel

深圳.取餐区

@Sz_qcq

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

29,184subscribers

+9,406 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-1001415768469
TypeChannel
Username@Sz_qcq
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/Sz_qcq

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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
@Sz_qcq/4338 · this entry8 Aug 2026, 07:53 UTC@choujiangzh/14128 Aug 2026, 07:53 UTC1.00under a minute
@Sz_qcq/4450 · this entry10 Aug 2026, 10:15 UTC@choujiangzh/142110 Aug 2026, 10:15 UTC1.00under a minute
@Sz_qcq/4574 · this entry12 Aug 2026, 12:30 UTC@choujiangzh/142812 Aug 2026, 12:30 UTC1.00under a minute
@choujiangzh/146224 Aug 2026, 15:13 UTC@Sz_qcq/5199 · this entry24 Aug 2026, 15:15 UTC1.002 minutes
@choujiangzh/146325 Aug 2026, 03:51 UTC@Sz_qcq/5204 · this entry25 Aug 2026, 03:52 UTC1.0072 seconds
@choujiangzh/152726 Sept 2026, 10:07 UTC@Sz_qcq/7087 · this entry26 Sept 2026, 10:13 UTC1.006 minutes
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
@choujiangzh29 (8/8 hand-verifiable sample passed)1.00under a minute@choujiangzh (16–13)

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. 16 of the 16 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 392 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_mutual, 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

18,77430,95724,865.529,1846 August 202617 November 2026
66 measurements spanning 103 days, net +9,406. 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 16,947–32,784 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
17 Nov 2026, 17:5729,184-138
14 Nov 2026, 15:1129,322-502
11 Nov 2026, 19:2729,824-593
10 Nov 2026, 00:5030,417-255
8 Nov 2026, 15:1630,672-134
7 Nov 2026, 09:5630,806+212
6 Nov 2026, 09:5030,594+288
5 Nov 2026, 12:5930,306+4,760
4 Nov 2026, 10:1425,546-291
3 Nov 2026, 13:1625,837-390
2 Nov 2026, 11:1026,227-586
1 Nov 2026, 08:1526,813-416
31 Oct 2026, 09:4127,229-361
30 Oct 2026, 12:1027,590-538
29 Oct 2026, 12:5728,128-9
28 Oct 2026, 13:2628,137-41
27 Oct 2026, 14:4028,178+145
26 Oct 2026, 17:2028,033+103
25 Oct 2026, 16:1527,930-71
24 Oct 2026, 16:0528,001first reading

Engagement

540 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 217 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.80%
avg views ÷ 29,184 subscribers
Avg views / post
525
141 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
141
of 540 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held540 (6 August 2026 – 17 November 2026)
Views total74,054
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 13:22 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

Video runtime
25m 57s
Average length
10s

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

Recent posts

Telegram’s own ‘edited’ marker: 0 of 141 posts held from the last 30 days (0%) 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, 13:06 UTC26 viewsread 17 November 2026

各位小哥哥们,🐺狼友群里福利活动已开始,还会不定时的推出老师们的抽奖活动🎟️,点击下面导航条找到🐺狼友群加入吧!

17 Nov 2026, 09:22 UTC700 viewsread 17 November 2026
Photo

茶餐厅11月活动:🔥🔥🔥🔥🔥 发言排名前7现金奖励红包🧧奖励: 第一名现金红包🧧:100元 第二名现金红包🧧:100元 第三名现金红包🧧:100元 第四名现金红包🧧:100元 第五名现金红包🧧:100元 第六名现金红包🧧:100元 第七名现金红包🧧:100元 备注:🐺狼友群发言排名奖励🎁同时开启🔛 11月邀请活动任在继续,多邀请多的奖励! 积分规则:签到20分,一句话1分,一份出击报告100分! 希望狼友踊跃参与,现金疯狂撒,多多发言,多多参与,多攒积分 下一步会开展积分抽奖、积分拍卖、积分兑换! 敬请期待!!!

17 Nov 2026, 01:06 UTC11 viewsread 17 November 2026

各位小哥哥们,🐺狼友群里福利活动已开始,还会不定时的推出老师们的抽奖活动🎟️,点击下面导航条找到🐺狼友群加入吧!

16 Nov 2026, 23:06 UTC20 viewsread 17 November 2026

各位小哥哥们,🐺狼友群里福利活动已开始,还会不定时的推出老师们的抽奖活动🎟️,点击下面导航条找到🐺狼友群加入吧!

16 Nov 2026, 21:06 UTC≈1,000 viewsread 16 November 2026

各位小哥哥们,🐺狼友群里福利活动已开始,还会不定时的推出老师们的抽奖活动🎟️,点击下面导航条找到🐺狼友群加入吧!

16 Nov 2026, 09:22 UTC843 viewsread 17 November 2026
Photo

茶餐厅11月活动:🔥🔥🔥🔥🔥 发言排名前7现金奖励红包🧧奖励: 第一名现金红包🧧:100元 第二名现金红包🧧:100元 第三名现金红包🧧:100元 第四名现金红包🧧:100元 第五名现金红包🧧:100元 第六名现金红包🧧:100元 第七名现金红包🧧:100元 备注:🐺狼友群发言排名奖励🎁同时开启🔛 11月邀请活动任在继续,多邀请多的奖励! 积分规则:签到20分,一句话1分,一份出击报告100分! 希望狼友踊跃参与,现金疯狂撒,多多发言,多多参与,多攒积分 下一步会开展积分抽奖、积分拍卖、积分兑换! 敬请期待!!!

15 Nov 2026, 16:28 UTC696 viewsread 17 November 2026
Photo

👤 深圳.茶餐厅 名字:源源 地区:南山(可上门) 验证:手势验证 资料:166身高45kg🐻E 价位:P1400/PP2500 联系:@aayuanu 频道: https://t.me/Ecy003x 双向:@Szyyjqrbot 标签: #鸳鸯浴 #无套口 #亲亲调情 #胸推 #激情69 #情趣制服 #丝袜诱惑 茶餐厅 | 取餐区 | 报告区

15 Nov 2026, 15:58 UTC840 viewsread 17 November 2026
Photo

👤 深圳.茶餐厅 名字:菲菲 地区:南山 验证:手势验证 资料:21岁166身高49kg🐻36D 价位:P800/PP1500/夜5000 联系:@feifeinan 频道:https://t.me/feifeinans 双向:@feifeinnbot 标签:#舌吻💋 #陪浴 #无套口 #激情69 #足交 #深喉 #指划 #情趣制服 #丝袜高跟 茶餐厅 | 取餐区 | 报告区

15 Nov 2026, 12:52 UTC607 viewsread 17 November 2026
Photo

👤 深圳.茶餐厅 名字:刘苡扉 地区:南山 验证:手势验证 资料:22岁166身高49kg🐻B+ 价位:P1400/PP2400 联系:@Szlyffff 频道:https://t.me/Szlyf001 双向:@Jjdchtaabot 标签:#舌吻💋 #激情69 #鸳鸯浴 #情趣制服 #丝袜诱惑 茶餐厅 | 取餐区 | 报告区

15 Nov 2026, 09:22 UTC33 viewsread 15 November 2026
Photo

茶餐厅11月活动:🔥🔥🔥🔥🔥 发言排名前7现金奖励红包🧧奖励: 第一名现金红包🧧:100元 第二名现金红包🧧:100元 第三名现金红包🧧:100元 第四名现金红包🧧:100元 第五名现金红包🧧:100元 第六名现金红包🧧:100元 第七名现金红包🧧:100元 备注:🐺狼友群发言排名奖励🎁同时开启🔛 11月邀请活动任在继续,多邀请多的奖励! 积分规则:签到20分,一句话1分,一份出击报告100分! 希望狼友踊跃参与,现金疯狂撒,多多发言,多多参与,多攒积分 下一步会开展积分抽奖、积分拍卖、积分兑换! 敬请期待!!!

15 Nov 2026, 09:06 UTC46 viewsread 15 November 2026

各位小哥哥们,🐺狼友群里福利活动已开始,还会不定时的推出老师们的抽奖活动🎟️,点击下面导航条找到🐺狼友群加入吧!

15 Nov 2026, 07:06 UTC558 viewsread 15 November 2026

各位小哥哥们,🐺狼友群里福利活动已开始,还会不定时的推出老师们的抽奖活动🎟️,点击下面导航条找到🐺狼友群加入吧!

Showing the 12 most recent of 540 posts we hold for @Sz_qcq. 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 recorded as deleted after publishing

We recorded 47 posts on @Sz_qcq 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
28 September 2026
Most recent seen missing
16 November 2026
Median time before seen missing
13 hours
Seen missing in the last 30 days
35

Forward network

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 46 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“深圳.取餐区” (@Sz_qcq), 29,184 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/Sz_qcq.

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.