Telegram RegisterThe public register of Telegram
Telegram profile photo for 惠州工兵老师库

Channel

惠州工兵老师库

@GingBingbnag6

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

15,639subscribers

+62 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-1002187468423
TypeChannel
Username@GingBingbnag6
Description聊天群: @HZgb_1118 作业榜:https://t.me/RPzy_9 典藏库:https://t.me/HZgb_98
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 live17 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/GingBingbnag6

Growth

15,57715,63915,6087 August 2026 — 15,577 subscribers7 August 2026 — 15,579 subscribers8 August 2026 — 15,586 subscribers9 August 2026 — 15,589 subscribers10 August 2026 — 15,595 subscribers11 August 2026 — 15,602 subscribers12 August 2026 — 15,612 subscribers13 August 2026 — 15,621 subscribers15 August 2026 — 15,627 subscribers16 August 2026 — 15,632 subscribers17 August 2026 — 15,639 subscribers7 August 202617 August 2026
11 measurements spanning 11 days, net +62. 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 15,568–15,648 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 19:5315,639+7
16 Aug 2026, 15:0215,632+5
15 Aug 2026, 00:2615,627+6
13 Aug 2026, 15:2715,621+9
12 Aug 2026, 16:3415,612+10
11 Aug 2026, 15:2615,602+7
10 Aug 2026, 12:2515,595+6
9 Aug 2026, 09:5315,589+3
8 Aug 2026, 06:2115,586+7
7 Aug 2026, 07:4515,579+2
7 Aug 2026, 03:1515,577first reading

Engagement

30 posts held, back to 3 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 25 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.79%
avg views ÷ 15,639 subscribers
Avg views / post
906
30 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
30
of 30 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 17 August 2026
Posts held30 (3 August 202617 August 2026)
Views total27,176
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 06:20 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

Photos
363
Videos
82
Links
84

Lifetime counters from Telegram’s own channel header, read 18 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
2m 10s
Average length
10s

Measured directly from 13 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.

Recent posts

17 Aug 2026, 11:36 UTC568 viewsread 18 August 2026
Photo

💸花名:#小听 地点:#惠城 💸价格:600p 1200pp 💸联系:@Xt2608 💸服务:见课表【#入库】 💸优点分类: 💸缺点分类: 💸推荐意向: 💸详细报告: 返回目录

17 Aug 2026, 08:59 UTC626 viewsread 18 August 2026
Photo

💸花名:#纹纹 地点:#江北 💸价格:600p 1200pp 💸联系:@wenwen1681 💸服务:见课表【#入库】 💸优点分类:#嫩妹 #瘦底大波 💸缺点分类:#多给100➕🐍 💸推荐意向: 💸详细报告: 报告26.03.27 工兵评价-#乙- 报告26.03.27 工兵评价-#乙 报告265.03.21 工兵评价-#乙 返回目录

16 Aug 2026, 06:55 UTC860 viewsread 18 August 2026
Photo

💸花名:#南南 地点:#水口 💸价格:500p 1000pp 💸联系:@nannan8636 💸服务:https://t.me/nannan926 💸优点分类: 💸缺点分类: 💸推荐意向: 💸详细报告: 返回目录

16 Aug 2026, 03:48 UTC902 viewsread 18 August 2026
Photo

💸花名:#纯纯 地点:#惠城区 💸价格:700p 1400pp 💸联系:@Chunchuna 💸服务:见课表【#入库】 💸优点分类: 💸缺点分类: 💸推荐意向: 💸详细报告: 返回目录

15 Aug 2026, 08:54 UTC992 viewsread 18 August 2026
Photo

💸花名:#小柳岩 地点:#江北 💸价格:600p 1200pp 💸联系:@xiaoliuyanr 💸服务:见课表【#入库】 💸优点分类:#服务型 #配合度高 💸缺点分类:#不是嫩妹 💸推荐意向:#蛇教 💸详细报告: 报告26.04.16 工兵评价-#乙 报告2026.02.25 工兵评价-#乙 报告2026.02.11 工兵评价-#乙 报告2026.02.12 工兵评价-#乙 报告2026.02.12 工兵评价-#丙 返回目录

14 Aug 2026, 12:25 UTC≈1,140 viewsread 18 August 2026
Photo

💸花名:#瑶瑶 地点:#河南岸 💸价格:700p 1300pp 💸联系:@zxcvbnm136977 💸服务:见课表【#入库】 💸优点分类:#嫩妹 #皮肤白 #颜值高 💸缺点分类:#纹身多 💸推荐意向: 💸详细报告: 工兵报告乙- 工兵报告 乙 返回目录

14 Aug 2026, 10:48 UTC999 viewsread 16 August 2026
Photo

💸花名:#依依 地点:#惠城区 💸价格:600p 1200pp 💸联系:@Kabj67 💸服务:见课表【#入库】 💸优点分类: 💸缺点分类: 💸推荐意向: 💸详细报告: 返回目录

13 Aug 2026, 13:27 UTC≈1,100 viewsread 16 August 2026
Photo

💸花名:#火灵儿 地点:#惠城区 💸价格:700p 1400pp 💸联系:@Huolingera08 💸服务:见课表【#入库】 💸优点分类:#嫩妹 #3点粉 #颜值高 #无风尘感 💸缺点分类:#无服务 💸推荐意向: 💸详细报告: 报告26.08.14 工兵评价-#乙+ 报告26.08.14 工兵评价-#乙- 返回目录

12 Aug 2026, 09:52 UTC≈1,240 viewsread 15 August 2026
Photo

💸花名:#故人归 地点:#河南岸 💸价格:700p 1400pp 💸联系:@gurenqian 💸服务:见课表【#入库】 💸优点分类: 💸缺点分类: 💸推荐意向: 💸详细报告: 报告26.08.13 工兵评价-#乙+ 返回目录

12 Aug 2026, 09:06 UTC≈1,110 viewsread 15 August 2026
Photo

💸花名:#桃桃 地点:#江北 💸价格:600p 1200pp 💸联系:@taotao520123 💸服务:见课表【#入库】 💸优点分类: 💸缺点分类: 💸推荐意向: 💸详细报告: 返回目录

12 Aug 2026, 04:27 UTC820 viewsread 13 August 2026

🎉 工兵群白嫖活动 🎁 奖品清单 • 老师库/典藏任选P白嫖劵 × 1 • 口令红包100 × 1 • 口令红包100 × 1 🛡️ 参与条件 • 加入 惠州工兵群【禁广告】 • 加入 惠州工兵老师库 • 加入 惠州工兵锐评典藏榜 • 需消耗工兵蛋:88 • 参加抽奖后需在 惠州工兵群【禁广告】 内发言168次 └ 群内发送“抽奖进度”查看完成度(每日限5次) • 必须设置用户名 ⌛ 抽选时刻 • 2026-08-18 15:24:00 📜 抽奖说明 开课期间劵2天有效期,写报告,中奖直接联系老师! 此卷不可转让 不可出售 需本人出击 ✨ 愿命运之剑指引你们前行,直至胜利之光照耀每一个人。

11 Aug 2026, 16:23 UTC899 viewsread 13 August 2026
Photo

💸花名:#安安 地点:#惠城区 💸价格:700p 1300pp 💸联系:@anan52199 💸服务:见课表【#入库】 💸优点分类: 💸缺点分类: 💸推荐意向: 💸详细报告: 返回目录

Showing the 12 most recent of 30 posts we hold for @GingBingbnag6. 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 — 552,912 of 1,548,671entries 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.

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 1 registered channel — 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.

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

“惠州工兵老师库” (@GingBingbnag6), 15,639 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/GingBingbnag6.

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.