Supergroup
合肥修车大队中转
@hf_xcdd
On this record: Growth · Engagement · Citations · Cite this entry
5,609members
+1,361 since we began measuring on 7 August 2026
290 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003767754241 |
|---|---|
| Type | Supergroup |
| Username | @hf_xcdd |
| Created | Between 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/hf_xcdd |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 4 Sept 2026, 06:01 | 5,609 | +154 |
| 1 Sept 2026, 02:49 | 5,455 | +138 |
| 31 Aug 2026, 19:49 | 5,317 | no change |
| 28 Aug 2026, 18:56 | 5,317 | +128 |
| 25 Aug 2026, 19:52 | 5,189 | +129 |
| 23 Aug 2026, 05:03 | 5,060 | +180 |
| 19 Aug 2026, 15:34 | 4,880 | +164 |
| 16 Aug 2026, 20:04 | 4,716 | +166 |
| 13 Aug 2026, 09:34 | 4,550 | +140 |
| 10 Aug 2026, 05:53 | 4,410 | +157 |
| 7 Aug 2026, 06:36 | 4,253 | +5 |
| 7 Aug 2026, 04:15 | 4,248 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 25 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@huishilig · 42,89123 posts柳州会所95甄选榜
@LZHS0772 · 25,35018 posts贵州联盟
@GuiZhouCN · 16,68414 posts兰州公开榜
@Tg730000_1 · 29,99514 posts江门【免费】资源
@gjmjamg · 27,70111 posts南通公开榜
@ntfpb · 16,72510 posts🏆 𝘽𝙍𝘼𝘽𝙐𝙎®杭州高端资源精选
@BRABUSPremiumHZ · 32,4888 posts常州🌳公开榜【2.0】
@czxlstl9 · 20,9918 posts南京公开榜
@NJGKB111 · 55,5327 posts福建（泉州厦门福州）车友总群公开榜
@Fjxiucheziyuan · 24,4276 posts江西赣州修车公开榜
@ganzhouGB · 11,2976 posts长沙打工人互助协会公开榜
@goupoyx · 18,2616 posts昆明电报群公开榜
@KMDBQGKB · 48,1256 posts南昌修车大队公开榜
@nanchangGA · 11,1516 posts珠海资源总榜
@ZH_ZZY · 34,7896 posts哈尔滨（驻凡学院）公开榜
@hrbylzl · 35,1135 posts成都总群公开
@olddriveGKB · 10,2095 posts三亚陵水老师公开榜 📢
@SanYaGkb · 26,4555 posts柳州公开资源总榜
@LZGKZB · 1,5842 posts宿州🌙公开榜
@suzhou2024 · 9,5132 posts西安公告榜【新人必读】
@XiAn_BG · 6,7072 posts盐城公告榜
@ycggb2 · 5,1552 posts上海修车指南公告频道
@shanghaixiu · 2,4161 post天津认证老师榜
@tianjinbang · 13,1261 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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“合肥修车大队中转” (@hf_xcdd), 5,609 members as measured 4 September 2026. Telegram Register, tgregister.com/channel/hf_xcdd.
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.