1

Channel
防诈频道‼️‼️‼️
@yyyguaiguai
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 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 | -1002938926984 |
|---|---|
| Type | Channel |
| Username | @yyyguaiguai |
| Created | 16 October 2025 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/yyyguaiguai |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 01:16 | 1 | no change |
| 7 Aug 2026, 17:30 | 1 | first reading |
Engagement
12 posts held, back to 16 October 2025 — the 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 12 posts for this entry, the most recent from 16 October 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Videos
- 6
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 10m 23s
- Average length
- 5m 12s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
哈喽
#柬埔寨 柬媒最新消息称,昨晚金边钻石天空被抓人员超过300人,另外我今天听到一点小道消息,说天空这次被扫,是因为下面小弟乱搞,绑了另外大老板的小弟搞钱,然后那边大老板很生气,就找了关系,然后,就有了突袭行动。 频道广告独家赞助商 ——————————————— ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡⚡️⚡️⚡️ 玩U投,上TG!大额无忧 全网首发 注册就送神秘彩金 每日以小博大 业界龙头 网投领导者 欢迎各位盘总来操 首存送 复存送 充值笔笔赠送3️⃣🔤
#网友爆料:木牌园区的注意了,现在过去了很多执法警车。马上要进园区了。 ——————————————— 🔔 订阅东南亚大事件-柬埔寨曝光 🔗 t.me/+AWEJzD5o4nthODQ1 ☎️ 欢迎投稿爆料:@Bnnc888
Sticker, posted without a caption
Posted without readable text
Sticker, posted without a caption
Channel photo updated
Sticker, posted without a caption
Channel name was changed to «防诈频道‼️‼️‼️»
Posted without readable text
Channel created
Showing the 12 most recent of 12 posts we hold for @yyyguaiguai. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“防诈频道‼️‼️‼️” (@yyyguaiguai), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/yyyguaiguai.
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.