Telegram RegisterThe public register of Telegram
Telegram profile photo for 明明就

Channel

明明就

@shuaji6

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

807subscribers

-45 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001920482448
TypeChannel
Username@shuaji6
Created23 June 2023measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live5 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/shuaji6

Growth

807852829.58 August 2026 — 852 subscribers8 August 2026 — 852 subscribers15 August 2026 — 842 subscribers23 August 2026 — 823 subscribers29 August 2026 — 812 subscribers5 September 2026 — 807 subscribers8 August 20265 September 2026
6 measurements spanning 28 days, net -45. 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 800–859 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 15:01807-5
29 Aug 2026, 15:33812-11
23 Aug 2026, 09:43823-19
15 Aug 2026, 01:53842-10
8 Aug 2026, 18:32852no change
8 Aug 2026, 09:05852first reading

Engagement

9 posts held, back to 23 June 2023the 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 9 posts for this entry, the most recent from 9 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

9 Apr 2026, 15:15 UTC145 viewsread 8 August 2026

全网No.1最高价!招租闲鱼号!🙂 😀😀😀😀 ⚡️租号 日结⚡️⚡️ 🟣直登价格: 🟢鱼力值400+ (200元) 🟢鱼力值421+(250元) 🟢鱼力值501+(260元) 🟢鱼力值601+(320元) 🟢鱼力值701+ (588元) 要求:【可以发作品,实名号,鱼力值400+,🈲:捣乱,私自下课不给予结算】 做单客服 @QQhc22

9 Apr 2026, 15:13 UTCviews —

明明就 pinned «wx QQ 闲鱼 出租dd 稳定bc盘口 价格优美 稳定结账不跑路 联系d @QQhc22»

9 Apr 2026, 15:13 UTC144 viewsread 8 August 2026

🐧 租QQ 来号啦!🎉 💵价格如下: 星星⭐️ 30 月亮🌙 60 单太阳☀️ 80 双太阳☀️☀️ 90 三太阳☀️☀️☀️ 110 皇冠👑 140 满3奖励 ¥25.8🧧 满5奖励 ¥60.8 🧧 满10奖励 ¥118.8 元🧧 做单客服 @QQhc22

9 Apr 2026, 15:12 UTC144 viewsread 8 August 2026

wx QQ 闲鱼 出租dd 稳定bc盘口 价格优美 稳定结账不跑路 联系d @QQhc22

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“明明就” (@shuaji6), 807 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/shuaji6.

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.