Telegram RegisterThe public register of Telegram
Telegram profile photo for 上师大资源总榜(2.0版)

Channel

上师大资源总榜(2.0版)

@ssdwyzls

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

787subscribers

-17,656 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002581125931
TypeChannel
Username@ssdwyzls
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 live18 November 2026
Measurements held42
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/ssdwyzls

Topic

Giveaways & airdrops — 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 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. This entry also forms a group of 2 channels linked by matching posts. 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
@ssdwyzls/2006 · this entry1 Sept 2026, 10:37 UTC@nmsbg/5421 Sept 2026, 14:35 UTC1.004.0 hours
@ssdwyzls/2009 · this entry1 Sept 2026, 11:55 UTC@nmsbg/5361 Sept 2026, 11:55 UTC1.00under a minute
@ssdwyzls/2012 · this entry2 Sept 2026, 10:38 UTC@nmsbg/5432 Sept 2026, 10:38 UTC1.00under a minute
@ssdwyzls/2212 · this entry26 Sept 2026, 10:16 UTC@nmsbg/56426 Sept 2026, 10:16 UTC1.00under a minute
@ssdwyzls/2246 · this entry28 Sept 2026, 10:13 UTC@nmsbg/57228 Sept 2026, 10:13 UTC1.00under a minute
@ssdwyzls/2249 · this entry29 Sept 2026, 09:56 UTC@nmsbg/57529 Sept 2026, 09:56 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
@nmsbg15 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–7)

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. 7 of the 7 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 31 comparable posts for this entry, running 4 August 2026 to 15 October 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 2 channels, the one whose matching posts we hold earliest is @ssdwyzls — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 19 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 2 registered channels linked by matching posts. 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

78730,16315,4756 August 2026 — 18,443 subscribers7 August 2026 — 18,462 subscribers8 August 2026 — 18,602 subscribers9 August 2026 — 18,652 subscribers10 August 2026 — 18,680 subscribers11 August 2026 — 18,712 subscribers12 August 2026 — 18,753 subscribers13 August 2026 — 19,243 subscribers14 August 2026 — 19,665 subscribers16 August 2026 — 19,757 subscribers17 August 2026 — 19,862 subscribers18 August 2026 — 19,906 subscribers19 August 2026 — 19,954 subscribers20 August 2026 — 20,031 subscribers21 August 2026 — 20,157 subscribers22 August 2026 — 20,700 subscribers24 August 2026 — 21,117 subscribers25 August 2026 — 21,495 subscribers26 August 2026 — 21,779 subscribers27 August 2026 — 22,099 subscribers28 August 2026 — 22,395 subscribers29 August 2026 — 22,720 subscribers30 August 2026 — 22,905 subscribers31 August 2026 — 23,151 subscribers1 September 2026 — 23,387 subscribers2 September 2026 — 23,635 subscribers3 September 2026 — 23,942 subscribers5 September 2026 — 24,656 subscribers8 September 2026 — 25,670 subscribers11 September 2026 — 26,172 subscribers13 September 2026 — 26,282 subscribers14 September 2026 — 26,427 subscribers16 September 2026 — 26,642 subscribers18 September 2026 — 26,897 subscribers25 September 2026 — 27,741 subscribers3 October 2026 — 29,012 subscribers8 October 2026 — 29,233 subscribers12 October 2026 — 29,848 subscribers14 October 2026 — 30,009 subscribers15 October 2026 — 30,074 subscribers16 October 2026 — 30,163 subscribers18 November 2026 — 787 subscribers6 August 202618 November 2026
42 measurements spanning 104 days, net -17,656. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
18 Nov 2026, 15:35787-29,376
16 Oct 2026, 09:3630,163+89
15 Oct 2026, 08:3630,074+65
14 Oct 2026, 10:3130,009+161
12 Oct 2026, 20:5829,848+615
8 Oct 2026, 11:1529,233+221
3 Oct 2026, 20:2129,012+1,271
25 Sept 2026, 03:0127,741+844
18 Sept 2026, 20:0126,897+255
16 Sept 2026, 14:5926,642+215
14 Sept 2026, 20:4126,427+145
13 Sept 2026, 07:1526,282+110
11 Sept 2026, 07:3926,172+502
8 Sept 2026, 13:0225,670+1,014
5 Sept 2026, 03:5724,656+714
3 Sept 2026, 10:2723,942+307
2 Sept 2026, 04:0223,635+248
1 Sept 2026, 02:0823,387+236
31 Aug 2026, 04:4823,151+246
30 Aug 2026, 05:1822,905first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 50 posts for this entry, the most recent from 15 October 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 59s
Average length
7s

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

34 reactions across 18 posts, in 2 distinct kinds. The most used accounts for 97.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3397.1%
😁12.94%

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

Measured over the 50 most recent posts we hold, published 4 August 2026 to 15 October 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

15 Oct 2026, 13:48 UTC368 views0 reactionsread 16 October 2026
Photo

🎰 思思福利活动 📮 参与条件: 🪪 必须设置用户名 🎫 加入-苗苗的后花园 🎫 加入-上海师范大学(聊天版) └ 🔑 发送口令﹝我爱苗苗﹞ 🎫 加入-上师大资源总榜(2.0版) 🎫 加入-上师大报告榜 🎫 加入-上海师范大学 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ pp优惠券200 × 10 💰️ p优惠券100 × 6 ⚠️ 抽奖说明: ❶中奖后把中奖截图发送给老师兑奖和约课(需要提交报告) ❷白嫖卷/半价卷/优惠卷中奖需要提交报告,优惠卷时效为3天有效,超时作废没有提交报告直接踢出本群 ❸优惠卷禁止转让和买卖发现直接踢出本群 ❹遇到老师红休,老师红休结束在约课,群内不支持找理由不去使用优惠卷 ❺注销账号、退群、炸号优惠卷全部回收以及中奖不去的。 📅 开奖日期:(北京时间) 2026年10月17日 21时48分00秒

