寻 大四方 、直盘,支付宝双端 成功率70+,费率置顶!! @Guesso_O0
![Telegram profile photo for 冠希担保-[供需频道]](https://cdn.tgregister.com/av/eb/ebeb2f42eb3d7a099a31dafd211e58a034248960844a051314bf674359b9fc59.jpg)
Channel
冠希担保-[供需频道]
@guanxi0022
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,496subscribers
-41 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002110715750 |
|---|---|
| Type | Channel |
| Username | @guanxi0022 |
| Created | Between 1 November 2023 and 17 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/guanxi0022 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 15:58 | 1,496 | -5 |
| 14 Sept 2026, 07:36 | 1,501 | -4 |
| 10 Sept 2026, 17:58 | 1,505 | -12 |
| 5 Sept 2026, 18:36 | 1,517 | -8 |
| 1 Sept 2026, 16:14 | 1,525 | -2 |
| 29 Aug 2026, 15:57 | 1,527 | -8 |
| 26 Aug 2026, 05:42 | 1,535 | -2 |
| 25 Aug 2026, 18:46 | 1,537 | first reading |
Engagement
20 posts held, back to 17 April 2024 — 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.
- ERR · 30 days
- 8.92%
- avg views ÷ 1,496 subscribers
- Avg views / post
- 134
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 20 (17 April 2024 – 22 August 2026) |
| Views total | 267 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Aug 2026, 18:46 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Reaction mix
5 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 40.0% | |
| ❤ | 1 | 20.0% | |
| 👎 | 1 | 20.0% | |
| 👏 | 1 | 20.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 5 of the 20 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 17 April 2024 to 22 August 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.
Recent posts
接180天交易违规解限 企业无对公提额 另外出提额技术 @QC342113
🔥备案域名出租(带质保) 🔥商城包装搭建每个网站都不一样 🔥微信原生/支付宝原生系统/三方支付系统 🔥域名管理系统(多域名平台管理) 🔥游戏进件服务/专注三方进件 🔥业务联系 @pohao666
👏1
Messages in this channel will be automatically deleted after 1 month
Messages in this channel will be automatically deleted after 1 month
收网易通用点核销和问道核销,接二道大额车。@xiaodewo888
充u代付收量: 冰点汇率,无费率! 全网白资天花板,保永久司法 支转支。支转卡。卡转卡。 备付金均有,专业代付!只做精品代付! 寻代付码商核销车队! 日量千万!小核销,小码商,卡卡车队可扶持! 联系人 @sanyuanpay
产品:人民币卡转卡代收付 充值单笔:1000以上 下发单笔:1000以上 下发模式:卡卡 交易时间:早9晚10 规则 1.银行内部白名单卡 100额度专卡 2.100万额度当日保60万,单卡总保500万 3内部白名单卡保盘口风控,当天解当天继续用 只接受纯bc 欢迎信誉盘口来合作 https://t.me/shashou66666
寻1手通道: 1手淘宝零钱 1手淘宝代付 1手售货机,小中大金额都行 1手小荷包原生 微信截图扫码:限额1元-3.99元收量 联系方式: @CHZFchzf 联系方式: @CHZFcyf
纯纯一手自营。收粮 收粮 持续稳定通道【通道名称】:支付宝零花钱 【通道金额】:50-300 【通道规则】:抗并发 抗投诉 ✅查单24小时 ✅禁止重复支付 支付时间5分钟,禁止延迟超时支付!!! 🈲三黑、🈲电炸、🈲杀猪、🈲资金盘、发现大头贴不查不补!!! @shxudu 欢迎量大的来扰 叼大 活好 事还少。
纯纯一手自营。收粮 收粮 持续稳定通道 【通道昵称】:【支付宝H5】❤️热推 24H 【通道限额】:30-500 【通道成功】:50+ 【通道规则】:查单48小时(不炕头,投诉1-1,追诉期15天,如果遇到砖头由商户1:3承担)🈲止刷单、🈲诈骗、🈲资金盘、禁三黑 禁黄游 仅支持纯SP,漫画,小说,VPN等无法提现的量 如发现有BC电 等其他量进来赔付1:3 @shxudu 欢迎量大的来扰
来点聚合码 微信商家码(收精聊一道点位15+)各种丝滑的都要汇率私聊 联系人 @xiaowai686
Showing the 12 most recent of 20 posts we hold for @guanxi0022. 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.
Mentions
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“冠希担保-[供需频道]” (@guanxi0022), 1,496 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/guanxi0022.
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.