Channel
@AG20026
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
271subscribers
-34 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003274430602 |
|---|---|
| Type | Channel |
| Username | @AG20026 |
| Created | 1 November 2025 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/AG20026 |
Marketing & affiliate — 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 23 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 01:05 | 271 | -1 |
| 1 Nov 2026, 21:59 | 272 | -3 |
| 17 Oct 2026, 17:58 | 275 | -2 |
| 11 Oct 2026, 18:36 | 277 | -3 |
| 30 Sept 2026, 16:37 | 280 | -5 |
| 17 Sept 2026, 05:02 | 285 | -6 |
| 8 Sept 2026, 19:56 | 291 | -3 |
| 31 Aug 2026, 07:57 | 294 | -2 |
| 25 Aug 2026, 01:53 | 296 | -4 |
| 18 Aug 2026, 00:53 | 300 | -5 |
| 10 Aug 2026, 17:47 | 305 | no change |
| 9 Aug 2026, 20:46 | 305 | first reading |
2 posts held, back to 1 November 2025 — 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 2 posts for this entry, the most recent from 19 March 2026. An engagement rate over an empty window would be a number about nothing.
❤️❤️❤️❤️全网No.1最高价招租闲鱼号！ 😀😃😀直登大量来号（30秒一个号） 🫥续租拉满😀😀过😀 🥽鱼力值 420以下😃😃😃 🥽鱼力值420以上😃😃😃 🥽鱼力值 500以上😃😃😃 🥽鱼力值600以上😃😃😃 🥽鱼力值越高价越高 😂😂😀小时全天 上满3个奖励🇳🇮🇳🇮 上满5个以上奖励🇳🇮🇳🇮 只限当天 全网在押😃😃😃😃😃😃 😃😃😊😊😊😊 上满2个小时可以预付！ 上满2个小时可以预付！ 全网首家！ 全网最高价 欢迎各大团队号商代理来合作 ❤️❤️❤️❤️ 鱼力值 400 也要，三认证➕随便发布一个商品 ❗️❗️❗️❗️❗️❗️❗️❗️ 🥱😲吊打所有上号慢 结算慢 卡时间的垃圾盘 高价必黑 必跑 寻求靠谱稳定认准财销集团🫥 🇻🇳上号联系：@AGEN2233 🇪🇭双向联系：@AGEN5566_bot😃
Signed 姬霓太美
Channel created
Showing the 2 most recent of 2 posts we hold for @AG20026. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“财销集团-业务通知频道” (@AG20026), 271 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/AG20026.
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.