Telegram RegisterThe public register of Telegram
Telegram profile photo for 头文字D重要通知

Channel

头文字D重要通知

@TWZDZYTZ

On this record: Growth · Engagement · Posts · Citations · Cite this entry

673subscribers

+32 since we began measuring on 16 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002948889230
TypeChannel
Username@TWZDZYTZ
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/TWZDZYTZ

Growth

64167365716 August 2026 — 641 subscribers16 August 2026 — 641 subscribers25 August 2026 — 657 subscribers31 August 2026 — 673 subscribers16 August 202631 August 2026
4 measurements spanning 15 days, net +32. 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 636–678 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 11:03673+16
25 Aug 2026, 05:48657+16
16 Aug 2026, 19:30641no change
16 Aug 2026, 19:15641first reading

Engagement

20 posts held, back to 16 August 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.

ERR · 30 days
12.7%
avg views ÷ 673 subscribers
Avg views / post
85.2
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 August 2026
Posts held20 (16 August 202616 August 2026)
Views total1,704
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Aug 2026, 19:30 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

16 Aug 2026, 19:21 UTC48 viewsread 16 August 2026
Photo

6666 IOS云闪付原生 限额:50,100,200固额❗️ 费率:1️⃣1️⃣🔣3️⃣ 主体:IOS云闪付单端‼️‼️‼️ —————————————————————————— 【点击查看规则】 各位总裁只能进iOS单端 记得同步一下费率‼️‼️‼️ 各位总裁只能进iOS单端 记得同步一下费率‼️‼️‼️ 各位总裁只能进iOS单端 记得同步一下费率‼️‼️‼️

16 Aug 2026, 19:14 UTC53 viewsread 16 August 2026
Photo

【名称规则】😀微信IOS原生 (淘宝/IOS单端) 【编码状态】6642 开启!!✔️✔️ 【固定金额】100 固额❗️ 【通道费率】1️⃣2️⃣🔣8️⃣ ————————————————————————————— 【名称规则】😀微信IOS原生 (淘宝/IOS单端) 【编码状态】6643 开启!!✔️✔️ 【固定金额】200 固额❗️ 【通道费率】1️⃣2️⃣🔣8️⃣🔼🔼🔼 ————————点击查看规则———————— ⚠️⚠️【全层抗投,抗并发,必须是bc/qp量】 禁三黑,杀猪.诈骗,资金,发现一律赔付订单金额1:10赔付所有查单24小时有效,过期自行承担。 引导会员需要安装淘宝APP。如果支付不成大退淘宝即可拉起支付 👌引导会员需要安装淘宝APP。如果支付不成大退淘宝即可拉起支付 ————————————————————————————— 🔠🔠🔠🔠各位 顶帅顶美,记得同步费率,码

16 Aug 2026, 19:04 UTC66 viewsread 16 August 2026
Photo

【通道编码】6655 【名称规则】😀微信原生 (淘宝/双端) 【固定金额】100 固额❗️❗️ ————————————点击查看规则————————————⚡️ 切停补码

16 Aug 2026, 18:56 UTC70 viewsread 16 August 2026
Photo

6007 支付宝联通原生 限额:50,100,200 固额❗️ 主体:联通商城 费率:1️⃣6️⃣🔣8️⃣ 🔼🔼🔼 —————————————————————————— 【点击通道规则】 高成功率

16 Aug 2026, 17:38 UTC91 viewsread 16 August 2026
Photo

6642 微信IOS(淘宝) 费率:12.8% 限额:100 6643 微信ios原生(淘宝) 费率:12.3% 限额:200 6655 微信原生 双端(淘宝) 费率:12.5% 限额:100 👌引导会员需要安装淘宝APP。如果支付不成大退淘宝即可拉起支付 ————————————————————————————— 🔠🔠🔠🔠各位 顶帅顶美,记得同步费率,码足不拉空

16 Aug 2026, 17:16 UTC99 viewsread 16 August 2026
Photo

6666 IOS云闪付原生 限额:50,100,200固额❗️ 费率上调:1️⃣1️⃣🔣3️⃣🔽🔽🔽 主体:IOS云闪付单端‼️‼️‼️ —————————————————————————— 【点击查看规则】 金额修改 50,100,200‼️‼️‼️ 金额修改 50,100,200‼️‼️‼️ 同步下费率!!!

