@ssejqr88bot 黄色视频机器人
Signed 糯米团子

Channel
@GRKDQ
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003817971549 |
|---|---|
| Type | Channel |
| Username | @GRKDQ |
| Description | 欢迎大家进入 |
| Created | Between 1 February 2026 and 27 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/GRKDQ |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 12:33 | 9 | no change |
| 7 Aug 2026, 19:35 | 9 | first reading |
20 posts held, back to 27 March 2026 — 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 pageof 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 20 posts for this entry, the most recent from 7 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
@ssejqr88bot 黄色视频机器人
Signed 糯米团子
@sucunbot 搜索机器人
Signed 糯米团子
简体中文(@zh_CN 版):https://t.me/setlanguage/classic-zh-cn 简体中
Signed 糯米团子
@TGJHS_BOT 黄色视频机器人🤖
Signed 糯米团子
Telegram 漏洞赏金计划官方客服邮箱 mailto:security@telegram.org
@username_bot Telegram 用户名官方机器人🤖
Telegram 官方客服邮箱 mailto:abuse@telegram.org
Telegram官方客服邮箱 mailto:dmca@telegram.org
@notoscam Telegram 官方举报客服机器人🤖
@EURegulation Telegram欧盟监管官方机器人🤖
Telegram 官网 https://telegram.org/
Turrit 官网 https://iturrit.com/
Showing the 12 most recent of 20 posts we hold for @GRKDQ. 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.
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.
@GRKDQ named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Telegram机器人仓库” (@GRKDQ), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/GRKDQ.
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.