Telegram RegisterThe public register of Telegram
Telegram profile photo for 上海风子修车行总榜

Channel

上海风子修车行总榜

@fzxczb1

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

85,893subscribers

+43,153 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001815146307
TypeChannel
Username@fzxczb1
Description上榜唯一管理: @fengmizhuanshu_bot 聊天群 :https://t.me/+rkur-OsBKTZjZmU0 备用群:https://t.me/fengzixiuche013 榜单: @fzxchbd1 作业频道: https://t.me/fzxchaoping1 外围:https://t.me/niao798
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/fzxczb1

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 21 August 2026 and assigned it the closest of 31 fixed categories, at 63% 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 2 other registered channels. 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
@fzxczb1/16718 · this entry7 Aug 2026, 07:09 UTC@fzxchbd1/105867 Aug 2026, 07:10 UTC1.00under a minute
@fzxchbd1/108701 Sept 2026, 12:26 UTC@fzxczb1/17170 · this entry1 Sept 2026, 12:26 UTC1.00under a minute
@fzxczb1/20123 · this entry21 Oct 2026, 09:51 UTC@fzxchbd1/129964 Nov 2026, 07:27 UTC1.0014 days
@fzxczb1/20723 · this entry4 Nov 2026, 11:24 UTC@fzxchbd1/129974 Nov 2026, 11:25 UTC1.00under a minute
@fzxczb1/21062 · this entry9 Nov 2026, 13:57 UTC@fzxchbd1/132299 Nov 2026, 13:58 UTC1.00under a minute
@fzxchbd1/1329210 Nov 2026, 15:33 UTC@fzxczb1/21184 · this entry10 Nov 2026, 15:34 UTC1.0072 seconds
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
@fzxchbd115 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–7)
@shanghaigroup316 (6/6 hand-verifiable sample passed)1.0023 hourseven

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

42,74085,89364,316.56 August 202614 November 2026
66 measurements spanning 100 days, net +43,153. 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 36,267–92,366 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
14 Nov 2026, 20:0085,893+1,788
11 Nov 2026, 16:3784,105+1,182
9 Nov 2026, 17:2082,923+411
8 Nov 2026, 11:1682,512-15
7 Nov 2026, 07:4982,527+252
6 Nov 2026, 10:1682,275+386
5 Nov 2026, 10:1881,889+574
4 Nov 2026, 11:0181,315+647
3 Nov 2026, 12:4680,668+740
2 Nov 2026, 10:1179,928+620
1 Nov 2026, 09:3579,308+682
31 Oct 2026, 11:3778,626+516
30 Oct 2026, 08:4778,110+615
29 Oct 2026, 07:4077,495+668
28 Oct 2026, 08:3576,827+741
27 Oct 2026, 07:0976,086+418
26 Oct 2026, 06:4675,668+525
25 Oct 2026, 04:5675,143+418
24 Oct 2026, 05:1874,725+287
23 Oct 2026, 02:5974,438first reading

Engagement

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

ERR · 30 days
0.44%
avg views ÷ 85,893 subscribers
Avg views / post
378
125 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
125
of 371 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 15 November 2026
Posts held371 (6 August 2026 – 15 November 2026)
Views total47,225
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 01:51 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
≈1,530
Videos
≈331
Links
≈292

Lifetime counters from Telegram’s own channel header, read 16 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
34m 19s
Average length
9s

Measured directly from 231 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: 4 of 125 posts held from the last 30 days (3.20%) 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).

15 Nov 2026, 14:11 UTC466 viewsread 16 November 2026
Photo

【全区95 98莞式全套海选会所】🌸私人定制spa私密会所 😇 海选 😇 油压 😇 莞式 😇 全套 😇 花式 🟢会所介绍 :海选模式 莞式服务, 环境豪华私密安全, 给您至尊享受的高端体验,可依您的喜好和需求为您做专属的私人项目定制。 更多剧本等你来解锁 主题房,制定角色,制定服装,满足你的所有幻想莞式36式 , 🛁皇帝共浴,💆菲式按摩,💪莞式抓龙, 👙制服诱惑, 👯‍♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 全裸艳舞 😃 鸳鸯戏水😄 水磨推拿😄 口舌调情 😄 后口毒龙 😀胯下吞龙 😃手推胸推😄 足推臀推 😊 激情爱爱 😄 制服情趣😀 到店海选 😄【冰火双重天】😃 等三十多种项目。💒 🔥服务流程:皇帝共浴🛁指滑🫳🏻鼻息🗓舌尖漫游🥂-ab面骑士-💋柔式按摩放松-❤️花式调情雄起📞-水漫金山-🎯漫水吹箫💖-深情直入🥂🍀深喉😒69+ 🌹舔耳😒鸳鸯浴 玫瑰浴 ☘️…