15 Oct 2026, 08:48 UTC367 viewsread 16 October 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H179187835922 🎰 上师大婷婷优惠福利 ⚠️ 抽奖说明: ❶中奖后把中奖截图发送给老师兑奖和约课(需要提交报告) ❷白嫖卷/半价卷/优惠卷中奖需要提交报告,优惠卷时效为3天有效,超时作废没有提交报告直接踢出本群 ❸优惠卷禁止转让和买卖发现直接踢出本群 ❹遇到老师红休,老师红休结束在约课,群内不支持找理由不去使用优惠卷 ❺注销账号、退群、炸号优惠卷全部回收以及中奖不去的。 💁 参与情况:2达标 / 5报名 🔋 人品加成:0票 ⚡️× 9 🎅 联系领奖:@Ting123660 1. YYY YYY 奖品:300优惠劵 祝大家心想事成好运连连!

13 Oct 2026, 08:16 UTC555 views1 reactionsread 16 October 2026
Photo

🥐艺名:#小雪 📱地址:#浦东 😦费用:#800p #1600pp 🏷标签:#嫩妹 📱联系:@shaixiaoxue 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜 【工兵名额】: 剩余2 名额 【工兵优惠】: #400p #800pp 1、群里发送“工兵”获取优惠模板和100探路值截图,发送给客服 2、复制工兵模板和探路值截图发送客服 @ndnxms_bot 报名,先到先得 3、工兵报名成功需72小时内出击并出报告,未按时出击或未出报告将被移除群聊并挂黑名单

❤1

12 Oct 2026, 12:48 UTC597 views2 reactionsread 16 October 2026
Photo

🥐艺名:#桃喜 📱地址:#奉贤 😦费用:#1000p #1800pp 🏷标签:#御姐 📱联系:@momo36d 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜

❤2

12 Oct 2026, 12:31 UTC526 views0 reactionsread 16 October 2026
Photo

🥐艺名:#彩灯 📱地址:#嘉定 😦费用:#600p #1000pp 🏷标签:#御姐 📱联系:@yaoyao666789 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜

12 Oct 2026, 12:14 UTC403 views0 reactionsread 15 October 2026
Photo

🥐艺名:#TS彤彤(男娘) 📱地址:#静安 😦费用:#1000p #1500pp 🏷标签:#男娘 📱联系:@tstt123 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜

12 Oct 2026, 11:24 UTC209 views1 reactionsread 13 October 2026
Photo

🥐艺名:#婷婷 📱地址:#浦东 😦费用:#1200p #2200pp 🏷标签:#嫩妹 📱联系:@Ting123660 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜

❤1

12 Oct 2026, 02:20 UTC79 viewsread 12 October 2026
Photo

🥐艺名:#彭佳丽 📱地址:#普陀 😦费用:#800p #1500pp 🏷标签:#御姐 📱联系:@pengjiali6688 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜

11 Oct 2026, 15:49 UTC203 viewsread 12 October 2026
Photo

🥐艺名:#苗苗 📱地址:#浦东 😦费用:#500p #900pp 🏷标签:#御姐 📱联系:@BBGG0438 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜

10 Oct 2026, 14:56 UTC456 views1 reactionsread 12 October 2026
Photo

🥐艺名:#娇娇 📱地址:#浦东 😦费用:#600p #1200pp 🏷标签:#御姐 📱联系:@shjjioajiao 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜 【工兵名额】: 剩余3 名额 【工兵优惠】: #300p #600pp 1、群里发送“工兵”获取优惠模板和100探路值截图,发送给客服 2、复制工兵模板和探路值截图发送客服 @ndnxms_bot 报名,先到先得 3、工兵报名成功需72小时内出击并出报告,未按时出击或未出报告将被移除群聊并挂黑名单

❤1

9 Oct 2026, 06:17 UTC652 viewsread 12 October 2026
Photo

🥐艺名:#小青 📱地址:#浦东 😦费用:#600p #1200pp 🏷标签:#御姐 📱联系:@shxiaoqingxq 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜 【工兵名额】: 剩余3 名额 目前剩余2 【工兵优惠】: #300p #600pp 1、群里发送“工兵”获取优惠模板和100探路值截图,发送给客服 2、复制工兵模板和探路值截图发送客服 @ndnxms_bot 报名,先到先得 3、工兵报名成功需72小时内出击并出报告,未按时出击或未出报告将被移除群聊并挂黑名单

8 Oct 2026, 12:02 UTC640 views0 reactionsread 11 October 2026
Photo

🥐艺名:#沐卿 📱地址:#杨浦 😦费用:#600p #1200pp 🏷标签:#御姐 📱联系:@mmmuqing 📣上海师范大学福利聊天群 🏝公开榜|报告榜|公告榜

Showing the 12 most recent of 50 posts we hold for @ssdwyzls. 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 6 posts on @ssdwyzls 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
12 August 2026
Most recent seen missing
15 October 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
0

Mentions

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

“上师大资源总榜(2.0版)” (@ssdwyzls), 787 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/ssdwyzls.

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.