群组栏空缺中,早投稿早收录 持续更新 快点关注吧 联系 @zgtxlbot 投稿!
👍5❤3

Channel
@zgtxl
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
777subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001526853081 |
|---|---|
| Type | Channel |
| Username | @zgtxl |
| Created | 1 March 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/zgtxl |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:14 | 777 | -3 |
| 7 Aug 2026, 09:48 | 780 | no change |
| 7 Aug 2026, 09:36 | 780 | first reading |
18 posts held, back to 1 March 2022 — 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 18 posts for this entry, the most recent from 3 March 2022. An engagement rate over an empty window would be a number about nothing.
324 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 53.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 173 | 53.4% | |
| ❤ | 34 | 10.5% | |
| 😁 | 28 | 8.64% | |
| 👎 | 23 | 7.10% | |
| 👏 | 21 | 6.48% | |
| 🔥 | 21 | 6.48% | |
| 🥰 | 16 | 4.94% | |
| 🎉 | 4 | 1.23% | |
| 🤔 | 3 | 0.926% | |
| 😇 | 1 | 0.309% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 17 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 324reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 1 March 2022 to 3 March 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
群组栏空缺中,早投稿早收录 持续更新 快点关注吧 联系 @zgtxlbot 投稿!
👍5❤3
💙Telegram最全男同/GAY【群组】公告板 💙 → 点 @zgtxl 关注 持续更新 ← 👇👇👇👇👇👇👇👇 全球骚基 gay开车 晒鸡 露菊群 川渝GAY吧 TG中学生
👍22👏7👎4🔥3🥰3❤2😁2
. 💙Telegram最全男同/GAY频道公告板💙 建议收藏 and 转发给朋友 → 关注👆持续更新 ← 👇👇👇👇👇👇👇👇 高颜值天菜视频 尿|Pee|Piss|圣水|淋尿|厕 天菜写真 恋物癖 白袜 制服 DogDav公告板 马栏山汉化组 Gv补钙助手频道 男男(solo……等)资源,小说,聊天 同志GAY片群 同志gv-男同片-彩虹资源-同性恋 同志-gay-彩虹家!!! 【飞机库】精选GV gay 白袜 体育生 粗口 SM 秘密的藏宝箱 独家GV猛料 每日GV 新鲜gay片 优质GAY片 优质资源分享 帅哥汁源开车频道 视频资源 一个逗比的收藏夹 插屁的奇怪 Gay Video 多人运动 国产gay视频网黄频道 Nathan 私藏 Gayhub #NSFW 超优质劲爆钙片~gv(gay) gay彩虹同志白袜体育生 GV电报福利群 帅哥情色gay福利 Gay不…
👍107❤28👎18😁17👏14🔥14🥰7🎉4
.
.
.
.
👍1
.
👍1👎1
.
👍4
.
👍4
。
🔥4❤1
。
🥰6
Showing the 12 most recent of 18 posts we hold for @zgtxl. 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.
@zgtxl named 33 handles 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“中国🌈同性恋🇨🇳持续更新” (@zgtxl), 777 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/zgtxl.
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.