邮政柜台流水 (利息不收费) (公户+30) 二月 45U 三月 55U 半年 110U 一年 140U 两年 180U 三年 220U 开卡 280U 名下卡带鱼15 卡反15 余额15

Channel
🦅鹰巢通知群
@QuanQiuYing1
On this record: Topic · Growth · Engagement · Posts · Cite this entry
63subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002230753318 |
|---|---|
| Type | Channel |
| Username | @QuanQiuYing1 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/QuanQiuYing1 |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 |
|---|---|---|
| 2 Oct 2026, 17:20 | 63 | +6 |
| 17 Sept 2026, 16:17 | 57 | -2 |
| 9 Sept 2026, 12:17 | 59 | -2 |
| 30 Aug 2026, 04:03 | 61 | -1 |
| 24 Aug 2026, 03:03 | 62 | -1 |
| 10 Aug 2026, 03:30 | 63 | no change |
| 7 Aug 2026, 13:55 | 63 | first reading |
Engagement
20 posts held, back to 19 December 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 19 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
车务一页 三页 名下车🚗 特价3天 一天多批 人在就秒 不在当天多批 有量有价~~
全头全户~ 市面上最稳定全户版本 价格 20U 当天回单
收点明天晚上回的云搜 还有5个位置 价格85U 价格高 贵在明日稳定回单 有急单可报,渠道要求错号回图收费,介意别来!
建设银行卡号:6217001210083208171胡温慈,开户行上海市普陀支行 一月流水 柜台带分秒 44 这单子谁的找我认领
差谁钱过来找我结算
有单子报了没回的客户过来私信我
有单子报了没回的客户过来私信我
📣网络平台订单(饿了么+快递+网购+租车+网约车+网络 🥺 定酒店+网络定机票) 📣捡漏 捡漏 捡漏 捡漏 捡漏 📣私聊拿板😎😎😎❤️ 📣有记录就收费哪怕一条记录也收费 📣( 自己审核是否敏感⚠️敏感扣单收费) 📣周末双休 🇨🇳:@QuanQiuYingC
📣网络平台订单(饿了么+快递+网购+租车+网约车+网络 🥺 定酒店+网络定机票) 📣捡漏 捡漏 捡漏 捡漏 捡漏 📣私聊拿板😎😎😎❤️ 📣有记录就收费哪怕一条记录也收费 📣( 自己审核是否敏感⚠️敏感扣单收费) 📣周末双休 🇨🇳:@QuanQiuYingC
🇨🇳微信号反查业务🇨🇳 1️⃣2️⃣0️⃣🔤 1️⃣➖3️⃣天回单 🧑💻稳定收到 报单不撤 老线老味道 🧑💻出单率百分之90 跟公网差不多 💯 百分百现绑定 🇨🇳:@QuanQiuYingC
📣网络平台订单(饿了么+快递+网购+租车+网约车+网络 🥺 定酒店+网络定机票) 📣捡漏 捡漏 捡漏 捡漏 捡漏 📣私聊拿板😎😎😎❤️ 📣有记录就收费哪怕一条记录也收费 📣( 自己审核是否敏感⚠️敏感扣单收费) 📣周末双休 🇨🇳:@QuanQiuYingC
Showing the 12 most recent of 20 posts we hold for @QuanQiuYing1. 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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“🦅鹰巢通知群” (@QuanQiuYing1), 63 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/QuanQiuYing1.
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.