Telegram RegisterThe public register of Telegram
Telegram profile photo for 舞艺联盟备用②群

Channel

舞艺联盟备用②群

@wuyilianmengby2

On this record: Growth · Engagement · Posts · Citations · Cite this entry

9subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003525768719
TypeChannel
Username@wuyilianmengby2
Created13 April 2026measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/wuyilianmengby2

Growth

913117 August 2026 — 13 subscribers12 August 2026 — 13 subscribers20 August 2026 — 12 subscribers27 August 2026 — 11 subscribers5 September 2026 — 10 subscribers13 September 2026 — 9 subscribers7 August 202613 September 2026
6 measurements spanning 37 days, net -4. 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 8–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 09:169-1
5 Sept 2026, 17:0110-1
27 Aug 2026, 18:4511-1
20 Aug 2026, 04:4512-1
12 Aug 2026, 02:4613no change
7 Aug 2026, 11:3613first reading

Engagement

3 posts held, back to 13 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 13 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Apr 2026, 12:09 UTC3 viewsread 12 August 2026

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 Telegram中的唯一搜索引擎,以收录超600万频道和群组,超4亿条信息,av,社工库,pg,黑产,轰炸等应有尽有 回家入口 入口2

13 Apr 2026, 12:09 UTC3 viewsread 12 August 2026

想看片?看这里!没挂玩了?看这里 想看点平时tg找不到的?看这里! 想要推特福利姬的套图?看这里! 搜图片搜频道搜暗网搜免费直装搜特殊资源搜套图 点击解锁全新搜索体验 更多其他类型资源免费观看 https://t.me/gov_2B_Expose

Showing the 3 most recent of 3 posts we hold for @wuyilianmengby2. 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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“舞艺联盟备用②群” (@wuyilianmengby2), 9 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/wuyilianmengby2.

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.