Telegram RegisterThe public register of Telegram
Telegram profile photo for 科技大学报告榜

Channel

科技大学报告榜

@nanningchep

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2,535subscribers

+531 since we began measuring on 21 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1004486620827
TypeChannel
Username@nanningchep
Created21 August 2026measured — dated from the channel’s first post
First recorded21 August 2026
Last confirmed live2 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/nanningchep

Growth

2,0042,5352,269.521 August 2026 — 2,004 subscribers22 August 2026 — 2,006 subscribers25 August 2026 — 2,254 subscribers27 August 2026 — 2,338 subscribers30 August 2026 — 2,427 subscribers2 September 2026 — 2,535 subscribers21 August 20262 September 2026
6 measurements spanning 12 days, net +531. 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 1,924–2,615 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 20:182,535+108
30 Aug 2026, 14:442,427+89
27 Aug 2026, 23:092,338+84
25 Aug 2026, 04:052,254+248
22 Aug 2026, 07:462,006+2
21 Aug 2026, 19:302,004first reading

Engagement

4 posts held, back to 21 August 2026the 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 · 30 days
0.723%
avg views ÷ 2,535 subscribers
Avg views / post
18.3
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 4 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 21 August 2026
Posts held4 (21 August 202621 August 2026)
Views total55
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Aug 2026, 19:30 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

Video runtime
1m 14s
Average length
1m 14s

Measured directly from 1 video 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

21 Aug 2026, 17:30 UTC28 viewsread 21 August 2026

南宁科技大学修车老师榜单 南宁科技大学修车公开群 南宁科技大学修车出击表 【验证留名】:匿名 【老师花名】:美嘉 【联系老师】:👉点击直达老师👈 【人照得分】:9 【颜值得分】:9 【身材得分】:8 【服务得分】:7 【态度得分】:9 【环境得分】:8 【验证时间】:2026-08-21 22:57:58 【过程描述】:跟老师约好时间就出击了,就是我是骑行过去的下雨了出了点小插曲,过去慢了老师也没有不耐烦,上去了网络不是很好兄弟们注意了。服务嘛还行就是没有陪洗,只能自己去浴室洗洗了,洗完躺下老师问我想怎么给你做服务,老师吹的有点生疏,因为老师刚做不太会需要调教,跟老师说办正事吧然后就开始了,传教士后入传教士,123 在抓着老师的D奶、销魂的叫声下发射了。总结老师很漂亮对版,没🐍没亲没69服务态度好,老师没有自己的飞机号 【综合评价】:中 【预约截图】:已上传 【报告提交】:@xiuchennbot

21 Aug 2026, 17:30 UTC22 viewsread 21 August 2026

南宁科技大学修车老师榜单 南宁科技大学修车公开群 南宁科技大学修车出击表 【验证留名】:114514 【老师花名】:小贝 【联系老师】:👉点击直达老师👈 【人照得分】:9 【颜值得分】:10 【身材得分】:9 【服务得分】:9 【态度得分】:9 【环境得分】:9 【验证时间】:2026-08-21 22:53:13 【过程描述】:最近几天终于有时间出击了,看到小贝老师频道照片十分不错果断拿下,约好时间,遥控上楼。进门眼前一亮,老师确实是有170,颜值和老师个人频道里的对版,穿了一身性感装,配上丝袜,加上一头长发,精致的脸庞,看的我内心砰砰直跳。虽然老师说话有些腼腆,确实是和之前有大哥说到的有一种邻家乖乖女的感觉,但也很贴心得递水聊天不冷场,嘴还是很甜的,宝贝宝贝的一直叫着。接之交水费后在等水热的时候就先来了个大蟒蛇,边洗边🐍,边摸着老师那两个不小的双峰。躺床上后又🐍了一遍,期间二弟一直挺着,很有感觉,之后就开始口了,老师口得确实

21 Aug 2026, 15:53 UTC5 viewsread 21 August 2026
Video

👆👆👆👆👆👆 车评提交教程视频 @xiuchennbot 车评报告在这个机器人这里提交,点进机器人输入关键词“写车评”然后输入老师的花名或者用户名即可给老师进行打分评价 有疑惑可联系管理: @Chongsglbot 交流群: 南宁修车官方大群

Showing the 4 most recent of 4 posts we hold for @nanningchep. 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.

Forward network

Republished by

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

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

“科技大学报告榜” (@nanningchep), 2,535 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/nanningchep.

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.