Telegram RegisterThe public register of Telegram
Telegram profile photo for 【支持测试】8989看图王 p图软件 【支持测试】8989看图王 p图软件 zt8989ktw zizi67888 8989ktw.com

Channel

【支持测试】8989看图王 p图软件 【支持测试】8989看图王 p图软件 zt8989ktw zizi67888 8989ktw.com

@zt8989lktw

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

4,888subscribers

-1,152 since we began measuring on 5 October 2026

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

Register entry

Telegram ID-1003955492867
TypeChannel
Username@zt8989lktw
CreatedBetween 1 April 2026 and 5 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 October 2026
Last confirmed live16 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/zt8989lktw

Topic

Technology — 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 19 October 2026 and assigned it the closest of 31 fixed categories, at 81% 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 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zt8989lktw/120 · this entry15 Jul 2026, 06:42 UTC@ht8989ktw/6515 Jul 2026, 06:45 UTC1.003 minutes
@zt8989lktw/130 · this entry22 Jul 2026, 09:00 UTC@ht8989ktw/7622 Jul 2026, 09:02 UTC1.002 minutes
@zt8989lktw/133 · this entry30 Jul 2026, 16:08 UTC@ht8989ktw/781 Aug 2026, 17:01 UTC1.002 days
@zt8989lktw/134 · this entry2 Aug 2026, 05:38 UTC@ht8989ktw/792 Aug 2026, 05:39 UTC1.00under a minute
@zt8989kttw/7114 Jul 2026, 18:51 UTC@zt8989lktw/120 · this entry15 Jul 2026, 06:42 UTC1.0012 hours
@zt8989kttw/8122 Jul 2026, 08:54 UTC@zt8989lktw/130 · this entry22 Jul 2026, 09:00 UTC1.005 minutes
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
@ht8989ktw6 (5/6 hand-verifiable sample passed)1.002 minutesthis entry (6–0)
@zt8989kttw5 (5/5 hand-verifiable sample passed)1.00under a minute@zt8989kttw (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. 1 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 7 comparable posts for this entry, running 5 June 2026 to 6 November 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 3 channels, the one whose matching posts we hold earliest is @zt8989kttw. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, 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 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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

4,8886,5835,735.55 October 2026 — 6,040 subscribers5 October 2026 — 6,040 subscribers9 October 2026 — 6,508 subscribers14 October 2026 — 6,412 subscribers16 October 2026 — 6,358 subscribers19 October 2026 — 6,309 subscribers22 October 2026 — 6,219 subscribers25 October 2026 — 6,153 subscribers28 October 2026 — 6,583 subscribers1 November 2026 — 6,513 subscribers3 November 2026 — 6,453 subscribers6 November 2026 — 6,557 subscribers10 November 2026 — 6,435 subscribers16 November 2026 — 4,888 subscribers5 October 202616 November 2026
14 measurements spanning 42 days, net -1,152. 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 4,634–6,837 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 13:444,888-1,547
10 Nov 2026, 19:516,435-122
6 Nov 2026, 19:406,557+104
3 Nov 2026, 21:476,453-60
1 Nov 2026, 01:386,513-70
28 Oct 2026, 16:016,583+430
25 Oct 2026, 06:446,153-66
22 Oct 2026, 17:076,219-90
19 Oct 2026, 16:576,309-49
16 Oct 2026, 18:276,358-54
14 Oct 2026, 01:286,412-96
9 Oct 2026, 16:406,508+468
5 Oct 2026, 16:226,040no change
5 Oct 2026, 15:476,040first reading

Engagement

12 posts held, back to 5 June 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 10 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
59.3%
avg views ÷ 4,888 subscribers
Avg views / post
2,900
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 12 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 held12 (5 June 2026 – 6 November 2026)
Views total2,900
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 17:39 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
2m 00s
Average length
1m 00s

Measured directly from 2 videos 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 of the 12 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 5 June 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, 11:17 UTC≈2,900 viewsread 14 November 2026
Photo

8️⃣9️⃣8️⃣9️⃣ 已更新 英文版 英文版链接🤦 https://t.me/zt8989kttw/80 开卡续费联系客服 🤦 @zizi678881 备用客服号 🤦 @duojln8989k 双向机器人联系 🤦@zt8989kttwbot

6 Aug 2026, 10:47 UTC≈1,890 viewsread 14 November 2026
Forwarded from @zt8989kttwPhoto

8️⃣9️⃣8️⃣9️⃣ 【看图王】 😖⚡️苹果17顶部已更新,使用网页版的,直接右键刷新一下就行.使用桌面版的,需要重新下载一下。

6 Aug 2026, 10:16 UTC≈1,680 viewsread 14 November 2026

由于维护需要暂停15分钟不能使用,希望各位老板谅解

2 Aug 2026, 05:38 UTC≈4,210 viewsread 14 November 2026
Photo

👌请您务必加入 @zt8989kttw 频道,避免被冒充着欺骗! 或在购买之前访问官网 web.8989ktw.com 点击联系客服即可确认真假 您也可以打开频道点击联系客服,8989客服的资料中同时拥有以下用户名 @zizi678881 @duojln8989k 谨防上当!

30 Jul 2026, 16:08 UTC≈4,170 viewsread 14 November 2026
Photo

👍👍👍👍专业:手机银行,电脑银行,微信支付宝的转账截图,银行到账短信 身份证 USDT... 等做图生成器,行走江湖必备神器,助力你业绩爆表🤑 ⚡️😖⚡️👍👍👍🙊👹🙊👹👍👍👍 ⚡️感恩相伴,尊享回馈!——用户是我们的上帝 ⚡️为了感谢您的支持,即日起,凡是推荐身边的朋友或同事使用8989看图王软件的老客户一律享受会员价的🫨折! 🫨推荐3个朋友购买月卡赠送1张月卡! 🫨.推荐2个朋友购买季卡赠送1张月卡! 🫨.推荐2个朋友购买年卡赠送1张季卡! 💸开卡续费联系客服 🥰@zizi678881😤 💸备用客服号 🤑 @duojln8989k😤 💸双向机器人联系 🤑@zt8989kttwbot😤 ❤️‍🔥⚡️😖⚡️全新推出【8989看图王】买3送1可测试,祝各位老板发大财,天天爆单🥰🥰🥰🥰🥰🥰🥰

23 Jul 2026, 06:24 UTC≈3,460 viewsread 14 November 2026
Forwarded from @zt8989kttwPhoto

⚡️😖⚡️👍👍👍🙊👹🙊👹👍👍👍 🫨已更新在线网页版手机端,支持试用 🫨 安卓苹果手机正常可以使用。 手机使用,网络好就流畅,有缓存了,就流畅了 🫨 和电脑版账号同步的 《卡密通用》

22 Jul 2026, 09:00 UTC≈4,990 viewsread 14 November 2026
Photo

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

15 Jul 2026, 11:31 UTC≈5,530 viewsread 14 November 2026
Video

请广大用户认准唯一官网 web.8989ktw.com 推荐谷歌浏览器使用。 点击右上角可安装到桌面的教程 开卡续费联系客服 😘 @zizi678881 备用客服号 @duojln8989k 双向机器人联系 😘 @zt8989kttwbot

15 Jul 2026, 06:42 UTC≈2,220 views1 reactionsread 14 November 2026
Photo

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

❤1

12 Jun 2026, 04:42 UTC≈1,680 viewsread 14 November 2026
Video

支付宝微信模拟器 支持苹果安卓使用 开卡续费联系客服 😘 @zizi678881 双向机器人联系 😘@zt8989kttwbot

5 Jun 2026, 14:23 UTC≈1,500 viewsread 14 November 2026
File

使用安装包下载,不用关闭任何杀毒软件 请广大用户认准唯一官网 web.8989ktw.com 网页版链接 8989ktw.com 推荐谷歌浏览器使用。 😍😍😍😍😍😍😍😍🥰🔥 @zizi678881 后续素材更新请上传官网并备注,方便识别!

5 Jun 2026, 14:23 UTC≈1,650 viewsread 6 November 2026
Photo

🔥⭐️🌈各大国内银行,海外银行,定制,机票,加密货币,股票,聊天生成,网络钱包,p图软件🔥🌈❤️ 一共4464个模版 欢迎各位老板来使用 🔥🔥🔥 支持免费测试 开卡续费联系客服🥰@zizi678881🌈🔥❤️

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 6 registered channels — 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.

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

“【支持测试】8989看图王 p图软件 【支持测试】8989看图王 p图软件 zt8989ktw zizi67888 8989ktw.com” (@zt8989lktw), 4,888 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/zt8989lktw.

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.