15 Nov 2026, 12:32 UTC555 viewsread 16 November 2026
Photo

💥💥 #香奈儿上海高端外围💥💥 👉全国大圈可安排👉 🔔年轻学妹 🔔气质御姐 🔔空乘空姐 🔔服务SM 🔔包天伴游 🔔情绪提供 🥰妹子多多,每天更新,等你来挑 👄上海总群 @shanghaixo2025 🥰上海大圈 @shhwaiwei 🥰上海中圈 @pdxo2025 🥰日本东京直营 @chaneltokyo0 🔡浦东中圈 🧩静安中圈 🔡黄浦中圈 🔡普陀中圈 🎭闵行中圈 💍徐汇中圈 🎭嘉定中圈 💍宝山中圈 🎭松江中圈 💍长宁中圈 🎭杨浦中圈 💍虹口中圈 🔡名称:#香奈儿 🥰客服: @sss2025sh (客服阿雅) 🥰双向: @sscutefairy_bot 📍位置:#浦东 #静安 #黄浦 #普陀 #徐汇 #闵行

15 Nov 2026, 08:19 UTC≈1,090 viewsread 16 November 2026
Photo

✉️6条车评,综合评分9.46 好评100% | 人照9.15 |颜值9.02 中评0% | 服务9.75 |态度9.83 差评0% | 身材9.55 |环境 艺名: #张菇凉 地区:#虹口 身材:162cm 50kg 胸D 课费: 700/p 1300/pp 服务: #御姐,#大胸,#鸳鸯浴,#舌吻,#六九,#口爆,#深喉,#过水,#SPA按摩,#制服,#丝袜 联系: @linjie618

15 Nov 2026, 07:08 UTC899 viewsread 16 November 2026
Photo

✉️21条车评,综合评分8.79 好评100% | 人照8.52 |颜值8.72 中评0% | 服务9.01 |态度8.91 差评0% | 身材9.07 |环境8.50 艺名: #杨倩 地区:#静安 身材:160cm 45kg 胸B 课费: 700/p 1400/pp 服务: #兼职,#御姐,#舌吻,#六九,#口爆,#角色扮演,#SM,#颜射,#按摩,#胸推,#制服,#丝袜,#外出,#推荐 联系: @qiaoqiaoer0003

15 Nov 2026, 03:22 UTC256 viewsread 15 November 2026
Photo

✉️0条车评,综合评分0 好评0% | 人照 |颜值 中评0% | 服务 |态度 差评0% | 身材 |环境 艺名: #糖果豆豆 地区:#普陀 身材:165cm 51.5kg 胸C 课费: 700/p 1300/pp 2800/夜 服务: #图二手势视频验证,#鸳鸯浴,#水中萧,#胸推,#漫游,#指滑,#深度调情,#外出 联系: @zengwen_0808

14 Nov 2026, 17:02 UTC≈1,440 viewsread 15 November 2026
Photo

TG必备的搜索引擎,快搜kuai帮你发现有趣群组、频道、视频、音乐、电影、新闻 | Find cool stuff all in one bot! 机器人:@kuai @kuaia @kuaiaa 👉 https://t.me/kuaiaa?start=a_3BJO01P

14 Nov 2026, 13:19 UTC≈1,070 viewsread 15 November 2026
Video

