Telegram RegisterThe public register of Telegram
Telegram profile photo for 上海出击大队公开榜

Channel

上海出击大队公开榜

@quanguo999

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

18,129subscribers

+2,518 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-1001247146550
TypeChannel
Username@quanguo999
Description上海出击大队: @shxczyq 上海报告榜: @shxhjpzy 上海福利榜: @shpccj 管理员: @SHXCDDGNY_bot
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/quanguo999

Topic

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 56% 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 3 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@shkccj/206966 Aug 2026, 08:32 UTC@quanguo999/23637 · this entry6 Aug 2026, 08:32 UTC1.00under a minute
@shkccj/207697 Aug 2026, 08:15 UTC@quanguo999/23674 · this entry7 Aug 2026, 08:15 UTC1.00under a minute
@shkccj/2106515 Aug 2026, 08:38 UTC@quanguo999/23960 · this entry15 Aug 2026, 08:38 UTC1.00under a minute
@shkccj/2148128 Aug 2026, 14:34 UTC@quanguo999/24375 · this entry28 Aug 2026, 14:35 UTC1.00under a minute
@shkccj/2152229 Aug 2026, 12:22 UTC@quanguo999/24418 · this entry29 Aug 2026, 12:22 UTC1.00under a minute
@shkccj/217143 Sept 2026, 06:06 UTC@quanguo999/24622 · this entry3 Sept 2026, 06:06 UTC1.00under a minute
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
@shkccj118 (8/8 hand-verifiable sample passed)1.00under a minute@shkccj (115–3)
@shpccj18 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (14–4)
@shxhjpzy5 (5/5 hand-verifiable sample passed)1.00under a minutethis 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. 119 of the 119 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 189 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).

Of the group of 4 channels, the one whose matching posts we hold earliest is @shkccj. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · 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.

Channels linked by matching posts

This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

15,38918,12916,7596 August 202614 November 2026
64 measurements spanning 100 days, net +2,518. 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 14,978–18,540 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
14 Nov 2026, 15:4818,129+79
11 Nov 2026, 17:1618,050+207
9 Nov 2026, 23:3817,843+434
8 Nov 2026, 14:1617,409+234
7 Nov 2026, 06:3617,175+5
6 Nov 2026, 02:3517,170+8
4 Nov 2026, 23:1817,162+15
3 Nov 2026, 19:4617,147+7
2 Nov 2026, 17:3117,140+5
1 Nov 2026, 20:5717,135+8
31 Oct 2026, 19:0017,127-9
30 Oct 2026, 17:2917,136+2
29 Oct 2026, 16:2017,134+19
28 Oct 2026, 15:0717,115+13
27 Oct 2026, 13:2617,102-217
26 Oct 2026, 10:4017,319+50
25 Oct 2026, 12:4517,269+324
24 Oct 2026, 09:3416,945+34
23 Oct 2026, 10:5716,911+3
22 Oct 2026, 11:1516,908first reading

Engagement

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

ERR · 30 days
0.944%
avg views ÷ 18,129 subscribers
Avg views / post
171
73 posts measured
Reaction rate
0.482%
reactions ÷ views · ER floor
Posts in window
73
of 204 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 13 of 73 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 held204 (6 August 2026 – 17 November 2026)
Views total12,494
Reactions total12
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 06:26 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
≈2,460
Videos
≈466
Links
≈554

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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
17m 27s
Average length
11s

Measured directly from 97 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

25 reactions across 21 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤25100.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 35 of the 204 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 204 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: 2 of 73 posts held from the last 30 days (2.74%) 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, 02:52 UTC96 viewsread 17 November 2026
Photo

艺名:#闪闪 己验证 位置:#虹口 奶妈 身高:163cm 体重: 52kg 胸围:G 课费:2000p 3000pp 优惠:1500p 2500pp 电报:@zxc199511 双向:@haha1996_bot ♥️联系老师说明来自:上海出击大队 评价1 评价2 评价3 评价4 评价5 评价6 ————————————————— 福利榜 报告榜 管理员

16 Nov 2026, 14:13 UTC218 viewsread 17 November 2026
Photo

艺名:#妍宝 己验证 #群友投稿 位置:#闵行 良家兼职 身高:166cm 胸围:D+ 重体:50kg 课费:800p 1500pp 📱微信:lyh726389 📱QQ: 1570789692 与你号:28135441sw5xg6 评价1 —————————————————— 福利榜 报告榜 管理员

16 Nov 2026, 13:59 UTC197 viewsread 17 November 2026
Photo

艺名:#Tina 己验证 群友投稿 位置:#闵行 嗲妹子 身高:165cm 体重:50kg 胸围:B+ 课费:800p 📱微信号:Ww696879 📱QQ: 2249125675 评价1 评价2 评价3 评价4 ———————————————— 福利榜 报告榜 管理员

16 Nov 2026, 10:22 UTC185 viewsread 16 November 2026
Photo

