#频道互推 #相似推荐 ------------------------------ 📢 邵阳95👄榜 📢 昆明·凯迪拉克【验证公开榜】 📢 惠州太子宫 📢 重庆资源 📢 厦门佳人 📢 武汉红花 📢 南宁凤阁 📢 长春春风苑 📢 杭州大吉《日常与体验指南》 📢 DJ东南亚包厢上头舞曲专属 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
Signed SOSO搜搜

Channel
@jinhuaquanqu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
28,040subscribers
+10,111 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002429400562 |
|---|---|
| Type | Channel |
| Username | @jinhuaquanqu |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/jinhuaquanqu |
Other / unclassifiable — 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 87% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 13:05 | 28,040 | -511 |
| 7 Nov 2026, 07:46 | 28,551 | -145 |
| 6 Nov 2026, 08:19 | 28,696 | -140 |
| 5 Nov 2026, 10:26 | 28,836 | -95 |
| 4 Nov 2026, 08:06 | 28,931 | -119 |
| 3 Nov 2026, 06:50 | 29,050 | -130 |
| 2 Nov 2026, 03:30 | 29,180 | -145 |
| 1 Nov 2026, 00:06 | 29,325 | -128 |
| 31 Oct 2026, 02:00 | 29,453 | -182 |
| 30 Oct 2026, 02:27 | 29,635 | -236 |
| 28 Oct 2026, 23:15 | 29,871 | -50 |
| 28 Oct 2026, 00:59 | 29,921 | -72 |
| 26 Oct 2026, 23:21 | 29,993 | -160 |
| 25 Oct 2026, 22:56 | 30,153 | -23 |
| 25 Oct 2026, 01:57 | 30,176 | -62 |
| 24 Oct 2026, 01:47 | 30,238 | +25 |
| 22 Oct 2026, 22:06 | 30,213 | -73 |
| 21 Oct 2026, 21:11 | 30,286 | +164 |
| 20 Oct 2026, 19:49 | 30,122 | -84 |
| 19 Oct 2026, 15:59 | 30,206 | first reading |
145 posts held, back to 14 July 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 169 pages 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. It is computed over the 6 of 60 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 November 2026 |
|---|---|
| Posts held | 145 (14 July 2026 – 8 November 2026) |
| Views total | 21,541 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 05: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.
Measured directly from 25 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.
35 reactions across 15 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 35 | 100.0% |
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 31 of the 145 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 35 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 145 most recent posts we hold, published 14 July 2026 to 8 November 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.
Telegram’s own ‘edited’ marker: 0 of 60 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#频道互推 #相似推荐 ------------------------------ 📢 邵阳95👄榜 📢 昆明·凯迪拉克【验证公开榜】 📢 惠州太子宫 📢 重庆资源 📢 厦门佳人 📢 武汉红花 📢 南宁凤阁 📢 长春春风苑 📢 杭州大吉《日常与体验指南》 📢 DJ东南亚包厢上头舞曲专属 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
Signed SOSO搜搜
新人开开
Photo, posted without a caption
#频道互推 #相似推荐 ------------------------------ 📢 惠州.惠阳.大亚湾.淡水.惠城.惠东.博罗全区:TG群友 📢 苏州•苏妃阁 📢 北京首府 📢 北京便民 📢 大连•牡丹花 📢 杭州风情 📢 杭州美女府 📢 厦门圣殿 📢 绍兴外围💎绍兴约炮💎绍兴上门💎绍兴修车 📢 厦门风情 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
Signed SOSO搜搜
刷到一个频道后,通常还想找更多同类入口。 SOSO 精选频道会随机推荐一批已收录频道。 适合继续发现相近内容。 🔗 本频道专属邀请链接 https://t.me/sooo?start=autopromo_-1002429400562_7511552041_channels_2c04541c
Signed SOSO搜搜
横店 新人
横店 新人
Photo, posted without a caption
#东阳 #义乌 #金华婺城区 #孝顺 #傅村 #横店 #永康 开课中 联系 @miaomiao980
开课
👋 你好!我在使用 iMe — 它是 Telegram,拥有相同的聊天和联系人,但提供更多功能和工具! ⚡️ 加入 iMe: Android: https://play.google.com/store/apps/details?id=com.iMe.android iOS: https://apps.apple.com/us/app/ime-messenger/id1450480822
大胸开课 特价
Showing the 12 most recent of 145 posts we hold for @jinhuaquanqu. 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.
@jinhuaquanqu edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 24 posts on @jinhuaquanqu 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“金华全区认证榜” (@jinhuaquanqu), 28,040 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/jinhuaquanqu.
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.