导航分类,点击直接跳转 公子 - 同学 - 公子2 - 同学2 点击直接跳转
Channel
公子/同学
@etrxd
On this record: Growth · Engagement · Posts · Citations · Cite this entry
5subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003768294971 |
|---|---|
| Type | Channel |
| Usernames | @etrxd @htrxw |
| Created | 21 April 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 14 August 2026 |
| On Telegram | t.me/etrxd |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 13:16 | 5 | no change |
| 13 Aug 2026, 09:33 | 5 | first reading |
Engagement
10 posts held, back to 21 April 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 2 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 791.4%
- avg views ÷ 5 subscribers
- Avg views / post
- 39.6
- 7 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 8
- of 10 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.
| Window | Rolling 30 days · latest post in window 19 July 2026 |
|---|---|
| Posts held | 10 (21 April 2026 – 19 July 2026) |
| Views total | 277 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 09:33 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.
Recent posts
1
同学2 @batongxue 138 八同学 @bentongxue 108 笨同学 @chuangtongxue 108 闯同学 @dietongxue 138 蝶同学 @kuangtongxue 168 狂同学 @pangtongxue 108 胖同学 🛫🛫🛫🛫 回到导航 🛫🛫🛫🛫
1
同学 @atongxue 168 阿同学 @baotongxue 138 宝同学 @beitongxue 138 北同学 @biantongxue 168 必安同学 @bingtongxue 138 冰同学 @bintongxue 138 斌同学 @botongxue 128 博同学 @butongxue 108 步同学 @cangtongxue 168 苍同学 @cantongxue 138 灿同学 @caotongxue 168 曹同学 @cengtongxue 138 曾同学 @chaitongxue 108 柴同学 @chetongxue 108 车同学 @chitongxue 108 驰同学 @chongtongxue 108 宠同学 @chuantongxue 168 川同学 @chuntongxue 108 纯同学 @chutongxue 168 楚同学 @congtongxue 138 聪同学 @cuito…
公子2 @anggongzi 108 昂公子 @aogongzi 168 敖公子 @benggongzi 108 蚌公子 @biaogongzi 108 表公子 @canggongzi 108 仓公子 @cegongzi 108 策公子 @cenggongzi 168 曾公子 @chagongzi 108 茶公子 @chaigongzi 138 柴公子 @chuogongzi 108 绰公子 @cigongzi 108 此公子 @conggongzi 168 聪公子 @cougongzi 108 凑公子 @cuangongzi 108 窜公子 @cuigongzi 168 崔公子 @danggongzi 138 荡公子 @diegongzi 108 叠公子 @digongzi 138 迪公子 @diugongzi 108 丢公子 @dougongzi 108 窦公子 @duigongzi 118 对公子 @dungong…
公子 @banggongzi 108 傍公子 @baogongzi 138 包公子 @biangongzi 108 扁公子 @bogongzi 108 波公子 @cangongzi 138 灿公子 @changongzi 108 馋公子 @chaogongzi 168 超公子 @chegongzi 138 车公子 @chigongzi 108 痴公子 @chonggongzi 108 宠公子 @chuaigongzi 108 踹公子 @chuanggongzi 108 闯公子 @chuangongzi 168 川公子 @chuigongzi 108 吹公子 @chungongzi 138 春公子 @cungongzi 108 村公子 @cuogongzi 108 挫公子 @dangongzi 108 单公子 @daogongzi 138 刀公子 @diangongzi 108 滇公子 @gagongzi 108 嘎公子 …
Channel name was changed to «公子/同学»
Channel name was changed to «@fchuai f踹»
Channel created
Showing the 10 most recent of 10 posts we hold for @etrxd. 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.
Citation-graph rank
Citation-graph rank — 2,698 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 2 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.
@cc4j4 · 31 postee7t7
@ee7t7 · 51 postgg3a3
@gg3a3 · 41 postgg4z4
@gg4z4 · 41 posthh8a8
@hh8a8 · 41 postjikenken
@jikenken · 31 postjj2d2
@jj2d2 · 41 postjj3m3
@jj3m3 · 51 postjj4s4
@jj4s4 · 31 postjjt2j
@jjt2j · 31 postmm1t1
@mm1t1 · 31 postmm6z6
@mm6z6 · 31 postnichunchun
@nichunchun · 41 postoo2j2
@oo2j2 · 31 postoo4j4
@oo4j4 · 31 postpeijuju
@peijuju · 31 postpp2r2
@pp2r2 · 51 postpp3r3
@pp3r3 · 31 postpp4q4
@pp4q4 · 31 postpp6o6
@pp6o6 · 31 postqq2a2
@qq2a2 · 31 postxx4w4
@xx4w4 · 31 postyy8g8
@yy8g8 · 31 postzz4b4
@zz4b4 · 31 post
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“公子/同学” (@etrxd), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/etrxd.
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.