Channel
@gz020ly
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,376subscribers
-2 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003850551455 |
|---|---|
| Type | Channel |
| Username | @gz020ly |
| Created | 3 March 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/gz020ly |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 03:14 | 1,376 | -2 |
| 12 Aug 2026, 18:47 | 1,378 | first reading |
8 posts held, back to 3 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 8 posts for this entry, the most recent from 4 March 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
5 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 100.0% |
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 2 of the 8 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 3 March 2026 to 4 March 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🌐公群导航： @zhdbe 💎租号供需： @zhgx0 🔰官方大群： @zuhaodanbao ✈️灰产交流： @tianzhun0 🏖️供需交流： @zhgxa ——点我收藏租号担保资源—— 🚩🚩🚩🚩🚩🚩🚩🚩🚩🚩 🌟 租号担保负责人 @zhdbfzr 🌟 租号供需负责人 @zhgxfzr 🌟 租号担保纠纷客服 @zhdbjf 🌟 租号担保专群交易 @zhdbzq 🌟 供需资源站 @gxzyz
❤4
⛔️报备交易教程 1.点开机器人 下方按钮🔘 2.发起报备 填写信息 3.报备成功后联系 公群老板审核 🤖公群报备验群机器人 👈
租号担保｜纠纷规则 pinned Deleted message
纠纷仲裁规则 ▪️仲裁申诉 一切纠纷以交易规则为主， 聊天记录只能证明需要申请仲裁纠纷。规则是灰产的法律，别跟我说玩规则，真能玩，你比谁都会！ ▪️仲裁门槛 1. 申诉方填表申诉，明确填写公群，管理员用户名等重要信息！ 2 超过7天以上的纠纷，不予仲裁 3.已下发的纠纷，不予处理。 4.申诉方对申诉内容有所隐瞒，拉群后被发现的，直接判输 ▪️仲裁过程 1. 首先发公群链接，验证公群真伪！ 2.公群方有权利要求申诉方双押对赌。 3.等待官方拉群。进群后，单方当事人不得超过2人，请双方理性阐述事发经过，并提供证据。 4.先发交易规则！交易规则是纠纷仲裁的唯一标准！ 5.整理好证据 【按照步骤发到纠纷群】 6.没有报备，不予退赔 ⛔️禁止事项 严禁耍嘴皮子、骂人、人格侮辱等行为，若出现不予仲裁。 严禁恶意造谣、制造舆论，若出现自动放弃仲裁，直接踢群。 纠纷过程中不管是谁分享出去链接，必须经得仲裁同意，否则不予纠纷，请记住不是谁…
❤1
租号担保｜纠纷规则 pinned «😃业务报备流程说明： ①.与公群老板或业务员达成交易，确认金额然后进行以下步骤操作 ②.做单人员私信机器人 @zhdbyqbot 点击按钮｛发起报备｝ ③.做单人员选择你做单的群组分享给公群管家 ④.填写公群报备订单信息发给公群管家进行报备 ⑤.公群管家会把报备订单发至公群内 ⑥.联系公群管理员审核即可报备完成，做单人开始开工 ⑦.报备期间做单人员可以在机器人点击按钮查看你报备的订单信息 ⑧.完成订单交易完成联系公群管理员进行结算 ⑨.公群管理员可在公群内发数字 3 查看报备数据 ⑩.点击报备订单编号即…»
😃业务报备流程说明： ①.与公群老板或业务员达成交易，确认金额然后进行以下步骤操作 ②.做单人员私信机器人 @zhdbyqbot 点击按钮｛发起报备｝ ③.做单人员选择你做单的群组分享给公群管家 ④.填写公群报备订单信息发给公群管家进行报备 ⑤.公群管家会把报备订单发至公群内 ⑥.联系公群管理员审核即可报备完成，做单人开始开工 ⑦.报备期间做单人员可以在机器人点击按钮查看你报备的订单信息 ⑧.完成订单交易完成联系公群管理员进行结算 ⑨.公群管理员可在公群内发数字 3 查看报备数据 ⑩.点击报备订单编号即可跳转机器人进行选择状态消除报备 🔔做单人员切记！所有订单务必 联系群管理进行报备！私下做单不 受担保方任何保护！如群管理以各 种理由推脱或拒绝报备！立刻举报 🔔群业务/管理切记！所有完成单 务必及时结算销单，如结算后不销 单，投机分子可能会以此为依据对 您的公群进行恶意投诉，浪费公共 资源和双方的时间，切记及时销单 🔔公…
Channel photo updated
Channel created
Showing the 8 most recent of 8 posts we hold for @gz020ly. 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.
Citation-graph rank — 1,357,532 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
@gz020ly 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“租号担保｜纠纷规则” (@gz020ly), 1,376 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/gz020ly.
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.