英卡 需要预订的来滴滴 量大优先上货

Channel
老秦项目通知
@Goodgx8
On this record: Growth · Engagement · Posts · Cite this entry
21,663subscribers
-1,277 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003075226820 |
|---|---|
| Type | Channel |
| Username | @Goodgx8 |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/Goodgx8 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 17:44 | 21,663 | -31 |
| 30 Aug 2026, 20:28 | 21,694 | -33 |
| 29 Aug 2026, 20:25 | 21,727 | -34 |
| 28 Aug 2026, 23:54 | 21,761 | -55 |
| 27 Aug 2026, 20:37 | 21,816 | -11 |
| 26 Aug 2026, 23:46 | 21,827 | -45 |
| 26 Aug 2026, 00:54 | 21,872 | -61 |
| 25 Aug 2026, 02:13 | 21,933 | -66 |
| 23 Aug 2026, 17:07 | 21,999 | -86 |
| 22 Aug 2026, 06:36 | 22,085 | -44 |
| 20 Aug 2026, 20:12 | 22,129 | -6 |
| 19 Aug 2026, 23:22 | 22,135 | -54 |
| 18 Aug 2026, 20:34 | 22,189 | -189 |
| 17 Aug 2026, 18:24 | 22,378 | -123 |
| 16 Aug 2026, 16:14 | 22,501 | -48 |
| 14 Aug 2026, 22:24 | 22,549 | -71 |
| 13 Aug 2026, 16:27 | 22,620 | -113 |
| 12 Aug 2026, 14:54 | 22,733 | -34 |
| 11 Aug 2026, 14:15 | 22,767 | -26 |
| 10 Aug 2026, 15:51 | 22,793 | first reading |
Engagement
26 posts held, back to 27 June 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 50 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.00%
- avg views ÷ 21,663 subscribers
- Avg views / post
- 217
- 7 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 8
- of 26 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 30 August 2026 |
|---|---|
| Posts held | 26 (27 June 2026 – 30 August 2026) |
| Views total | 1,521 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 10:35 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.
Recent posts
港 英 美 加 印尼 各补货2w 需要联系
冷门虚拟关键词 大麦 像素*uu*生数*得到*清枫*UU*酷我 螃蟹*孩子*4399*麦当劳*米哈*库洛 37网游*锅圈*汉爵*达美乐*橙子*海信*点点 星巴克*洋葱*小程序*公众平台 锦江*航旅 亚朵*肯德基 Soul*哔哩 拼多多*百度 天安门*商汤*威孚*九游*千圣网络**天勤*星星云*biubiu*创翰**YY*得物*欧意*同花顺*迅游*巨人*飞蝠*喜番*贺宽*完美*麦座*凡特*乐播*蜂助手*海螺* 互娱*达能饮料*一起彩*神耀*文旅*鑫广*趣游*晓屋*海南*通达文*智谱*云手机*信易添*悦言*畅言*微语*柚游*酷我*乐鸿
出广电卡注册QQ 全新卡,一卡注册2个号 项目介绍:出虚拟卡号段(162)出广电卡(192)接码业务 抖音 QQ 快手 陌陌 微博 百度 拼多多 灵魂,各种接码小业务 四方卡位,留卡跟具业务时间长短(3-5天时间)也可一卡一链接, 企业和微信只有虚拟卡可做,广电(192)不做高危项目,需要联系 @laoqin6
刚从老外那边搞了25万的美卡老数据 需要筛选QQ的可以联系我了 @laoqin6
特1 星月单 包解 到货1750个 需要联系 @elllp
老秦项目通知 pinned «美实卡 小红书 京东 补货2w 港 小红书 京东 补货1w 需要联系 @elllp»
美实卡 小红书 京东 补货2w 港 小红书 京东 补货1w 需要联系 @elllp
出邮箱支付白 outau格式 直登 代付 美卡支付白带接短信api 直登 代付 隔天会死号 需要联系 @elllp
出 苹果密保强改软件 出 苹果双重id 注册脚本 出 B站评论点赞软件 出 B站视频 可见范围 批量修改 软件 (仅自己可见) 出 B站账号密码登录 取ck 软件 需要联系 @elllp
补货港卡微信,京东,抖音,阿里,小红书,10000张全新首次 需要联系下 @elllp
出各种银行带信息资料 做富国客户可以聊 WS号码大量出 @elllp
Showing the 12 most recent of 26 posts we hold for @Goodgx8. 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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“老秦项目通知” (@Goodgx8), 21,663 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Goodgx8.
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.