Telegram RegisterThe public register of Telegram
Telegram profile photo for 衡阳老师真实反馈

Channel

衡阳老师真实反馈

@zfdit

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

23,661subscribers

+21,640 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002233850407
TypeChannel
Username@zfdit
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live28 October 2026
Measurements held47
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/zfdit

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 16 August 2026 and assigned it the closest of 31 fixed categories, at 60% 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.

Growth

2,021121,07161,5467 August 2026 — 2,021 subscribers7 August 2026 — 2,021 subscribers8 August 2026 — 2,022 subscribers11 August 2026 — 2,069 subscribers15 August 2026 — 13,833 subscribers16 August 2026 — 121,071 subscribers17 August 2026 — 118,955 subscribers18 August 2026 — 113,582 subscribers20 August 2026 — 113,210 subscribers20 August 2026 — 113,213 subscribers22 August 2026 — 113,235 subscribers24 August 2026 — 113,229 subscribers25 August 2026 — 113,261 subscribers26 August 2026 — 113,265 subscribers27 August 2026 — 113,276 subscribers28 August 2026 — 113,298 subscribers29 August 2026 — 114,982 subscribers30 August 2026 — 118,728 subscribers31 August 2026 — 117,453 subscribers1 September 2026 — 113,550 subscribers2 September 2026 — 113,531 subscribers3 September 2026 — 113,530 subscribers5 September 2026 — 113,531 subscribers9 September 2026 — 113,536 subscribers11 September 2026 — 113,555 subscribers13 September 2026 — 113,557 subscribers15 September 2026 — 111,568 subscribers17 September 2026 — 70,350 subscribers25 September 2026 — 62,735 subscribers3 October 2026 — 44,081 subscribers8 October 2026 — 31,712 subscribers12 October 2026 — 25,496 subscribers14 October 2026 — 24,732 subscribers15 October 2026 — 24,499 subscribers16 October 2026 — 24,441 subscribers17 October 2026 — 24,436 subscribers18 October 2026 — 24,405 subscribers19 October 2026 — 24,389 subscribers20 October 2026 — 24,362 subscribers21 October 2026 — 24,250 subscribers22 October 2026 — 24,152 subscribers23 October 2026 — 24,122 subscribers24 October 2026 — 24,070 subscribers25 October 2026 — 24,058 subscribers26 October 2026 — 23,979 subscribers27 October 2026 — 23,829 subscribers28 October 2026 — 23,661 subscribers23,6617 August 202628 October 2026
47 measurements spanning 82 days, net +21,640. 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 47
Measured (UTC)SubscribersChange
28 Oct 2026, 18:1023,661-168
27 Oct 2026, 15:5423,829-150
26 Oct 2026, 16:5623,979-79
25 Oct 2026, 15:2724,058-12
24 Oct 2026, 16:2524,070-52
23 Oct 2026, 13:5524,122-30
22 Oct 2026, 14:0924,152-98
21 Oct 2026, 06:0024,250-112
20 Oct 2026, 05:2924,362-27
19 Oct 2026, 03:2024,389-16
18 Oct 2026, 04:3024,405-31
17 Oct 2026, 06:3024,436-5
16 Oct 2026, 07:5524,441-58
15 Oct 2026, 10:2824,499-233
14 Oct 2026, 09:4624,732-764
12 Oct 2026, 21:3925,496-6,216
8 Oct 2026, 13:3831,712-12,369
3 Oct 2026, 23:4044,081-18,654
25 Sept 2026, 02:4262,735-7,615
17 Sept 2026, 04:5870,350first reading

Engagement

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

ERR · 30 days
1.50%
avg views ÷ 23,661 subscribers
Avg views / post
355
84 posts measured
Reaction rate
0.094%
reactions ÷ views · ER floor
Posts in window
84
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 22 of 84 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 27 October 2026
Posts held242 (6 August 2026 – 27 October 2026)
Views total29,820
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Oct 2026, 06:12 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.

Reaction mix

52 reactions across 30 posts, in 10 distinct kinds. The most used accounts for 55.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2955.8%
😇47.69%
😴47.69%
👌35.77%
👍35.77%
🤗35.77%
🔥23.85%
🤩23.85%
💯11.92%
😎11.92%

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 59 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 52 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 6 August 2026 to 27 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

27 Oct 2026, 16:17 UTC159 viewsread 28 October 2026
Photo

#糖果 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

27 Oct 2026, 12:35 UTC201 views0 reactionsread 28 October 2026
Photo

#苏妲己 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

27 Oct 2026, 12:23 UTC218 views0 reactionsread 28 October 2026
Photo

#苏妲己 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

26 Oct 2026, 18:39 UTC320 viewsread 28 October 2026
Photo

#杨幂 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

26 Oct 2026, 16:22 UTC309 viewsread 28 October 2026
Photo

#林夕 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

26 Oct 2026, 08:41 UTC315 viewsread 28 October 2026
Photo

#林夕 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

26 Oct 2026, 07:14 UTC302 viewsread 28 October 2026

⚠️⚠️防骗指南⚠️⚠️ ⚠️不要相信群里个人老师广告,百分之百都是骗子 ⚠️主动私聊大部分是骗子 ⚠️不要相信带你赚钱的,百分百骗子 ⚠️不要相信任何群里面教你 们去下个钱包,转U币,99%是骗子 ⚠️有人冒充衡阳各大群主骗钱,不要相信任何人,不要给任何人转钱,任何群的群主都不会向客人借钱 ⚠️聊天群频繁改名的,需要谨慎,大部分是骗子 ⚠️需要交押金的,需要谨慎,大部分是骗子 ⚠️卖资源的99%不可靠 ⚠️本人只有一个聊天群,请认准我账号,@Azhangfei 以免碰上杀猪盘

25 Oct 2026, 18:37 UTC337 viewsread 28 October 2026
Photo

#夏冰 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

25 Oct 2026, 16:34 UTC330 viewsread 28 October 2026
Photo

#波浪 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

25 Oct 2026, 14:33 UTC320 viewsread 27 October 2026
Photo

#林夕 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

24 Oct 2026, 15:50 UTC460 viewsread 27 October 2026
Photo

#杨幂 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

23 Oct 2026, 12:31 UTC502 views0 reactionsread 26 October 2026
Photo

#纯酱 咨询 @Azhangfei 聊天群 @XD884899 课表 @th0734 双向限制联系 @xlth168_bot

Showing the 12 most recent of 242 posts we hold for @zfdit. 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.

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.

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

“衡阳老师真实反馈” (@zfdit), 23,661 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/zfdit.

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.