Telegram RegisterThe public register of Telegram
Telegram profile photo for 8989看图王 作图软件 【支持测试】P图软件 zizi67888 zt8989ktw8

Channel

8989看图王 作图软件 【支持测试】P图软件 zizi67888 zt8989ktw8

@zt8989ktw8_2

2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

4,867subscribers

-1,235 since we began measuring on 2 October 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1004309943102
TypeChannel
Usernames@DY88989ktw @zt8989ktw8_2
CreatedBetween 1 June 2026 and 2 October 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 October 2026
Last confirmed live17 November 2026
Measurements held7
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/zt8989ktw8_2

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 8 November 2026 and assigned it the closest of 31 fixed categories, at 69% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@DY8989ktw/597 Sept 2026, 13:11 UTC@zt8989ktw8_2/49 · this entry2 Oct 2026, 10:34 UTC1.0025 days
@DY8989ktw/647 Sept 2026, 13:22 UTC@zt8989ktw8_2/50 · this entry2 Oct 2026, 10:34 UTC1.0025 days
@DY8989ktw/9020 Sept 2026, 09:21 UTC@zt8989ktw8_2/54 · this entry2 Oct 2026, 11:02 UTC1.0012 days
@DY8989ktw/9524 Sept 2026, 19:48 UTC@zt8989ktw8_2/55 · this entry2 Oct 2026, 11:05 UTC1.008 days
@DY8989ktw/8617 Sept 2026, 08:31 UTC@zt8989ktw8_2/51 · this entry2 Oct 2026, 10:48 UTC0.9915 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@DY8989ktw5 (5/5 hand-verifiable sample passed)1.0015 days@DY8989ktw (5–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 2 October 2026 to 2 October 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @DY8989ktw. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

17,2303,615.52 October 2026 — 6,102 subscribers7 October 2026 — 7,230 subscribers13 October 2026 — 1 subscribers7 November 2026 — 5,808 subscribers7 November 2026 — 5,808 subscribers12 November 2026 — 5,799 subscribers17 November 2026 — 4,867 subscribers4,8672 October 202617 November 2026
7 measurements spanning 46 days, net -1,235. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 18:284,867-932
12 Nov 2026, 12:095,799-9
7 Nov 2026, 23:225,808no change
7 Nov 2026, 22:475,808+5,807
13 Oct 2026, 16:591-7,229
7 Oct 2026, 14:427,230+1,128
2 Oct 2026, 23:226,102first reading

Engagement

15 posts held, back to 2 October 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.678%
avg views ÷ 4,867 subscribers
Avg views / post
33.0
1 post measured
Reaction rate
800.0%
reactions ÷ views · ER floor
Posts in window
1
of 15 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 6 November 2026
Posts held15 (2 October 2026 – 6 November 2026)
Views total33
Reactions total264
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 23:22 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.

What this channel posts

Video runtime
24s
Average length
24s

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

371 reactions across 3 posts, in 8 distinct kinds. The most used accounts for 17.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6317.0%
😁6216.7%
🎉5615.1%
👍5013.5%
🔥4913.2%
😍3910.5%
🥰3810.2%
👏143.77%

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

Measured over the 15 most recent posts we hold, published 2 October 2026 to 6 November 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

Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 09:56 UTC33 views264 reactionsread 7 November 2026
Photo

8️⃣9️⃣8️⃣9️⃣ 😱😤😭 已更新 英文版 左上角点击切换 开卡续费联系客服 😘 @DY_88989 双向机器人联系 😘 @DY_88989_bot

😁62🎉56👍50🔥49❤47

18 Oct 2026, 06:29 UTC242 views106 reactionsread 7 November 2026
Photo

🔥🔥🔥🔥🔥重要通知 重要通知 重要通知 🔥🔥🔥已更新在线网页版手机端, 安卓苹果手机正常使用。 和电脑版账号同步的 开卡续费联系客服 😘 @DY_88989 双向机器人联系 😘@DY_88989_bot

😍39🥰38❤15👏14

2 Oct 2026, 19:31 UTC≈1,570 views1 reactionsread 7 November 2026
Video

🔔最新版本已更新上线🔔 软件功能包含: 🎲国内银行;🎲国外银行;🎲网络钱包; 🎲加密货币;🎲股票证券;🎲聊天生成; 🎲机票酒店;🎲证件生成;🎲电脑银行; 🔔全网唯一无毒绿色p图神器!⭐️ 开卡续费联系客服 🥰@DY_8989 双向联系客服🥰 @DY_88989_bot

❤1

2 Oct 2026, 19:23 UTC≈1,500 viewsread 7 November 2026
Photo

8989看图王 👍👍👍👍 😍😍😍 😍😍😍 😍😍😍😍 💳假图💳转账💳流水💳USDT💳 🔠网银🔠手机app🔠营业执照🔠 各种证件一键生成以假乱真 🏦支持主流银行转账界面模拟,可自定义收款人、金额、时间等信息,生成高度逼真的转账截图或电子回单 提供多种模板选择,支持修改转账状态(如“处理中”“转账成功”)和动态更新余额 ‌虚拟账户管理‌ 💵💵💵💵💵💵💵💵💵💵💵💵💵💵💵 ☺️微信支付宝红包制作 ☺️微信转账银行卡制作 ☺️司法冻结止取图制作 ☺️支付宝微信聊天制作 ☺️海外银行转账制作 ☺️手机网银转账制作 ☺️电脑网银转账制作 ☺️银行到账短信制作 ☺️证件机票酒店制作 ☺️营业执照股票制作 ☺️交易所转账制作 ☺️支付宝转账制作 ☺️银行流水图制作 ☺️护照驾驶证制作 🔥支持 USDT🌟全部模板🌟国内银行🌟网络钱包🌟聊天生成🌟海外银行🌟加密货币🌟股票证劵…

2 Oct 2026, 11:06 UTC≈1,020 viewsread 7 November 2026
Photo

最近很多盗版模仿者,各位老板注意,骗子太多了 我就一个软件名字叫 8️⃣9️⃣8️⃣9️⃣ 😱😤😭 🥰注意 注意 注意 各位老板,需要更新图,必须提供原图高清,不然没法更新。 开卡续费联系客服 😘 @DY_8989 双向联系客服: @DY_8989_bot

2 Oct 2026, 11:05 UTC914 viewsread 7 November 2026
Photo

🎑 8️⃣9️⃣8️⃣9️⃣ 😱😤😭公告 | 中秋快乐·黄金九月启航 🌕 🏷 亲爱的用户 月圆人团圆,情满共此时。 在这花好月圆的中秋佳节,8989全体人员祝大家—— 💫 事业如月中明辉,圆满顺遂; 💫 财运如桂花飘香,源源不断; 💫 家庭如月光清朗,幸福安宁。 同时,8️⃣9️⃣8️⃣9️⃣ 😱😤😭迎来“黄金九月”,感谢一路支持我们的每一位用户与合作伙伴。 我们将在这个收获的季节,持续优化8989体验、提升作图效果,让客户使用更有价值。 开卡续费联系客服 😘 @DY_8989 ⚡️⚡️⚡️⚡️【皇冠天行组公群5027已上押】皇冠担保✔️官方认证,放心使用✔️

2 Oct 2026, 11:02 UTC833 viewsread 7 November 2026
Photo

全新推出8️⃣9️⃣8️⃣9️⃣【8989看图王】祝各位老板发大财,天天爆单🥰🥰🥰🥰🥰🥰🥰 ⚡️⚡️⚡️⚡️【皇冠天行组公群5027已上押】皇冠担保✔️官方认证,放心使用✔️ 看图王作图所有版本都可以免费测试,测试卡密请联系客服,本频道是全网唯一价格最低商家

2 Oct 2026, 10:54 UTC823 viewsread 7 November 2026
File

最近很多盗版模仿者,各位老板注意,骗子太多了 我就一个软件名字叫 8️⃣9️⃣8️⃣9️⃣ 😱😤😭 🥰注意 注意 注意 各位老板,需要更新图,必须提供原图高清,不然没法更新。 开卡续费联系客服 😘 @DY_8989 双向联系客服: @DY_8989_bot

2 Oct 2026, 10:48 UTC774 viewsread 7 November 2026
Photo

🔄8️⃣9️⃣8️⃣9️⃣看图王🔄 👍👍👍👍👍👍 😋😋🤓😎😋📣🔊 🔥支持 USDT🌟全部模板🌟国内银行🌟网络钱包🌟聊天生成🌟海外银行🌟加密货币🌟股票证劵🌟机票酒店🌟证件合成🌟 支持 USDT🌟 全部模板🌟国内银行🌟网络钱包🌟聊天生成🌟海外银行🌟加密货币🌟股票证劵🌟机票酒店🌟证件合成 🌟 😍😍😍 😍😍😍 👩‍👩‍👦‍👦美股、盈通证券、台湾股票、国内股票、德国股票、日本股票、日本东京证券、澳大利亚股票👩‍👩‍👦‍👦 😀😀😀😀😀😀😀😀😀😀😀😀 👩‍👩‍👦‍👦大陆身份证、港澳台证件、海外证件、工作证、护照、营业执照、捐款证书、柜机汇出、发票、旅游证件图、金融定制、结婚证、离婚证👩‍👩‍👦‍👦 😀😀😀😀😀😀😀😀😀😀😀😀 👩‍👩‍👦‍👦美团电商、国内机票、国际机票、酒店预定、国内火车票、运营推广、电影、演唱票、税务单、捐血、浏览器、Stayify👩‍👩‍👦‍👦 😀😀😀😀😀😀😀😀😀😀😀😀 👩‍👩‍👦‍👦国内银行、海外银行、贷款a…

2 Oct 2026, 10:34 UTC212 viewsread 7 November 2026
Photo

8989看图王强势活动中......... 😍😍😍😍😍 ⚠️有【旺财作图】【图册New】【8989看图王】 【2345看图王】等等一系列爆火作图软件 卡密出售价格优惠 先测后买 部分软件支持【手机使用】全部开放测试 /使用欢迎品鉴 ⚠️全场折扣: 💥月卡,季卡,年卡6️⃣折优惠!💥 ⚠️注册即送: 💥注册成功联系客服领取一小时测试!💥 合作从第一次信任开始!更新优化从未停止! 😍祝力业绩报表!爆单暴富😍 欢迎 购买//测试 8989看图王全部功能开放中 咨询客服: @DY_8989 🥰🥰🥰🥰🥰🥰🥰🥰

2 Oct 2026, 10:34 UTC194 viewsread 7 November 2026
Photo

➡️国内银行说明:包含转账,收款,余额,明细,分享信息,回单,转账失败等等。 中国银行,中国网页,工商银行,工商网页,招商银行,中信银行,泸州银行,农商银行,广发银行,建设银行,交通银行,兴业银行,邮政银行,农业银行,华夏银行,浦发银行,民生银行,光大银行,平安银行,香港银行,台湾银行,银行扫码转出,流水账单,回单

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

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

“8989看图王 作图软件 【支持测试】P图软件 zizi67888 zt8989ktw8” (@zt8989ktw8_2), 4,867 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/zt8989ktw8_2.

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.