Supergroup
武汉会所交流群
@GHNB88
On this record: Growth · Engagement · Citations · Cite this entry
13,253members
-1,319 since we began measuring on 7 August 2026
1,593 online right now
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002965856077 |
|---|---|
| Type | Supergroup |
| Username | @GHNB88 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/GHNB88 |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 6 Sept 2026, 15:41 | 13,253 | -45 |
| 4 Sept 2026, 03:40 | 13,298 | -23 |
| 2 Sept 2026, 17:42 | 13,321 | -79 |
| 1 Sept 2026, 15:08 | 13,400 | -65 |
| 31 Aug 2026, 15:46 | 13,465 | -21 |
| 30 Aug 2026, 13:54 | 13,486 | -42 |
| 29 Aug 2026, 17:05 | 13,528 | -99 |
| 28 Aug 2026, 17:53 | 13,627 | -12 |
| 27 Aug 2026, 17:07 | 13,639 | -20 |
| 26 Aug 2026, 19:38 | 13,659 | -63 |
| 25 Aug 2026, 23:11 | 13,722 | -19 |
| 24 Aug 2026, 22:02 | 13,741 | -70 |
| 23 Aug 2026, 09:47 | 13,811 | -10 |
| 21 Aug 2026, 21:07 | 13,821 | -16 |
| 20 Aug 2026, 19:35 | 13,837 | -6 |
| 19 Aug 2026, 21:05 | 13,843 | -7 |
| 19 Aug 2026, 18:01 | 13,850 | no change |
| 18 Aug 2026, 21:54 | 13,850 | +8 |
| 18 Aug 2026, 01:12 | 13,842 | -62 |
| 16 Aug 2026, 22:34 | 13,904 | first reading |
Engagement
No public post preview. We read this entry on 19 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
Mentions
Named by 14 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.
@wuhanhu0 · 9,2397 posts武汉出击资源
@jljri · 58,8066 posts武汉认证榜
@LG88995 · 36,0904 posts武汉认证资源
@cph996 · 37,9233 posts武汉黄金楼资源榜
@whhhl01 · 43,2793 posts🚙武汉曝光/打窝🚙
@hijackcar · 5,4912 posts武汉股神
@gpttzt · 7,0641 postTGBot_Lottery抽奖频道🎗
@tgbot_lottery · 14,6741 post武汉寻花问柳
@tsukiakira1025 · 9,0361 post武汉骑士榜（突击版）
@WHDTHYXCBB · 28,5401 post武汉会所榜
@WHJEHDB6 · 1,0981 post武汉少女诗集2.0
@whsnsj8 · 7,1561 post🅥 武汉老师榜 🅥
@wuhanhua1 · 98,7291 post武汉修车公开榜
@zqylzy01 · 15,7811 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“武汉会所交流群” (@GHNB88), 13,253 members as measured 6 September 2026. Telegram Register, tgregister.com/channel/GHNB88.
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.