Channel
@SHssdbgb
On this record: Growth · Engagement · Posts · Citations · Cite this entry
240subscribers
+195 since we began measuring on 2 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003902730613 |
|---|---|
| Type | Channel |
| Username | @SHssdbgb |
| Created | 1 September 2026 — measured — dated from the channel’s first post |
| First recorded | 2 September 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/SHssdbgb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 20:18 | 240 | +195 |
| 2 Sept 2026, 11:15 | 45 | no change |
| 2 Sept 2026, 11:00 | 45 | first reading |
4 posts held, back to 1 September 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 1 page of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 4 (1 September 2026 – 2 September 2026) |
| Views total | 171 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 11:15 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.
🎰 上师大现金红包抽奖 📮 参与条件： 🪪 必须设置用户名 🎫 加入-上师大报告榜 🎫 加入-上师大工兵福利优惠区 🎫 加入-上海师范大学（聊天版） └ 🎟️ 发言数大于 3 条 🎫 加入-上师大资源总榜（重生2.0版） 🎫 加入-上师大商家榜 🎫 加入-上海师范大学 └ 🔑 发送口令﹝我爱上师大﹞ ❗ 口令提示： 请先参与抽奖，再发送口令激活 🎁 奖品内容： 💰️ 20现金红包 × 5 ⚠️ 抽奖说明： 24小时领取，超时作废 🔋 人品加成：⚡️× 9 规则 📅 开奖日期：(北京时间) 2026年09月05日 18时37分00秒
以前报告全部清空了现在重新收录新报告
上师大报告展示栏 https://t.me/+lAmPudguj_hjZWNh 报告提交处：@ndnxms_bot 【妹妹花名】：#+老师花名 【妹妹联系】：@+老师用户名 【报告署名】：自己名字 【验证时间】：日期 【验证地点】：哪个区，或哪个地标即可 【服务类别】：95（中项）还是98（大项），如果是莞式全套请注明 【修车水费】：1000p或500kb 【妹妹类型】：服务型少妇/颜值系嫩妹/女友型/大长腿御姐等等，说清楚风格即可 【颜值身材】： ｛年龄｝：目测 ｛颜值｝：与照片视频相似度，简单描述 ｛皮肤｝：黄皮/白皮/偏黑？皮肤状态怎么样？有无可疑皮肤病？有无纹身？ ｛罩杯｝：目测即可，胸型如何？科技胸务必注明 ｛身高｝：目测即可 ｛体重｝：目测即可，看不准就说下胖瘦 ｛赘肉｝：腹部，腰间，手臂，大腿等部位有无赘肉 ｛颜值综合打分｝：10分 ｛身材综合打分｝：10分 【服务质量】： ｛服务内容｝：简述，与课表相比有…
Channel created
Showing the 4 most recent of 4 posts we hold for @SHssdbgb. 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.
Named by 4 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“上师大报告榜” (@SHssdbgb), 240 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/SHssdbgb.
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.