Supergroup
深圳移动修车大队
@fdsdffdfsdd
On this record: Growth · Engagement · Citations · Cite this entry
35,911members
-5,120 since we began measuring on 6 August 2026
94 online right now
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001553041701 |
|---|---|
| Type | Supergroup |
| Username | @fdsdffdfsdd |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/fdsdffdfsdd |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 3 Sept 2026, 11:01 | 35,911 | -233 |
| 2 Sept 2026, 03:17 | 36,144 | -149 |
| 1 Sept 2026, 04:15 | 36,293 | -161 |
| 31 Aug 2026, 03:55 | 36,454 | -730 |
| 30 Aug 2026, 01:35 | 37,184 | -212 |
| 29 Aug 2026, 04:04 | 37,396 | -182 |
| 28 Aug 2026, 01:18 | 37,578 | -183 |
| 27 Aug 2026, 01:08 | 37,761 | -77 |
| 26 Aug 2026, 03:38 | 37,838 | -216 |
| 25 Aug 2026, 05:39 | 38,054 | -235 |
| 24 Aug 2026, 02:24 | 38,289 | -593 |
| 22 Aug 2026, 13:08 | 38,882 | -321 |
| 21 Aug 2026, 02:44 | 39,203 | -181 |
| 20 Aug 2026, 03:43 | 39,384 | -133 |
| 19 Aug 2026, 00:37 | 39,517 | -304 |
| 17 Aug 2026, 21:53 | 39,821 | -82 |
| 16 Aug 2026, 21:08 | 39,903 | -324 |
| 15 Aug 2026, 08:44 | 40,227 | -61 |
| 14 Aug 2026, 00:37 | 40,288 | -177 |
| 12 Aug 2026, 20:30 | 40,465 | first reading |
Engagement
No public post preview. We read this entry on 12 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 15 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.
@efsefer · 8,61928 posts移动体检报告榜
@ghfcyfytcvtf · 12,43211 posts福田名师·しよう 裸身疗愈抓龙筋SPA
@cc663766 · 5,0694 posts深圳移动精选榜
@hshsguh · 9,6782 posts南山 曦曦个人兼职
@xixi69007 · 1,1802 posts深圳光明小圆朋友圈
@chfy0586 · 2,2201 post罗湖MM岚岚姐
@frewqz · 6291 post广州佛山全部女神榜
@GJRTIYIU6 · 3691 post深圳全部女神榜
@GSYWHH · 4,3161 post琳琳的，后花园💋💋
@gzgzv666 · 6501 post新人，短期兼职
@hjfbfjfj · 9101 post深圳94–95-96
@szhsv66 · 9411 post深圳各区94-95-98水疗会所
@szjdh9598 · 3,1591 post深圳 南山 蜜桃私享の半裸 龙筋 SPA
@sztiantian0_0 · 6181 post天河溪溪个人相册
@xixinn188 · 1,1541 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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳移动修车大队” (@fdsdffdfsdd), 35,911 members as measured 3 September 2026. Telegram Register, tgregister.com/channel/fdsdffdfsdd.
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.