Channel
@av002002
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
214subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001313278110 |
|---|---|
| Type | Channel |
| Username | @av002002 |
| Description | TG群发器，tg成品号，tg协议号，tg群组拉指定群活人，tg频道刷订阅，僵尸粉 |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/av002002 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 03:32 | 214 | no change |
| 7 Aug 2026, 00:57 | 214 | first reading |
20 posts held, back to 10 April 2022 — 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 pageof 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 27 September 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 August 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.
你好欢迎进入本群，本群业务表 🔥飞机TG账号🔥 🔥土豆(potato)账号🔥 🔥TG协议号🔥 🔥TG协议号登陆器🔥 🔥TG直登号🔥 🔥TG群发拉人助手🔥 🔥TG指定群组拉活人🔥 🔥TG老频道群组出售🔥 🔥TG老号出售🔥 🔥TG会员代开🔥 🔥TG私信代发🔥 🔥tg.推特.脸书.tiktok等等业务🔥 🔥僵尸粉代刷，海外各大平台(tiktok.脸书.ins.)等等🔥 官网 www.tgzhan.com 联系客服 @jinguizi 双向联系 @jinguizibot 🔥TG周边业务都可以洽谈室🔥🔥
你好欢迎进入本群，本群业务表 🔥飞机TG账号🔥 🔥土豆(potato)账号🔥 🔥TG协议号🔥 🔥TG协议号登陆器🔥 🔥TG直登号🔥 🔥TG群发拉人助手🔥 🔥TG指定群组拉活人🔥 🔥TG老频道群组出售🔥 🔥TG老号出售🔥 🔥TG会员代开🔥 🔥TG私信代发🔥 🔥tg.推特.脸书.tiktok等等业务🔥 🔥僵尸粉代刷，海外各大平台(tiktok.脸书.ins.)等等🔥 🔥TG周边业务都可以洽谈室🔥🔥
本群为中专群，关注总频道 浏览最新业务 @qunfaqi0
你好欢迎进入本群，本群业务表 🔥飞机TG账号🔥 🔥土豆(potato)账号🔥 🔥飞机协议号🔥 🔥协议号登陆器🔥 🔥飞机直登号🔥 🔥TG群发拉人助手🔥 🔥TG指定群组拉活人🔥 🔥TG老频道群组出售🔥 🔥TG老号出售🔥 🔥僵尸粉代刷，海外各大平台(tiktok.脸书.ins.)等等🔥 🔥TG周边业务都可以洽谈室🔥🔥
你好欢迎进入本群，本群业务表 🔥飞机TG账号🔥 🔥土豆(potato)账号🔥 🔥飞机协议号🔥 🔥协议号登陆器🔥 🔥飞机直登号🔥 🔥TG群发拉人助手🔥 🔥TG指定群组拉活人🔥 🔥TG老频道群组出售🔥 🔥TG老号出售🔥 🔥僵尸粉代刷，海外各大平台(tiktok.脸书.ins.)等等🔥 🔥TG周边业务都可以洽谈室🔥🔥
. .🔥业务表，解说🔥 1，飞机成品号，飞机协议号，飞机直登号 (进群看价格 @aaxxav) 2，飞机僵尸粉代刷，代拉指定群活人 (进群看价格 @jiangshife ) 3，海外各大平台推特tiktok等等僵尸粉，播放量，评论代刷，等等 (进群看价格 @ckjiema1) 4，协议号转直登号软件 (进群看价格 @qunfaqiTG) 5，协议群发拉人助手出售，可以批量拉人，批量群发，批量吵群，批量私信等等 (进群看价格 @feiniao990) 6，出一年左右老频道200一个，数量不多先到先得 (另外关于飞机周边业务也能谈) 总频道 @qunfaqi0 联系客服 @haozhu1
‼️‼️‼️本群项目！！！ ✨协议小号✨ 🌵4块1个 打包20个起售 🌵 100个起按3 🌵1000个起按2.5 🌵5000个起按2块 ✨电报账号需要接验证登陆 ✨ 🌵1个/15元 🌵5个/14元一个 🌵20个/12元一个 🌵100个/9元一个 直登号群组 @aaxxav ❗️❗️❗️价格更新啦❗️❗️❗️ 🐮群组频道僵尸粉🐮 🌵1000/50元 🌵5000/200元 🌵10000/350元 🌵20000/650元（两万以上每增加一万+200） 🐮代拉活人🐮 指定群拉活人 🌵1000/300元 指定群拉活人🌵10000/2500元 海外平台僵尸粉代刷 @ckjiema1 🔥频道文章刷阅读量.一千阅读量 5元，量大有折扣，不能多个频道混搭🔥 最新版协议版群发器，群组 @toupai…
. .🔥业务表，解说🔥 1，飞机成品号，飞机协议号，飞机直登号 (进群看价格 @aaxxav) 2，飞机僵尸粉代刷，代拉指定群活人 (进群看价格 @jiangshife ) 3，海外各大平台推特tiktok等等僵尸粉，播放量，评论代刷，等等 (进群看价格 @ckjiema1) 4，协议号转直登号软件 (进群看价格 @qunfaqiTG) 5，协议群发拉人助手出售，可以批量拉人，批量群发，批量吵群，批量私信等等 (进群看价格 @feiniao990) 6，出一年左右老频道200一个，数量不多先到先得 (另外关于飞机周边业务也能谈) 总频道 @qunfaqi0 联系客服 @haozhu1
‼️‼️‼️本群项目！！！ ✨协议小号✨ 🌵4块1个 打包20个起售 🌵 100个起按3 🌵1000个起按2.5 🌵5000个起按2块 ✨电报账号需要接验证登陆 ✨ 🌵1个/15元 🌵5个/14元一个 🌵20个/12元一个 🌵100个/8元一个 ❗️❗️❗️价格更新啦❗️❗️❗️ 🐮群组频道僵尸粉🐮 🌵1000/50元 🌵5000/200元 🌵10000/350元 🌵20000/650元（两万以上每增加一万+200） 🐮代拉活人🐮 🌵1000/300元 🌵10000/2500元 协议版群发器群组 @toupai4 ☎️联系客服💁🏻 @haozhu1
. . . .🔥导航指南🔥 🔥各大平台拉僵尸粉活人🔥点我 🔥协议拉人群发助手，演示🔥点我 🔥✈️飞机群发器官网✈️🔥 ✈️飞机群发器购买，和代理👌点击我✈️👈 🔥飞机成品账号购买🔥点我👈 🔥土豆potato成品号购买🔥 .招代理合作商联系 @haozhu1
🔥拉人业务调价提醒🔥 🔥僵尸粉一千人50元🔥 🔥僵尸粉五千人200元🔥 🔥僵尸粉一万人350元🔥 🔥🔥🔥🔥🔥🔥🔥🔥🔥 🔥指定群拉人，一千人300🔥 🔥指定群拉人，五千人1500🔥 🔥刷阅读量一个频道近五十条 一千+只需50元即可，不能多个频道混搭🔥🔥🔥🔥🔥🔥 另出飞机成品号和土豆成品号 单买15一个，量大价低 ❤频道只能拉僵尸粉❤ ❤群组可拉任何粉 ❤ ❤需要的朋友联系客服❤ ❤ @haozhu1 ❤
🔥飞机号(Telegram)🔥 🔥土豆号（potato） 🔥单个购买 15元一个🔥 ✈批量购买价格低✈ 🔥五个起，14.元一个🔥 🔥二十个起 12元一个🔥 🔥百个起 8元一个🔥 🔥五百起 6元一个🔥 另外冷门平台代接码业务 需要购买联系 @haozhu1
Showing the 12 most recent of 20 posts we hold for @av002002. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“TG群发器，tg成品号，tg协议号，tg群组拉指定群活人，tg频道刷订阅，僵尸粉” (@av002002), 214 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/av002002.
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.