#普陀#静安 #推油 #海选 #四推 御兰亭 😃😃😃静安-普陀高端T台海选 😳🤯😃😃😃 🧂⚽️🏀🏈⚾️🥎🎾🏐 坐标:#静安#安远路 类型:#海选 #4T 价格:#499元 😀😀静安安远路首家高端SPA会所,静安第一旗舰店 📱📱专业团队·强势来袭,聘各店之红牌,铸就本店巅峰颜值,实体口碑店【颜控首选】👍 🔔服务时间60分钟,出水不限次数💦 🥐原价799/999,现活动价499元‼️ 😆😄双飞第二个半价😋😋一龙二凤 同进同出 双倍快乐🤠 🔺🔻🔸🔹🔶🔷🔳🔲 🐗为回馈新老客户,本店推出长期优惠活动🔥(多店互通♥️) 1️⃣.三人同行共优惠3️⃣0️⃣0️⃣ 2️⃣.四人同行共优惠4️⃣0️⃣0️⃣ 3️⃣.五人同行直接免一单 4️⃣.累计到店消费5次,优惠😍🙃🙃 📱📱📱📱📱📱📱📱📱📱📱📱📱 😀全场海选模式,每天出勤30➕💕主打00后.模特.小网红.空姐.车模.大学生兼职.大胸.A4腰.蜜桃臀.筷子腿…等各类高颜值极品嫩…

14 Nov 2026, 12:22 UTC182 viewsread 15 November 2026
Photo

✉️3条车评,综合评分9.16 好评100% | 人照8.83 |颜值8.67 中评0% | 服务9.83 |态度9.83 差评0% | 身材8.83 |环境9.00 艺名: #神的宠儿 地区:#闵行 身材:160cm 44.5kg 胸B 课费: 700/p 1200/pp 3500/夜 服务: #陪浴,#六九,#口爆,#毒龙,#深喉,#颜射,#指滑,#漫游,#车震,#外出,#上榜视频已验证 联系: @chongerbaby

14 Nov 2026, 11:09 UTC212 viewsread 15 November 2026
Photo

✉️35条车评,综合评分9.35 好评97% | 人照9.39 |颜值9.20 中评3% | 服务9.41 |态度9.41 差评0% | 身材9.37 |环境9.13 艺名: #coco 地区:#青浦 身材:168cm 59kg 胸C 课费: 700/p 1300/pp 2500/夜 服务: #御姐,#鸳鸯浴,#舌吻,#六九,#胸推,#按摩,#丝袜,#图二视频验证,#推荐 联系: @Coco77881

13 Nov 2026, 13:02 UTC≈1,840 viewsread 14 November 2026
Photo

TG必备的搜索引擎,快搜kuai帮你发现有趣群组、频道、视频、音乐、电影、新闻 | Find cool stuff all in one bot! 机器人:@kuai @kuaia @kuaiaa 👉 https://t.me/kuaiaa?start=a_3BJO01P

13 Nov 2026, 10:44 UTC≈1,930 viewsread 14 November 2026
Photo

虹口移动95专场 价格:🤫🫨🫠 本店主打:00.99.年 🤫❤️+📱🥶 出勤15+ 组团活动: 📣3人以上包括3人每人400 实体店:每间房都有单独淋浴 每天出勤15+ 双F只加2张 停车方便,路边有停车位 营业时间: 中午13点至凌晨2点。 😀地址:虹口曲阳 🫨🤫🤫🫠电话电话:18701779500(同v) 🫨🤫🤫🫠QQ:2993299507 🫨🤫🤫🫠电报:@Yd12222223 频道:https://t.me/xie12345666 TG群:https://t.me/ye12345688

13 Nov 2026, 05:21 UTC371 viewsread 14 November 2026
Photo

✉️0条车评,综合评分0 好评0% | 人照 |颜值 中评0% | 服务 |态度 差评0% | 身材 |环境 艺名: #晴儿 地区:#闵行 身材:169cm 48kg 胸C 课费: 1000/p 1700/pp 服务: #白虎,#上榜视频已验证,#嫩妹,#陪浴,#舌吻,#六九,#制服,#丝袜 联系: @qingqing2271

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

@fzxczb1 edited 5 posts 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
26 October 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @fzxczb1 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
31 October 2026
Most recent seen missing
2 November 2026
Median time before seen missing
33 hours
Seen missing in the last 30 days
3

Mentions

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

“上海风子修车行总榜” (@fzxczb1), 85,893 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/fzxczb1.

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.