Telegram RegisterThe public register of Telegram
Telegram profile photo for 太平洋公群 @TPYSY (太平洋上押)群组

Channel

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

@TPYSY

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

80,304subscribers

+12,781 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002002864617
TypeChannel
Username@TPYSY
Description太平洋负责人:@TPYFZ(太平洋负责首拼) 公群频道:@TPYSY (太平洋上押) 供需频道:@USDPD @TPYBB(太平洋宝宝首拼) 太平洋纠纷员:@tpypd4 (金牌纠纷) 老供需频道:@BB88 老公群频道:@AA88(担保公群失效转移到 @TPYSY) 太平洋验群机器人:@TPYYQ_bot (太平洋验群 首拼+_bot) 太平洋自助供需机器人:@tpydl_bot (太平洋代理 首拼+_bot)(内置免费代理哦~~~) 太平洋交流大群:@TPYJLQ(太平洋交流群 首拼)
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live25 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.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 why it has no browse page of its own yet.

Growth

61,20680,30470,75515 August 2026 — 67,523 subscribers16 August 2026 — 67,557 subscribers17 August 2026 — 67,587 subscribers18 August 2026 — 67,496 subscribers19 August 2026 — 67,433 subscribers20 August 2026 — 67,445 subscribers22 August 2026 — 67,457 subscribers23 August 2026 — 67,474 subscribers25 August 2026 — 67,420 subscribers26 August 2026 — 67,385 subscribers27 August 2026 — 67,386 subscribers28 August 2026 — 67,351 subscribers29 August 2026 — 67,327 subscribers30 August 2026 — 67,334 subscribers31 August 2026 — 67,330 subscribers1 September 2026 — 67,334 subscribers2 September 2026 — 67,333 subscribers3 September 2026 — 67,346 subscribers5 September 2026 — 67,363 subscribers8 September 2026 — 67,396 subscribers11 September 2026 — 63,198 subscribers13 September 2026 — 62,240 subscribers14 September 2026 — 61,697 subscribers16 September 2026 — 61,206 subscribers19 September 2026 — 64,063 subscribers25 September 2026 — 80,304 subscribers15 August 202625 September 2026
26 measurements spanning 41 days, net +12,781. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 58,341–83,169 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
25 Sept 2026, 17:3780,304+16,241
19 Sept 2026, 04:1664,063+2,857
16 Sept 2026, 20:1561,206-491
14 Sept 2026, 23:1761,697-543
13 Sept 2026, 05:3662,240-958
11 Sept 2026, 05:3863,198-4,198
8 Sept 2026, 09:5667,396+33
5 Sept 2026, 06:5967,363+17
3 Sept 2026, 08:5867,346+13
2 Sept 2026, 03:2867,333-1
1 Sept 2026, 06:4667,334+4
31 Aug 2026, 04:5367,330-4
30 Aug 2026, 06:5967,334+7
29 Aug 2026, 08:0867,327-24
28 Aug 2026, 06:0367,351-35
27 Aug 2026, 07:0967,386+1
26 Aug 2026, 04:5667,385-35
25 Aug 2026, 04:4667,420-54
23 Aug 2026, 22:3867,474+17
22 Aug 2026, 08:3667,457first reading

Engagement

70 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 98 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
—
no view readings in window
Avg views / post
—
no view readings
Reaction rate
—
this channel exposes no reaction counts
Posts in window
29
of 70 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 October 2026
Posts held70 (9 August 2026 – 2 October 2026)
Views total—
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Oct 2026, 05: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.

What this channel posts

Photos
1
Links
10

Lifetime counters from Telegram’s own channel header, read 3 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

72 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 41.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3041.7%
👎2534.7%
👍1318.1%
🥰45.56%

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 11 of the 70 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 72 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 70 most recent posts we hold, published 9 August 2026 to 2 October 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

