Telegram RegisterThe public register of Telegram
Telegram profile photo for Fzdn1群发程序

Channel

Fzdn1群发程序

@quanfa01

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

13subscribers

+2 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-1003897466497
TypeChannel
Username@quanfa01
CreatedBetween 1 February 2026 and 23 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 31 August 2026
On Telegramt.me/quanfa01

Growth

1113127 August 2026 — 11 subscribers12 August 2026 — 11 subscribers15 August 2026 — 12 subscribers23 August 2026 — 13 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net +2. 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 20:0713+1
15 Aug 2026, 20:4612+1
12 Aug 2026, 07:4511no change
7 Aug 2026, 19:1611first reading

Engagement

20 posts held, back to 23 May 2026the 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 3 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 37s
Average length
4m 37s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

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

Measured over the 20 most recent posts we hold, published 23 May 2026 to 3 August 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

3 Aug 2026, 06:32 UTC21 viewsread 12 August 2026
File

增加批量修改资料的会员图标 优化群发账号多而导致时间不对 (之前是前端阻塞了)

29 Jul 2026, 07:06 UTC26 views2 reactionsread 12 August 2026
File

群组克隆可克隆源群的回复引用

2

19 Jul 2026, 06:05 UTC44 viewsread 12 August 2026
File

session转换密码错了可手动输入 监听私信修复 其他逻辑和之前一样 请选择性更新

16 Jul 2026, 15:44 UTC47 viewsread 12 August 2026
File

链接验活可配置代理 综合功能里的session转换可以通过接码转换 修复已知bug

9 Jul 2026, 05:28 UTC61 viewsread 12 August 2026
File

监听私信改为独立进程启动监听账号 (之前占用内存是windows的通病) 目标关键词可以精准匹配 优化加群验证

4 Jul 2026, 07:15 UTC62 viewsread 12 August 2026
File

修复私密群加群问题 代理持久化 私信自动回复多种模式

25 Jun 2026, 15:25 UTC97 viewsread 12 August 2026
Photo

ai验证新建一个密钥 不要限制模型 选择非2.5开头的模型 ai模式过群组验证 注册好充值10块rmb去令牌管理创建密钥 选择图片里的模型 填入程序 这里注册 https://www.right.codes

23 May 2026, 14:01 UTC146 viewsread 12 August 2026
Photo

群发新增自动补群 可以设置第几轮检查一次 低于就按你设置的数量去加 本次任务不重复指的是全局不重复就是所有账户 重复就是使用同一个列表随机选择

23 May 2026, 14:00 UTC127 viewsread 12 August 2026
Photo

账户管理页面新增双向申诉 去https://yescaptcha.com/i/pMIngY 注册一个打码平台填key(在仪表盘那) 代理填不填可选(只是验证链接走)

23 May 2026, 14:00 UTCviews —

Fzdn1群发程序 pinned «📌 功能导航 🔹 登录账号 🔸 导入 session / 手动登录 🔹 群发 🔸 引用 / 转发 / 直发 / Post 🔹 批量私信 🔸 用户名 / 手机号 / Bot 自动验证 🔹 群成员采集 🔸 公开群 / 聊天记录,保存表格 🔹 采集群组 🔸 关键词群组采集 🔹 批量进群 🔸 自动加群 + Bot 验证+ai验证 🔹 监听私信 🔸 监听关键词进行私信或回复 🔹 群组活跃度检测 🔸 最近发言检查 🔹 群组链接验活 🔸 加群前验证有效性 🔹 配置ai教程 🔸 Ai辅助过群组验证 …»

Showing the 12 most recent of 20 posts we hold for @quanfa01. 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.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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

“Fzdn1群发程序” (@quanfa01), 13 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/quanfa01.

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.