高德担保最近太火啦,鸽子妹已上押 放心交易~ 😄😄😄😄😄😄 公群520 鸽子🕊️飞机号|会员|VPN|僵尸粉|典藏礼物 (押金2000U)
👎1

Channel
@geziyewu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
19,520subscribers
-1,650 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003368341765 |
|---|---|
| Type | Channel |
| Usernames | @geziyewu @ppprh |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/geziyewu |
Ecommerce storefront — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:16 | 19,520 | -6 |
| 17 Sept 2026, 22:41 | 19,526 | -34 |
| 16 Sept 2026, 03:41 | 19,560 | -9 |
| 15 Sept 2026, 18:41 | 19,569 | -39 |
| 14 Sept 2026, 09:16 | 19,608 | -5 |
| 14 Sept 2026, 04:21 | 19,613 | -40 |
| 12 Sept 2026, 16:18 | 19,653 | -1 |
| 12 Sept 2026, 13:21 | 19,654 | -108 |
| 10 Sept 2026, 16:41 | 19,762 | -12 |
| 10 Sept 2026, 11:59 | 19,774 | -149 |
| 7 Sept 2026, 16:17 | 19,923 | -6 |
| 7 Sept 2026, 10:17 | 19,929 | -69 |
| 4 Sept 2026, 17:02 | 19,998 | no change |
| 4 Sept 2026, 15:40 | 19,998 | -38 |
| 3 Sept 2026, 01:53 | 20,036 | no change |
| 3 Sept 2026, 00:56 | 20,036 | -59 |
| 1 Sept 2026, 20:44 | 20,095 | no change |
| 1 Sept 2026, 20:14 | 20,095 | -27 |
| 31 Aug 2026, 23:38 | 20,122 | no change |
| 31 Aug 2026, 21:26 | 20,122 | first reading |
19 posts held, back to 1 May 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 53 pages of Telegram’s post history, 20 posts per page.
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 31 August 2026 |
|---|---|
| Posts held | 19 (1 May 2026 – 31 August 2026) |
| Views total | 885 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00:56 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.
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.
144 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 30.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 44 | 30.6% | |
| 🎉 | 25 | 17.4% | |
| 🔥 | 25 | 17.4% | |
| 😁 | 25 | 17.4% | |
| 👍 | 23 | 16.0% | |
| 👎 | 1 | 0.694% | |
| 💩 | 1 | 0.694% |
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 14 of the 19 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 144 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 1 May 2026 to 31 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.
高德担保最近太火啦,鸽子妹已上押 放心交易~ 😄😄😄😄😄😄 公群520 鸽子🕊️飞机号|会员|VPN|僵尸粉|典藏礼物 (押金2000U)
👎1
🇹🇭 泰国 AIS 电话卡出售 📱 实卡可邮寄|线上可开 eSIM ✨ 可选 +66 6 开头靓号 📶 套餐包含: • 流量:20GB • 泰国本地通话:双无限 • 后续续费:15U ⚡拿货价格: • 实体卡:40U/张(5张起拿) • eSIM:38U/张(5张起拿) • True:23U/张(10张起拿) ⚡️可注册、可接码
❤1
七夕/Happy Qixi Festival 💙🩵 🎀缘分让我们相遇 🕊️ @gezi🍃 今天是 8月19日,农历七月初七,七夕。🎆 七夕也叫 乞巧节。🦄 一年一会,七夕如期而至。🦄🦄 愿有情人长久, 也愿所有喜欢都有回应。🦄 七夕快乐!💙🩵
群发器出售|附带服务器 稳定运行,无广告干扰 有需求欢迎咨询 @gezi 了解
❤1
https://clashplus.io 客户反馈:电脑端使用 VPN 节点时,这款软件体验会更好、更稳定一些。 有需要的用户可以自行下载安装,并导入对应节点使用。
❤1
🎉 恭喜成功开通 🅰️官方认证标识 1️⃣认证永久有效 2️⃣提升频道/群组公信力,增强品牌形象 3️⃣让用户更容易识别官方身份。 🅰️提供频道、群组 A+ 官方认证服务 🅰️办理稳定|全程协助|快速开通 有需要开通 🅰️认证的老板,欢迎随时联系鸽子:@gezi 📩
❤2💩1
🪽电报类业务 首选鸽子牌资源商🪽 ❤️电报会员星星 ❤️群组/频道A+认证 😍小火箭VPN 😍苹果ID·谷歌邮箱 ❤️僵尸粉 在线粉 浏览量 频道助力 😍GPT代开 😍快连代开 ❤️全球TG老号 ❤️高速代理 😍esim 流量卡 😍香港流量卡 💴鸽子专注优质资源整合,以稳定货源为基础,以服务为核心。让每一位合作伙伴,买得安心,用得放心,做得长久💴
❤1
🎉 恭喜成功开通 🅰️官方认证标识 1️⃣认证永久有效 2️⃣提升频道/群组公信力,增强品牌形象 3️⃣让用户更容易识别官方身份。 🅰️提供频道、群组 A+ 官方认证服务 🅰️办理稳定|全程协助|快速开通 有需要开通 🅰️认证的老板,欢迎随时联系鸽子:@gezi 📩
❤14🎉11🔥11👍10😁9
现专线已全部恢复 我们将统一为受影响的用户发放相应的【延迟/中断补偿】。给您带来不便,我们深表歉意,感谢您的理解与配合!
🟢TG钱包闪兑|即时到账 ❌ 钱包互提 = 1U手续费 ✅ 换U宝闪兑 = 仅0.5U 👛 支持: OKpay|福利来|达利|爱赌钱包|未来钱包|PPay|YYPay 🔹全钱包互通 🔹即时到账 🔹24小时自助 🔹TG玩家首选 👇 立即兑换,省下每一笔手续费!
鸽子🕊️自助会员 @gezi66bot 鸽子🕊️源头号铺自助 @gezihpbot 需要的老板自助下单哦😊 客服联系:@gezi
🎉 恭喜成功开通 🅰️官方认证标识 1️⃣认证永久有效 2️⃣提升频道/群组公信力,增强品牌形象 3️⃣让用户更容易识别官方身份。 🅰️提供频道、群组 A+ 官方认证服务 🅰️办理稳定|全程协助|快速开通 有需要开通 🅰️认证的老板,欢迎随时联系鸽子:@gezi 📩
😁16🎉14👍13🔥12❤9
Showing the 12 most recent of 19 posts we hold for @geziyewu. 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.
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.
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.
“缘分让我们相遇🕊️@gezi” (@geziyewu), 19,520 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/geziyewu.
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.