2 Oct 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 🍷 【烟酒类】 ✨ 178 好人香烟 太平洋上押1000U 🎲 【骰子类】 ✨ 全网手摇快三 太平洋上押1000U 💻 【ZMPC】 ✨ 凯迪拉克PCZM 太平洋上押1500u 💻 【ZMPC】 ✨ 7777 PCzm盘口首选[泡沐集团]专注续租盘 最低十天起步 不说多余的不掺假 太平洋上押1000U 👤 【买卖账号】 ✨ 899 金蟾集团 收/售 交友软件 太平洋上押1000U ━━━━━━━━━━━━━━ 🧭 更多业务请查看公群导航…»

1 Oct 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 5213 起点集团·租微pcZM 超强续租 太平洋上押1000U ✈️ 【TG服务】 ✨ 5000 小可TRX兑换笔数闪租能量代开TG会员 转错秒退!太平洋上押金1000U 💻 【ZMPC】 ✨ 阿楠超强续租QQ/微信ZMPC 🔥 【手机口类】 ✨ 小葵葵场地直营分钟无线手波 太平洋上押1000U 💻 【ZMPC】 ✨ C139 k微信租号pc 太平洋上押500U ━━━━━━━━━━━━━━ 🧭 更多业务请查看公群导航…»

30 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ ✈️ 【TG服务】 ✨ 5000 小可TRX兑换笔数闪租能量代开TG会员 转错秒退!太平洋上押金1000U 📂 【待分类】 ✨ 太平洋交流大群(@TPYJLQ)🈲广告 禁止重复刷屏重复词 🎲 【骰子类】 ✨ 全网手摇快三 太平洋上押1000U 💻 【ZMPC】 ✨ 7777 PCzm盘口首选[泡沐集团]专注续租盘 最低十天起步 不说多余的不掺假 太平洋上押1000U 👤 【买卖账号】 ✨ 899 金蟾集团 收/售 交友软件 太平洋上押1000U…»

29 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 5213 起点集团·租微pcZM 超强续租 太平洋上押1000U 💻 【ZMPC】 ✨ C139 k微信租号pc 太平洋上押500U 💻 【ZMPC】 ✨ 7777 PCzm盘口首选[泡沐集团]专注续租盘 最低十天起步 不说多余的不掺假 太平洋上押1000U 📂 【待分类】 ✨ 太平洋交流大群(@TPYJLQ)🈲广告 禁止重复刷屏重复词 🔥 【手机口类】 ✨ 小葵葵场地直营分钟无线手波 太平洋上押1000U ━━━━━━━━━━━━━━…»

28 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 📂 【待分类】 ✨ 太平洋交流大群(@TPYJLQ)🈲广告 禁止重复刷屏重复词 ✈️ 【TG服务】 ✨ 5000 小可TRX兑换笔数闪租能量代开TG会员 转错秒退!太平洋上押金1000U 💻 【ZMPC】 ✨ 阿楠超强续租QQ/微信ZMPC 👤 【买卖账号】 ✨ 899 金蟾集团 收/售 交友软件 太平洋上押1000U 💻 【ZMPC】 ✨ 5213 起点集团·租微pcZM 超强续租 太平洋上押1000U ━━━━━━━━━━━━━━…»

27 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 阿楠超强续租QQ/微信ZMPC 💻 【ZMPC】 ✨ 7777 PCzm盘口首选[泡沐集团]专注续租盘 最低十天起步 不说多余的不掺假 太平洋上押1000U ✈️ 【TG服务】 ✨ 5000 小可TRX兑换笔数闪租能量代开TG会员 转错秒退!太平洋上押金1000U 👤 【买卖账号】 ✨ 899 金蟾集团 收/售 交友软件 太平洋上押1000U 💻 【ZMPC】 ✨ 5213 起点集团·租微pcZM 超强续租 太平洋上押1000U…»

