太平洋公群 @TPYSY (太平洋上押)群组 pinned a photo

Channel
太平洋公群 @TPYSY (太平洋上押)群组
@TPYSY
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
129,290subscribers
+61,767 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1002002864617 |
|---|---|
| Type | Channel |
| Username | @TPYSY |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/TPYSY |
Topic
Hacking & security — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 13:55 | 129,290 | +2,093 |
| 14 Nov 2026, 05:11 | 127,197 | +3,916 |
| 11 Nov 2026, 10:17 | 123,281 | -320 |
| 9 Nov 2026, 19:09 | 123,601 | +1,634 |
| 8 Nov 2026, 14:15 | 121,967 | +3,093 |
| 7 Nov 2026, 10:31 | 118,874 | -4,057 |
| 6 Nov 2026, 09:26 | 122,931 | +2,156 |
| 5 Nov 2026, 12:38 | 120,775 | +2,531 |
| 4 Nov 2026, 12:10 | 118,244 | -758 |
| 3 Nov 2026, 10:18 | 119,002 | +1,812 |
| 2 Nov 2026, 06:41 | 117,190 | +485 |
| 1 Nov 2026, 07:30 | 116,705 | +2,222 |
| 31 Oct 2026, 07:45 | 114,483 | -2,226 |
| 30 Oct 2026, 08:27 | 116,709 | -551 |
| 29 Oct 2026, 09:49 | 117,260 | +1,900 |
| 28 Oct 2026, 10:38 | 115,360 | +731 |
| 27 Oct 2026, 08:47 | 114,629 | +134 |
| 26 Oct 2026, 10:37 | 114,495 | +1,532 |
| 25 Oct 2026, 14:08 | 112,963 | +346 |
| 24 Oct 2026, 16:16 | 112,617 | first reading |
Engagement
126 posts held, back to 9 August 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 188 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.88%
- avg views ÷ 129,290 subscribers
- Avg views / post
- 2,430
- 9 posts measured
- Reaction rate
- 0.043%
- reactions ÷ views · ER floor
- Posts in window
- 39
- of 126 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. It is computed over the 2 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 126 (9 August 2026 – 16 November 2026) |
| Views total | 21,870 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 11:17 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
102 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 41.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 42 | 41.2% | |
| 👎 | 38 | 37.3% | |
| 👍 | 17 | 16.7% | |
| 🥰 | 4 | 3.92% | |
| 😁 | 1 | 0.98% |
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 126 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 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 126 most recent posts we hold, published 9 August 2026 to 16 November 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
Telegram’s own ‘edited’ marker: 2 of 39 posts held from the last 30 days (5.13%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
太平洋 · 联系与安全说明 ━━━━━━━━━━━━━━ 按问题选择对应入口 🤝 供需发布 供需客服:@TPYFZ1 自助供需服务:@tpydl_bot 👤 负责人联系 负责人:@TPYFZ ⚖️ 纠纷协助 · 永久免费 纠纷员:@TPYPD4 请准备完整聊天记录、相关消息链接及问题说明,处理结果以核实情况为准。 🚀 免费代理 机器人:@tpydl_bot 在机器人内查看当前线路、使用教程及恢复通知。 ━━━━━━━━━━━━━━ 🛡 谨防冒充 认准完整用户名,不只看昵称和头像。 保留聊天记录、主页及交易证据,不轻信陌生人私聊。 涉及报备、交易或纠纷,请通过本公告对应入口核实。 💬 太平洋交流大群:@TPYJLQ
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 03|阿楠超强续租QQ/微信ZMPC 📂 【待分类】 ✨ 06|老中医无副作独家壮阳药 太平洋上押:500U 💻 【ZMPC】 ✨ 08|凯迪拉克PCZM 太平洋上押1500u 🍎 【苹果ID】 ✨ 14|空白高价租苹果id超长续租 太平洋上押888u 💻 【ZMPC】 ✨ 09|5213 起点集团·租微pcZM 超强续租 太平洋上押1000U 🔥 【手机口类】 ✨ 11|1919 文赫团队🔥手机口 秒结账 太平洋上押4777U…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 🔥 【手机口类】 ✨ 01|小葵葵场地直营分钟无线手波 太平洋上押1000U 🍎 【苹果ID】 ✨ 14|空白高价租苹果id超长续租 太平洋上押888u 💻 【ZMPC】 ✨ 10|C139 k微信租号pc 太平洋上押500U 🤝 【拉手类】 ✨ 05|奶糖租号 QQ/小红书/抖音/小红书绿色项目 太平洋上押2000U 🔥 【手机口类】 ✨ 11|1919 文赫团队🔥手机口 秒结账 太平洋上押4777U 👤 【买卖账号】 ✨ 07|899…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 🎵 【抖音】 ✨ 12|锦鲤高价微信口快手口抖音口 上押1000U 🔥 【手机口类】 ✨ 01|小葵葵场地直营分钟无线手波 太平洋上押1000U 👤 【买卖账号】 ✨ 07|899 金蟾集团 收/售 交友软件 太平洋上押1000U 📂 【聊手类】 ✨ 15|货拉拉货车帮货主下单 太平洋上押500U 🤝 【拉手类】 ✨ 05|奶糖租号 QQ/小红书/抖音/小红书绿色项目 太平洋上押2000U 🍎 【苹果ID】 ✨ 14|空白高价租苹果id超长续租…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 🔥 【手机口类】 ✨ 01|小葵葵场地直营分钟无线手波 太平洋上押1000U 🎵 【抖音】 ✨ 12|锦鲤高价微信口快手口抖音口 上押1000U 📂 【聊手类】 ✨ 15|货拉拉货车帮货主下单 太平洋上押500U 💻 【ZMPC】 ✨ 09|5213 起点集团·租微pcZM 超强续租 太平洋上押1000U 💻 【ZMPC】 ✨ 03|阿楠超强续租QQ/微信ZMPC 📂 【待分类】 ✨ 06|老中医无副作独家壮阳药 太平洋上押:500U…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 📂 【待分类】 ✨ 06|老中医无副作独家壮阳药 太平洋上押:500U 📂 【聊手类】 ✨ 15|货拉拉货车帮货主下单 太平洋上押500U 💻 【ZMPC】 ✨ 10|C139 k微信租号pc 太平洋上押500U 🔥 【手机口类】 ✨ 01|小葵葵场地直营分钟无线手波 太平洋上押1000U 🎵 【抖音】 ✨ 12|锦鲤高价微信口快手口抖音口 上押1000U 💻 【ZMPC】 ✨ 09|5213 起点集团·租微pcZM 超强续租 太平洋上押1000U…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 🔥 【手机口类】 ✨ 01|小葵葵场地直营分钟无线手波 太平洋上押1000U 🔥 【手机口类】 ✨ 11|1919 文赫团队🔥手机口 秒结账 太平洋上押4777U 📂 【聊手类】 ✨ 15|货拉拉货车帮货主下单 太平洋上押500U 📂 【待分类】 ✨ 06|老中医无副作独家壮阳药 太平洋上押:500U 💻 【ZMPC】 ✨ 09|5213 起点集团·租微pcZM 超强续租 太平洋上押1000U 💻 【ZMPC】 ✨ 03|阿楠超强续租QQ/微信ZMPC…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 🍎 【苹果ID】 ✨ 14|空白高价租苹果id超长续租 太平洋上押888u 🤝 【拉手类】 ✨ 05|奶糖租号 QQ/小红书/抖音/小红书绿色项目 太平洋上押2000U 🎵 【抖音】 ✨ 12|锦鲤高价微信口快手口抖音口 上押1000U 👤 【买卖账号】 ✨ 07|899 金蟾集团 收/售 交友软件 太平洋上押1000U 📂 【待分类】 ✨ 06|老中医无副作独家壮阳药 太平洋上押:500U 💻 【ZMPC】 ✨ 09|5213 起点集团·租微pcZM…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 📂 【聊手类】 ✨ 15|货拉拉货车帮货主下单 太平洋上押500U 🍎 【苹果ID】 ✨ 14|空白高价租苹果id超长续租 太平洋上押888u 🔥 【手机口类】 ✨ 11|1919 文赫团队🔥手机口 秒结账 太平洋上押4777U 🎵 【抖音】 ✨ 12|锦鲤高价微信口快手口抖音口 上押1000U 🤝 【拉手类】 ✨ 05|奶糖租号 QQ/小红书/抖音/小红书绿色项目 太平洋上押2000U 🔥 【手机口类】 ✨ 01|小葵葵场地直营分钟无线手波…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 🔥 【手机口类】 ✨ 01|小葵葵场地直营分钟无线手波 太平洋上押1000U 💻 【ZMPC】 ✨ 03|阿楠超强续租QQ/微信ZMPC 📂 【聊手类】 ✨ 13|处女集团扫码充电宝 太平洋上押500U 🎵 【抖音】 ✨ 12|锦鲤高价微信口快手口抖音口 上押1000U 🤝 【拉手类】 ✨ 05|奶糖租号 QQ/小红书/抖音/小红书绿色项目 太平洋上押2000U 👤 【买卖账号】 ✨ 07|899 金蟾集团 收/售 交友软件 太平洋上押1000U…»
太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 08|凯迪拉克PCZM 太平洋上押1500u 💻 【ZMPC】 ✨ 09|5213 起点集团·租微pcZM 超强续租 太平洋上押1000U 🔥 【手机口类】 ✨ 11|1919 文赫团队🔥手机口 秒结账 太平洋上押4777U 📂 【待分类】 ✨ 06|老中医无副作独家壮阳药 太平洋上押:500U 🔥 【手机口类】 ✨ 01|小葵葵场地直营分钟无线手波 太平洋上押1000U 🍎 【苹果ID】 ✨ 14|空白高价租苹果id超长续租…»
Showing the 12 most recent of 126 posts we hold for @TPYSY. 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.
Posts edited after publishing
@TPYSY edited 12 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 16 August 2026
- Most recent edit
- 17 November 2026
Posts recorded as deleted after publishing
We recorded 5 posts on @TPYSY as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 16 August 2026
- Most recent seen missing
- 1 October 2026
- Median time before seen missing
- 3 days
- Seen missing in the last 30 days
- 0
Mentions
Named by 4 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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“太平洋公群 @TPYSY (太平洋上押)群组” (@TPYSY), 129,290 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/TPYSY.
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.