16 Aug 2026, 16:31 UTC93 viewsread 16 August 2026
Photo

【通道编码】6002 【通道名称】😀纯小芒IOS单端(BC全层 ) 【固定金额】100,200 小芒商城主体 【通道规则】点击查看规则 费率;1️⃣7️⃣ ——————————————————————————————⚡️ 【通道编码】6018 【通道名称】😀纯小芒双端(BC全层) 【固定金额】100,200 小芒商城主体 【通道规则】点击查看规则 费率;1️⃣7️⃣ ——————————————————————————————⚡️ 同步下费率🔽🔽🔽

16 Aug 2026, 16:08 UTC98 viewsread 16 August 2026
Photo

通道编码:【6687】 通道名称:【微信原生双端扫码H5】 高橙绿版本 通道限额:【100 ~ 500】 通道费率:【12.5%】 通道规则:【全层.抗诉 必须BC,棋牌量,打赏量! 禁三黑,刷单,色料,电诈,资金盘等其他任何料子,混料1赔10! 发现大头照不回不补设置延时不退不补,支付时间5分钟,如出现超时支付/修改金额/重复支付/修改支付方式不退不补。 如果出现刷单被骗/网页诱导充值/约炮软件/话费充值/兼职/话费券充值/刮刮乐等非bc投诉导致的司法冻结,罚款5万! 查单24小时内!混料一经发现罚款3w,可以直播带彩!】 费率;1️⃣2️⃣🔣8️⃣🔼🔼🔼 ——————————————————————————————————-- 费率上调 同步费率

16 Aug 2026, 16:05 UTC94 viewsread 16 August 2026
Photo

6668 云闪付原生双端 限额:10-500 任意金额❗️ 费率:1️⃣3️⃣🔣6️⃣🔼🔼🔼 主体:腾讯 【点击通道规则】 —————————————————————————— 同步费率‼️

16 Aug 2026, 15:53 UTC99 viewsread 16 August 2026

6003 支付宝纯原生 费率:暂定% 限额:300,400 6007 支付宝联通商城 费率:15.3% 限额:50,100,200 6014 抖音话费 费率:9.8% 限额:50,100,200 6015 支付宝旗舰版话费 费率:9.8% 限额:50,100,200 6100 支付宝超级H5【个码】 费率:13.5% 限额:100-200 6614 微信原生双端固额(高成率) 费率:21.3% 限额:30 6642 微信IOS(淘宝) 费率:暂定% 限额:100 6643 微信ios原生(淘宝) 费率:暂定% 限额:200 6655 微信原生 双端(淘宝) 费率:暂定% 限额:100 6666 超级云闪付原生 费率:11.5% 限额:50,100,200,300,400,500 6668 云闪付原生 费率:13.1% 限额:10-500,且任意整数金额 6687 微信双端扫码H5(高橙绿版本) 费率:12.

16 Aug 2026, 15:41 UTC97 viewsread 16 August 2026
Photo

【通道编码】6002 【通道名称】😀纯小芒IOS单端(BC全层 ) 【固定金额】100,200 小芒商城主体 【通道规则】点击查看规则 费率;❌❌❌❌ ——————————————————————————————⚡️ 【通道编码】6018 【通道名称】😀纯小芒双端(BC全层) 【固定金额】100,200 小芒商城主体 【通道规则】点击查看规则 费率;❌❌❌❌ —————————————————————————————— 切停维护 系统被拉爆了 先处理掉单

16 Aug 2026, 15:25 UTC18 viewsread 16 August 2026
Photo

【通道编码】6002 【通道名称】😀纯小芒IOS单端(BC全层 ) 【固定金额】100,200 小芒商城主体 【通道规则】点击查看规则 费率;1️⃣3️⃣🔼🔼🔼 ——————————————————————————————⚡️ 【通道编码】6018 【通道名称】😀纯小芒双端(BC全层) 【固定金额】100,200 小芒商城主体 【通道规则】点击查看规则 费率;1️⃣3️⃣🔼🔼🔼 ——————————————————————————————⚡️ 同步下费率🔽🔽🔽

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

Citation-graph rank

Citation-graph rank — 1,583,570 of 1,629,808 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“头文字D重要通知” (@TWZDZYTZ), 673 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/TWZDZYTZ.

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.