26 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 阿楠超强续租QQ/微信ZMPC 💻 【ZMPC】 ✨ 7777 PCzm盘口首选[泡沐集团]专注续租盘 最低十天起步 不说多余的不掺假 太平洋上押1000U ✈️ 【TG服务】 ✨ 5000 小可TRX兑换笔数闪租能量代开TG会员 转错秒退!太平洋上押金1000U 👤 【买卖账号】 ✨ 899 金蟾集团 收/售 交友软件 太平洋上押1000U 💻 【ZMPC】 ✨ 5213 起点集团·租微pcZM 超强续租 太平洋上押1000U…»

25 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 凯迪拉克PCZM 太平洋上押1500u 🍷 【烟酒类】 ✨ 178 好人香烟 太平洋上押1000U 🔥 【手机口类】 ✨ 小葵葵场地直营分钟无线手波 太平洋上押1000U 🎲 【骰子类】 ✨ 全网手摇快三 太平洋上押1000U 📂 【待分类】 ✨ 太平洋交流大群(@TPYJLQ)🈲广告 ━━━━━━━━━━━━━━ 🧭 更多业务请查看公群导航 🤝 合作愉快 · 谨防仿冒»

24 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 凯迪拉克PCZM 太平洋上押1500u 🍷 【烟酒类】 ✨ 178 好人香烟 太平洋上押1000U 🔥 【手机口类】 ✨ 小葵葵场地直营分钟无线手波 太平洋上押1000U 🎲 【骰子类】 ✨ 全网手摇快三 太平洋上押1000U 📂 【待分类】 ✨ 太平洋交流大群(@TPYJLQ)🈲广告 ━━━━━━━━━━━━━━ 🧭 更多业务请查看公群导航 🤝 合作愉快 · 谨防仿冒»

23 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 凯迪拉克PCZM 太平洋上押1500u 🍷 【烟酒类】 ✨ 178 好人香烟 太平洋上押1000U 🔥 【手机口类】 ✨ 小葵葵场地直营分钟无线手波 太平洋上押1000U 🎲 【骰子类】 ✨ 全网手摇快三 太平洋上押1000U 📂 【待分类】 ✨ 太平洋交流大群(@TPYJLQ)🈲广告 ━━━━━━━━━━━━━━ 🧭 更多业务请查看公群导航 🤝 合作愉快 · 谨防仿冒»

22 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 💻 【ZMPC】 ✨ 凯迪拉克PCZM 太平洋上押1500u 🍷 【烟酒类】 ✨ 178 好人香烟 太平洋上押1000U 🔥 【手机口类】 ✨ 小葵葵场地直营分钟无线手波 太平洋上押1000U 🎲 【骰子类】 ✨ 全网手摇快三 太平洋上押1000U 📂 【待分类】 ✨ 太平洋交流大群(@TPYJLQ)🈲广告 ━━━━━━━━━━━━━━ 🧭 更多业务请查看公群导航 🤝 合作愉快 · 谨防仿冒»

21 Sept 2026, 08:00 UTCviews —

太平洋公群 @TPYSY (太平洋上押)群组 pinned «🌊 太平洋 · 今日业务精选 ━━━━━━━━━━━━━━ 🎲 【骰子类】 ✨ 全网手摇快三 太平洋上押1000U 📂 【待分类】 ✨ 太平洋交流大群(@TPYJLQ)🈲广告 💻 【ZMPC】 ✨ 阿楠超强续租QQ/微信ZMPC 💻 【ZMPC】 ✨ 凯迪拉克PCZM 太平洋上押1500u 👤 【买卖账号】 ✨ 899 金蟾集团 收/售 交友软件 太平洋上押1000U ━━━━━━━━━━━━━━ 🧭 更多业务请查看公群导航 🤝 合作愉快 · 谨防仿冒»

Showing the 12 most recent of 70 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 10 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
2 October 2026

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.

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“太平洋公群 @TPYSY (太平洋上押)群组” (@TPYSY), 80,304 subscribers as measured 25 September 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.