艺名:#杨杨 己验证 位置:#嘉定 巨臀肉腿bbw 身高:160cm 胸围:D 重体:64kg 课费:800p 1400pp 📱电报:@Yxy1122 🤖双向:@yangyang112233_bot ♥️联系老师说明来自:上海出击大队 评价1 评价2 评价3 评价4 评价5 评价6 评价7 评价8 评价9 —————————————————— 福利榜 报告榜 管理员

16 Nov 2026, 10:13 UTC182 viewsread 16 November 2026
Video

#沙田新都汇 版主认证推荐🤕📱📱📱📱📱😠📱 价格:#468元 类型:#新都汇海选 😢营业时间 中午12:00-凌晨3:00 十多年老店放心消费有东西懂得都懂 五星装修 两千多平大店 环境好 全场大海选模式 每天出勤保持在38位左右,在岗类别有 ​洋马 05后姐妹花 网红 车模 商K下海 俄罗斯 兼职 教室 护士 御姐等等 (每次进店报“利群”可享受以下优惠) 两人行 老带新立减200 2️⃣.三人团最高优惠300 3️⃣.四人同行最高优惠400 4️⃣.五人同行直接免一单 5️⃣.累记到店满五次可享受400优惠 ⤴ 利群海选: @WG8723 @WG872 ⤴️店内实时更新频道: @ykys01 聊天探讨抽奖群:@KKH890 利群电话: 18516771618 同微 利群电话:17621642239 同微 利群电话:13072172972 同微 QQ:25623…

16 Nov 2026, 06:09 UTC18 viewsread 16 November 2026
Photo

艺名:#语儿 己验证 位置:#普陀 嫩妹 身高:165cm 体重: 50kg 胸围:C 课费:800p 1600pp 电报:@Yuuerbb 双向:@gnfgnjghjnbot ♥️联系老师说明来自:上海出击大队 ———————————————— 福利榜 报告榜 管理员

15 Nov 2026, 12:42 UTC213 views3 reactionsread 16 November 2026
Photo

艺名:#lucky 己验证 群友投稿 位置:#浦东 女友系 身高:165cm 体重:50kg 胸:36C 课费:1500p 2500pp 📱微信:tt15988931756 评价1 —————————————————— 广播台 报告榜 管理员

❤3

15 Nov 2026, 11:58 UTC230 viewsread 16 November 2026
Photo

艺名:#微微 己验证 群友投稿 位置:#浦东 居家个人spa 身高:163cm 体重:49kg 胸:C 课费:600 📱qq号:2495793110 评价1 评价2 评价3 评价4 评价5 评价6 评价7 评价8 ————————————————— 福利榜 报告榜 管理员

15 Nov 2026, 10:27 UTC167 viewsread 15 November 2026
Photo

艺名:#小乐 己验证 群友投稿 位置:#黄埔 居家个人SPA 身高:165cm 体重:48kg 胸:C 课费::600/70分钟 📱QQ:3225888409 与你号:17821384056 与你号:18017367302 📱微信:19986840519 ————————————————— 福利榜 报告榜 管理员

15 Nov 2026, 04:42 UTC56 viewsread 15 November 2026
Photo

艺名:#子涵 己验证 位置:#松江 大学生在读兼职 身高:170cm 体重: 49kg 胸围:D+ 课费:1100p 1600pp 电报:@bbbhkmm 双向:@bbbhkmm_BOT ♥️联系老师说明来自:上海出击大队 ———————————————— 报告榜 写评价 管理员

14 Nov 2026, 10:26 UTC215 viewsread 15 November 2026
Photo

艺名:#苗苗 己验证 位置:#闵行 模特兼职 身高:172cm 体重: 51kg 胸围:B 课费:600p 1200pp 电报:@jiaojiao1010 双向:@jiaojiao1122_bot ♥️联系老师说明来自:上海出击大队 评价1 ———————————————— 报告榜 写评价 管理员

14 Nov 2026, 08:45 UTC211 viewsread 15 November 2026
Photo

艺名:#林熙儿 己验证 群友投稿 位置:#黄浦 上戏大二学生 身高:170cm 胸围:E 体重:50kg 课费:2200p 📱微信:xiaobaby7766 评价01 评价02 评价03 评价04 评价05 评价06 评价07 评价08 评价09 评价10 评价11 评价12 评价13 评价14 评价15 评价16 评价17 评价18 评价19 评价20 评价21 评价22 评价23 ————————————————— 上海大队 报告榜 管理员

Showing the 12 most recent of 204 posts we hold for @quanguo999. 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 1 post on @quanguo999 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
13 November 2026
Most recent seen missing
13 November 2026
Median time before seen missing
22 hours
Seen missing in the last 30 days
1

Mentions

Named by 11 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.

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

“上海出击大队公开榜” (@quanguo999), 18,129 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/quanguo999.

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.