Telegram RegisterThe public register of Telegram
Telegram profile photo for 成都医科大学报告榜单

Channel

成都医科大学报告榜单

@chengduainila

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

36,637subscribers

+21,232 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-1002563010025
TypeChannel
Username@chengduainila
Description成都医科大学已验车库: https://t.me/shangpailaoshi 上牌:商务合作或提交报告联系 : @lyihstzw 双向机器人 @Yike55688_bot
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/chengduainila

Topic

Other / unclassifiable — 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 53% 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@chengduainila/932 · this entry8 Aug 2026, 08:57 UTC@yihaoxianbaogao/53199 Aug 2026, 07:30 UTC1.0023 hours
@yihaoxianbaogao/534410 Aug 2026, 12:10 UTC@chengduainila/945 · this entry10 Aug 2026, 12:20 UTC1.0010 minutes
@yihaoxianbaogao/558428 Aug 2026, 03:34 UTC@chengduainila/999 · this entry28 Aug 2026, 03:52 UTC1.0019 minutes
@yihaoxianbaogao/636412 Nov 2026, 04:18 UTC@chengduainila/1221 · this entry12 Nov 2026, 07:44 UTC1.003.4 hours
@chengduainila/951 · this entry12 Aug 2026, 05:54 UTC@yihaoxianbaogao/536212 Aug 2026, 06:33 UTC0.8639 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
@yihaoxianbaogao5 (5/5 hand-verifiable sample passed)0.9739 minutes@yihaoxianbaogao (3–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. 3 of the 3 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 238 comparable posts for this entry, running 1 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

15,40536,63726,0216 August 202616 November 2026
67 measurements spanning 102 days, net +21,232. 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 12,220–39,822 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
16 Nov 2026, 21:0936,637+1,394
13 Nov 2026, 10:4735,243+628
10 Nov 2026, 23:3834,615+578
9 Nov 2026, 12:2134,037+448
8 Nov 2026, 05:1833,589+229
6 Nov 2026, 22:2533,360+222
6 Nov 2026, 00:1033,138+449
4 Nov 2026, 21:3932,689+668
3 Nov 2026, 18:4732,021+98
2 Nov 2026, 21:0931,923+354
1 Nov 2026, 22:2531,569+392
1 Nov 2026, 01:2731,177+285
30 Oct 2026, 22:4830,892+358
30 Oct 2026, 00:0930,534+443
29 Oct 2026, 00:5530,091+538
27 Oct 2026, 22:1029,553+560
26 Oct 2026, 18:5828,993+68
25 Oct 2026, 21:2628,925+377
24 Oct 2026, 21:1728,548+353
23 Oct 2026, 21:5628,195first reading

Engagement

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

ERR · 30 days
1.09%
avg views ÷ 36,637 subscribers
Avg views / post
399
70 posts measured
Reaction rate
0.192%
reactions ÷ views · ER floor
Posts in window
70
of 242 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 23 of 70 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 held242 (1 August 2026 – 17 November 2026)
Views total27,901
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 11:25 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
8
Links
996

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.

Reaction mix

56 reactions across 50 posts, in 4 distinct kinds. The most used accounts for 83.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4783.9%
👍610.7%
👏23.57%
👎11.79%

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 60 of the 242 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 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 242 most recent posts we hold, published 1 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: 0 of 70 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, 10:33 UTC24 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:小羊羊 【妹子车牌】:@YNAAAB21 【验证留名】:蜜雪冰城🥰 【人照得分】: 8.5 【颜值得分】: 8.5 【身材得分】: 8.5 【服务得分】: 8.5 【态度得分】: 9 【环境得分】: 9 【综合得分】: 8.67 【验证时间】:2026-11-17 【所在位置】:#天府一街 【修车水费】:#6P #9PP 【是否代聊】:#自聊 【身高体重】:身高161,体重45kg,身材匀称,屁股有肉感,正常肤色手感光滑,没有纹身 【妹子年龄】:26 【服务内容】:陪洗,调情,舌吻,ab面,69,口活,爱爱 【优点缺点】:优点:妹妹人妻感足,舌吻主动奔放,身材匀称皮肤光滑,服务态度真诚可贵,爱爱十分投入,享受其中配合默契,水多湿滑日感超级棒,缺点:一点不催,舍不得走 【过程描述】:{妹妹26岁,人妻感足,身高161,体重45kg,穿包臀裙高跟鞋前凸…

17 Nov 2026, 10:33 UTC22 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:雨薇 【妹子车牌】:@kkde24 【验证留名】:🈚 【人照得分】: 8.5 【颜值得分】: 8.5 【身材得分】: 9 【服务得分】: 8 【态度得分】: 8 【环境得分】: 9 【综合得分】: 8.5 【验证时间】:2026-11-17 【所在位置】:成华区王府井 【修车水费】:600/P 【是否代聊】:代聊 【身高体重】:160/90 【妹子年龄】:22 【服务内容】:帮洗、舔咪咪、口、 爱爱 【优点缺点】:优点:胸型好看,皮肤光滑,水多,日感佳,反馈诱人 缺点:服务偏简单,无舌无69 【过程描述】:{约课顺利,给代聊点赞,沟通丝滑,推门入室,老师热情招呼,人照相似8.8,自觉付水费闲聊几句,老师也刚入课室,空调已开启,随后双双脱衣进入浴室,洗漱擦干后,转战至床上…… 老师重庆人,颜值小乖,身材匀称,皮肤光滑,硬件挺不错的,态度还不错,…

17 Nov 2026, 06:18 UTC93 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:晨曦 【妹子车牌】:@chenxi5566 【验证留名】:Blake 【人照得分】: 7.5 【颜值得分】: 7.5 【身材得分】: 8 【服务得分】: 8 【态度得分】: 8 【环境得分】: 8 【综合得分】: 7.83 【验证时间】:2026-11-16 【所在位置】:高新区世纪城 【修车水费】:6 【是否代聊】:否 【身高体重】:165cm/55kg 【妹子年龄】:30+ 【服务内容】:陪洗,69,舔咪咪,无套口,ab 面,毒龙应该有我没喊老师搞 【优点缺点】:优点服务态度没问题。服务车,缺点年纪大了一点有点赘肉 【过程描述】:{和老师约的 6 点半,到了直接进去,地方有点绕开导航看了半天,进去洗澡,今天老师租的反正只能浴缸里面洗老师就没帮忙陪洗,当然了也很贴心的帮忙擦拭这些,随后老师就是服务服务的很到位 ab 面,舔咪咪,深喉口这些,老师服务完以…

16 Nov 2026, 17:38 UTC168 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:朵儿 【妹子车牌】:@huaduo592013 【验证留名】:Amy Scott 【人照得分】: 7.5 【颜值得分】: 7.5 【身材得分】: 7.5 【服务得分】: 7.5 【态度得分】: 8 【环境得分】: 8 【综合得分】: 7.67 【验证时间】:2026-11-17 【所在位置】:理工大学 【修车水费】:4/p 7/pp 【是否代聊】:自聊 【身高体重】:身高160,体重110斤 【妹子年龄】:22 【服务内容】:胸推,陪洗,口,舔胸 【优点缺点】:胸软屁股大 【过程描述】:{进门第一眼感觉老师就比较耐看,穿着黑色的情趣内衣,人照基本一致,老师帮洗,洗完在床上先是舔胸然后口,口的时候无尺感,还有舔蛋,老师口技很好,之后是胸推有润滑油非常有感觉,差不多戴套开始了,先是传教,老师配合度很高,胸手感非常好很软,之后女上和后入,背枪视角非常爽大屁股撞…

16 Nov 2026, 15:34 UTC202 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:桃子 【妹子车牌】:@Ttao510 【验证留名】:李才醒(炸号版) 【人照得分】: 8 【颜值得分】: 8 【身材得分】: 8 【服务得分】: 9 【态度得分】: 9 【环境得分】: 10 【综合得分】: 8.67 【验证时间】:2026-11-16 【所在位置】:牛王庙 【修车水费】:7p12pp 【是否代聊】:是 【身高体重】:167.102斤 【妹子年龄】:26 【服务内容】:陪洗,乳交,吸皮 【优点缺点】:优点:服务态度好,人很热情,胸大。缺点:不可以🐍,服务有待提高 【过程描述】:{约好时间,位置好找,教室安全,进门上楼都要扫码。见到老师,照片是本人,开了美颜。老师陪洗,人态度很好。老师主动换上情趣内衣,老师有一对e的大车灯,喜欢乳交的可以试一试。b面服务有吸皮,胸推。a面口活不错,可以乳交,老师不可以🐍。老师下面毛量适中,褐色小穴,很紧,水…

16 Nov 2026, 08:04 UTC202 views1 reactionsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:甜生生 【妹子车牌】:@YZS1245 【验证留名】:只想耍 【人照得分】: 8.5 【颜值得分】: 9 【身材得分】: 9 【服务得分】: 8.5 【态度得分】: 10 【环境得分】: 9 【综合得分】: 9 【验证时间】:2026-11-16 【所在位置】:天府二街 【修车水费】:6/9 【是否代聊】:否 【身高体重】:160/95斤 【妹子年龄】:26/27 【服务内容】:课本上都有,主推舌吻和胸推 【优点缺点】:这妹子情绪价值很高,很会哄人不冷场,缺点目前没 【过程描述】:{前两天就加了生生,工作日没时间上课,周末有空就果断约课。 教室比较安全,打开门见到生生就给我眼前一亮,是自己喜欢的款。跟着生生进门闲聊了几句,交了学费,然后坐在沙发上舌吻和挑逗了一会儿,生生一点都不抗拒。随后进入浴室洗澡,美女主动帮忙洗,洗的时候小弟弟一直敬礼,水中xiao感…

❤1

16 Nov 2026, 04:59 UTC192 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:思思 【妹子车牌】:@sisisisiyayaya 【验证留名】:霄 烬 【人照得分】: 9 【颜值得分】: 9 【身材得分】: 10 【服务得分】: 8.5 【态度得分】: 9 【环境得分】: 8.5 【综合得分】: 9 【验证时间】:2026-11-13 【所在位置】:文殊院 【修车水费】:10pp 【是否代聊】:自聊 【身高体重】:150 80 【妹子年龄】:20 【服务内容】:陪洗,无套口,爱爱,蛇 【优点缺点】:妹子很嫩,身材很好,胸型挺拔手感好,态度也很不错,中间休息不玩手机,日感强烈。 【过程描述】:{老师所在位置不能自己上去,是老师下来接的我,人照基本一致,很耐看的嫩妹。进门交完水费开始洗澡,身材很亮眼,胸型挺拔手感好,腰也很细。上床先蛇后口,然后老师女上,日感强烈,温暖湿润紧致。第一发结束后老师也没有玩手机,就爬在身上聊天,休息一会…

15 Nov 2026, 23:37 UTC197 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:浅浅 【妹子车牌】:@qianqian668669 【验证留名】:李 亦蜂 【人照得分】: 7 【颜值得分】: 5 【身材得分】: 6 【服务得分】: 6 【态度得分】: 6 【环境得分】: 8 【综合得分】: 6.33 【验证时间】:2026-11-16 【所在位置】:成华区猛追湾 【修车水费】:600p 【是否代聊】:自聊 【身高体重】:160,110斤左右,微胖 【妹子年龄】:25左右 【服务内容】:陪洗,口,舔胸 【优点缺点】:优点:胸型好,大,乳头也好看,会聊天! 缺点:稍微有点胖,大腿比较粗,肚子稍微有赘肉,下面有异味! 【过程描述】:{初遇老师,黑色情趣内衣。进屋后老师先收了水费!开始帮洗。简单洗洗后上床,言语间老师是云南人,之前做幼师的工作吧。少数名族,身材微胖,天然e奶,态度还可以,用心在服务。刚下水。服务质量不高。就口。舔舔。硬了带上…

15 Nov 2026, 23:37 UTC188 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:兮兮 【妹子车牌】:@xixi3838438 【验证留名】:李 亦蜂 【人照得分】: 7 【颜值得分】: 7 【身材得分】: 7 【服务得分】: 1 【态度得分】: 1 【环境得分】: 6 【综合得分】: 4.83 【验证时间】:2026-11-15 【所在位置】:牛王庙 【修车水费】:700p 【是否代聊】:代聊 【身高体重】:165,90左右比较苗条 【妹子年龄】:19左右 【服务内容】:直接昆,没服务 【优点缺点】:优点:身材可以,比较紧! 缺点:态度差,这也不行,那也不行,洗完澡直接日,日几就催完了没完了没!很不耐烦!🤣 【过程描述】:{跟代哥确定好时间,按时到达,代哥很是谨慎,没到一个地方都要拍照上图🤣 到达教室后就看见老师,老师165,90斤左右,看着身材还行,于是交了水费去洗澡,洗完出来老师已经准备好了,手臂上有纹身,胸很小只有a左右,但是…

14 Nov 2026, 15:25 UTC322 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:露露 【妹子车牌】:@sexybabycare6 【验证留名】:小钢炮 【人照得分】: 8.5 【颜值得分】: 8 【身材得分】: 8 【服务得分】: 8 【态度得分】: 8.5 【环境得分】: 8 【综合得分】: 8.17 【验证时间】:2026-11-14 【所在位置】:交子大道 【修车水费】:6P/9PP 【是否代聊】:代聊 【身高体重】:身高165 体重110斤 【妹子年龄】:25 【服务内容】:嫩妹服务,口,做爱 【优点缺点】:优点:态度好,有情绪价值,超级敏感,反馈好。缺点:服务少。 【过程描述】:{民宿房间环境还行,刚进门就给我讲刚经历的故事,人热情大方。简单洗漱后,开始服务,服务比较简单嫩妹三件套,妹妹不喜欢接吻,所以没有接吻,口活还行,口的深挺舒服的。女上位开始,很努力的摇摆,体力很快就不行了,还我开始发力,没想到妹妹居然是个超级敏感车…

14 Nov 2026, 06:33 UTC485 viewsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:卷卷 【妹子车牌】:@Melissa_Brown33 【验证留名】:白城 【人照得分】: 8.5 【颜值得分】: 7.5 【身材得分】: 7.5 【服务得分】: 9 【态度得分】: 9 【环境得分】: 9 【综合得分】: 8.42 【验证时间】:2026-11-14 【所在位置】:二仙桥 【修车水费】:370/口1次 手1次 480/口2次 【是否代聊】:否 【身高体重】:身高162 体重100斤 【妹子年龄】:37 【服务内容】:按摩 胸推 臀推 乳交 过水 漫游 口莎 毒龙 丝袜诱惑 【优点缺点】:老师半套导师,职业会所半套出身。态度非常好,为人和善,爱聊天,有邻家少妇,服务巴适,不催,无机车行为,情绪价值拉满 【过程描述】:{提前跟老师约好时间,顺利到达老师的教室。老师全程本人聊天,不带聊。位置也很好找,私密性不错。推门入室,老师邻家少妇的感觉…

14 Nov 2026, 06:14 UTC252 views1 reactionsread 17 November 2026

成都医科大学修车群专属报告 【妹子花名】:墨涵 【妹子车牌】:@amh521 【验证留名】:小鬼 【人照得分】: 8 【颜值得分】: 8 【身材得分】: 8 【服务得分】: 8.5 【态度得分】: 8.5 【环境得分】: 8.5 【综合得分】: 8.25 【验证时间】:2026-11-11 【所在位置】:西门金沙 【修车水费】:500p 【是否代聊】:自聊 【身高体重】:身高165 体重112 【妹子年龄】:28 【服务内容】:陪洗、胸推、69、舔咪咪、深喉、爱爱等 【优点缺点】:优点:态度可以,服务也不错,缺点:肚子有点赘肉,老师说前阵子长肥了 【过程描述】:{和老师约好时间,遥控上门后,开门第一眼就是一袭黑色情趣打扮的少御模样,看着还是挺有感觉,小坐一下交了水费就去洗澡。有一说一,老师洗的还是挺认真,前前后后,上上下下,谈话也非常愉快,轻松自在。然后擦了水,就来到了床上。老师问我要选择激情…

👏1

Showing the 12 most recent of 242 posts we hold for @chengduainila. 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 @chengduainila 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
10 October 2026
Most recent seen missing
10 October 2026
Median time before seen missing
21 hours
Seen missing in the last 30 days
0

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“成都医科大学报告榜单” (@chengduainila), 36,637 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/chengduainila.

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.