Supergroup
海南独立团·三亚海口交流群
@dulituan001
On this record: Growth · Engagement · Citations · Cite this entry
18,537members
+2,052 since we began measuring on 11 August 2026
11 online right now
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002103295188 |
|---|---|
| Type | Supergroup |
| Username | @dulituan001 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/dulituan001 |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 2 Sept 2026, 20:53 | 18,537 | +64 |
| 1 Sept 2026, 22:47 | 18,473 | +122 |
| 1 Sept 2026, 01:08 | 18,351 | +171 |
| 31 Aug 2026, 03:17 | 18,180 | -150 |
| 30 Aug 2026, 02:58 | 18,330 | +112 |
| 28 Aug 2026, 23:47 | 18,218 | +163 |
| 27 Aug 2026, 22:49 | 18,055 | +163 |
| 27 Aug 2026, 00:13 | 17,892 | +179 |
| 25 Aug 2026, 23:23 | 17,713 | +299 |
| 25 Aug 2026, 02:24 | 17,414 | -33 |
| 23 Aug 2026, 14:38 | 17,447 | +266 |
| 21 Aug 2026, 21:54 | 17,181 | +198 |
| 20 Aug 2026, 17:36 | 16,983 | +257 |
| 19 Aug 2026, 20:53 | 16,726 | +130 |
| 18 Aug 2026, 22:06 | 16,596 | +183 |
| 18 Aug 2026, 09:27 | 16,413 | no change |
| 18 Aug 2026, 00:12 | 16,413 | +179 |
| 16 Aug 2026, 22:27 | 16,234 | +212 |
| 15 Aug 2026, 16:37 | 16,022 | +141 |
| 14 Aug 2026, 07:05 | 15,881 | first reading |
Engagement
No public post preview. We read this entry on 18 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 16 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.
@HNPBT_5 · 3,9716 posts🇨🇳 中文联盟
@CN_Car · 53,0134 posts福州公开榜（认证老师榜）
@fuzhou222 · 12,0282 posts绵阳-故事汇公开榜
@aqbaogao · 17,2781 post长春站【东北学生会】
@ccjy0431 · 28,0851 post大连线下频道
@dlyp6 · 46,0421 post桂林群花坊
@glgkb · 21,1941 post遵义仁怀🅥资源榜
@gylmzyb · 14,8721 post贵阳玫瑰山庄🅥认证榜
@gymgrzb · 11,4951 post海南独立团老师榜
@HBPBT_8 · 21,6971 post兰州炮兵团新公开榜总榜
@PBT_2 · 13,5461 post沈阳公开榜（辽宁）
@shenyanggk · 30,6191 post天津意风广播台
@tianjingk · 42,4211 post西宁炮兵团公开榜
@Xnth586 · 14,0611 post扬州泰州呱呱叫—楼凤总榜单【已验证区】
@yangzhouhaige98 · 27,6711 post郑州烩面馆公开榜
@zzyx18 · 36,0151 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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“海南独立团·三亚海口交流群” (@dulituan001), 18,537 members as measured 2 September 2026. Telegram Register, tgregister.com/channel/dulituan001.
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.