Telegram RegisterThe public register of Telegram

Channel

泽塔工作室实名接码代付自营地

@zzzkkk

2 usernames

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,683subscribers

+96 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002639901480
TypeChannel
Usernames@ztgzs6 @zzzkkk
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/zzzkkk

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 58% 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 why it has no browse page of its own yet.

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 word for word on 1 other registered channel. 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
@zzzkkk/249 · this entry26 May 2026, 09:50 UTC@ztgzs999/93226 May 2026, 09:50 UTC1.00under a minute
@zzzkkk/256 · this entry8 Jun 2026, 11:17 UTC@ztgzs999/9378 Jun 2026, 11:18 UTC1.00under a minute
@zzzkkk/257 · this entry13 Jun 2026, 18:08 UTC@ztgzs999/93813 Jun 2026, 18:09 UTC1.00under a minute
@zzzkkk/262 · this entry24 Jun 2026, 14:28 UTC@ztgzs999/94124 Jun 2026, 14:29 UTC1.00under a minute
@zzzkkk/268 · this entry26 Jun 2026, 11:22 UTC@ztgzs999/94726 Jun 2026, 11:23 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ztgzs9999 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (90)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 18 May 2026 to 25 July 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).

Across the whole group of 2, the earliest publisher we hold is @zzzkkk — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

1,5871,6831,6357 August 2026 — 1,587 subscribers7 August 2026 — 1,587 subscribers7 August 2026 — 1,591 subscribers7 August 2026 — 1,591 subscribers10 August 2026 — 1,646 subscribers11 August 2026 — 1,652 subscribers13 August 2026 — 1,679 subscribers14 August 2026 — 1,683 subscribers7 August 202614 August 2026
8 measurements spanning 7 days, net +96. 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 1,573–1,697 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:391,683+4
13 Aug 2026, 05:181,679+27
11 Aug 2026, 00:081,652+6
10 Aug 2026, 07:101,646+55
7 Aug 2026, 17:361,591no change
7 Aug 2026, 17:191,591+4
7 Aug 2026, 10:461,587no change
7 Aug 2026, 09:181,587first reading

Engagement

12 posts held, back to 18 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 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
60.6%
avg views ÷ 1,683 subscribers
Avg views / post
1,020
1 post measured
Reaction rate
0.196%
reactions ÷ views · ER floor
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 25 July 2026
Posts held12 (18 May 202625 July 2026)
Views total1,020
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:58 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
11s
Average length
11s

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

13 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 76.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1076.9%
👏17.69%
🔥17.69%
🤣17.69%

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 9 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 13reactions 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 18 May 2026 to 25 July 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

25 Jul 2026, 12:26 UTC≈1,020 views2 reactionsread 7 August 2026
Photo

Grab 实名 + UUPay 开通信用卡,出门更轻松! 🚖💳 还在担心出门没带现金、找零麻烦? 现在只需: ✅ Grab 完成实名认证 ✅ 通过 UUPay 开通信用卡 ✅ 绑定 Grab App 即可享受: 🚕 打车自动扣款,无需携带现金 💳 线上线下消费更方便 ⚡️ 支付快捷,出行更省心 🔒 正规绑定,支付更安全 一部手机,轻松搞定出行支付,让每一次打车都更便捷! 如需了解开通流程,欢迎咨询。 🌐全球话费充值机器人【@hqchfbot】支持u 📞 联系客服 @zzzttt 🛡 防伪888电话:【+88807472695】 🔄 备用客服 @zzzmmm 📡 双向联系机器人: @ztgzs_bot 🌐 代做落地页专题: @ztldy haxicha.com 🔍 查询USDT交易明细并快速统计收支 💰 偷偷看你的朋友你的竞争对手挣了多少钱,有没有瞒着你偷偷发财 🤫💸

1🔥1

4 Jul 2026, 07:22 UTC≈2,040 views2 reactionsread 7 August 2026
Photo

👍基操勿六,牛逼又日常 🇭🇰 香港 ATM 现金代存 ✔️ 香港本地代存服务 ✔️ 跑腿代存港卡 ✔️ 效率快,到账及时(以实际情况为准) ✔️ 美股 / 港股资金周转更便捷 有需要欢迎咨询。 远离诈骗,谨慎交易。 🌐全球话费充值机器人【@hqchfbot】支持u 📞 联系客服 @zzzttt 🛡 防伪888电话:【+88807472695】 🔄 备用客服 @zzzmmm 📡 双向联系机器人: @ztgzs_bot 🌐 代做落地页专题: @ztldy haxicha.com 🔍 查询USDT交易明细并快速统计收支 💰 偷偷看你的朋友你的竞争对手挣了多少钱,有没有瞒着你偷偷发财 🤫💸

2

1 Jul 2026, 14:31 UTC≈1,730 viewsread 7 August 2026
Video

🌐全球话费充值机器人【@hqchfbot】支持u 📞 联系客服 @zzzttt 🛡 防伪888电话:【+88807472695】 🔄 备用客服 @zzzmmm 📡 双向联系机器人: @ztgzs_bot 🌐 代做落地页专题: @ztldy haxicha.com 🔍 查询USDT交易明细并快速统计收支 💰 偷偷看你的朋友你的竞争对手挣了多少钱,有没有瞒着你偷偷发财 🤫💸

26 Jun 2026, 11:22 UTC≈1,730 views1 reactionsread 7 August 2026
Photo

国际 Visa 信用卡|批量开卡|全球支付 ✔️ 一人多卡 ✔️ 每张卡独立信息 ✔️ 支持批量开通 ✔️ 适用于众多支持 Visa 支付的国际平台(具体以平台规则为准) 🌐 覆盖云服务、AI 工具、SaaS 软件、海外订阅等多种支付场景。 🌐全球话费充值机器人【@hqchfbot】支持u 📞 联系客服 @zzzttt 🛡 防伪888电话:【+88807472695】 🔄 备用客服 @zzzmmm 📡 双向联系机器人: @ztgzs_bot 🌐 代做落地页专题: @ztldy haxicha.com 🔍 查询USDT交易明细并快速统计收支 💰 偷偷看你的朋友你的竞争对手挣了多少钱,有没有瞒着你偷偷发财 🤫💸

1

24 Jun 2026, 14:28 UTC≈1,660 views1 reactionsread 7 August 2026
Photo

📌 支付宝/微信代付服务|淘宝代购代付|外卖代订|中国手机话费充值|全球话费充值|eSIM购买服务:环球充机器人: @hqchfbot 🤖 专业团队长期运营,高效响应、稳定服务 ✨ 📞 联系客服 @zzzttt 🛡 防伪888电话:【+88807472695】 🔄 备用客服 @zzzmmm 📡 双向联系机器人: @ztgzs_bot 🌐 代做落地页专题: @ztldy haxicha.com 🔍 查询USDT交易明细并快速统计收支 💰 偷偷看你的朋友你的竞争对手挣了多少钱,有没有瞒着你偷偷发财 🤫💸

1

23 Jun 2026, 13:56 UTC≈1,650 views1 reactionsread 7 August 2026
Photo

当年我离成为世界首富只差一点,那天我和马斯克坐村口抽烟,他跟我说了一句“我们做AI吧”,我回他“我们两个糙大汉怎么能做呢”,于是马斯克自己单干了。数年后看到他成名的那一刻,我才知道当年他说的不是拼音。

🤣1

13 Jun 2026, 18:08 UTC≈2,310 views0 reactionsread 7 August 2026
Photo

🌍 全球充值,一步搞定! 想要更方便地完成海外通信充值? 关注我们的频道,轻松解决 全球话费充值 与 eSIM 在线购买需求! ✅ 核心服务 📱 全球运营商话费充值 覆盖多国家/地区运营商,在线下单,快速到账。 🌐 eSIM 在线购买 即买即用,无需实体卡,适合出国旅行、跨境业务、海外生活。 💳 支持 USDT 支付 支付方式灵活,操作更便捷。 🤖 全自动系统 自助下单,自动处理,省时省心。 ⚡️ 充值秒到账 流程高效,快速完成通信续费。 👉 立即体验: @hqchfbot 👉 立即体验: @hqchfbot 👉 立即体验: @hqchfbot

8 Jun 2026, 11:17 UTC≈2,150 viewsread 7 August 2026

联系客服 @zzzttt 防伪888电话:【+88807472695】 备用客服 @zzzmmm 双向联系机器人: @ztgzs_bot 代做落地页专题: @ztldy haxicha.com 查询USDT交易明细并快速统计收支 偷偷看你的朋友你的竞争对手挣了多少钱,有没有瞒着你偷偷发财

7 Jun 2026, 11:45 UTC≈1,730 views2 reactionsread 7 August 2026
Forwarded from @ztgzs7Photo

☁️云服务器 🌎阿里云,100u起充,充500打95折,充1000打85折 🌍腾讯云,100u起充,充500打95折,充1000打85折 🌍华为云,100u起充,充500打95折,充1000打85折 🌍AWS(亚马逊云)200u起充,充1000打9折 🌍Google (谷歌云)200u起充,充1000打9折 🌍azure (微软云)200u起充,充1000打9折 ➡️所有云账号都是匿名 ➡️可接受任何行业 ➡️无需个人银行卡 ➡️技术支持365天 ➡️账号都是付款后立刻发货 ➡️我们接受USDT 付款 ➡️开户充值有优惠 业务联系:@ztgzs 备用号联系:@ztgzsby haxicha.com 查询USDT交易明细并快速统计收支 偷偷看你的朋友你的竞争对手挣了多少钱,有没有瞒着你偷偷发财

2

28 May 2026, 11:10 UTCviews —

泽塔工作室实名接码代付自营地 pinned «1.支付宝微信代付,paypal信用卡外国代付 2.企业备案域名长期大量出租,无视行业 3.各种外国网站实名认证KYC,外国人高难度实名 4.自营能量兑换机器人,trx兑换机器人 5.网易云信,网易易盾提供成品企业认证,个人认证账号 6.欧盟德国英国🇪🇺苹果开发者账号 7.百度统计与百度站长通用号,长期大量出货。。 8.飞机竞价网站代实名,飞机内部频道推广展现 9.各种IDC实名,网站实名个人实名企业实名 10.各种短信签名平台实名,稳定大厂 11.聚名实名,专业服务一条龙解决各种难题 12.E签宝广告代付,代签正规签约…»

26 May 2026, 09:50 UTC≈2,720 views2 reactionsread 7 August 2026
Photo

聚名专业户,每天都在实名聚名账户。 个人实名企业实名,全套人脸实名模板,包白名单模板 专业聚名大户,专业解决各种难题!!! =================================== 联系客服 @zzzttt 防伪888电话:【+88807472695】 备用客服 @ztgzsby 双向联系机器人: @ztgzs_bot 代做落地页专题: @ztldy 全球话费直冲,支持usdt充值:@hqchfbot haxicha.com 查询USDT交易明细并快速统计收支 偷偷看你的朋友你的竞争对手挣了多少钱,有没有瞒着你偷偷发财

2

18 May 2026, 05:07 UTC≈3,180 views2 reactionsread 7 August 2026

1.支付宝微信代付,paypal信用卡外国代付 2.企业备案域名长期大量出租,无视行业 3.各种外国网站实名认证KYC,外国人高难度实名 4.自营能量兑换机器人,trx兑换机器人 5.网易云信,网易易盾提供成品企业认证,个人认证账号 6.欧盟德国英国🇪🇺苹果开发者账号 7.百度统计与百度站长通用号,长期大量出货。。 8.飞机竞价网站代实名,飞机内部频道推广展现 9.各种IDC实名,网站实名个人实名企业实名 10.各种短信签名平台实名,稳定大厂 11.聚名实名,专业服务一条龙解决各种难题 12.E签宝广告代付,代签正规签约 13.大批量出企业公众号,大量出货 14.开飞机大会员价格实惠正规渠道开 15.专业PayPal代付,CF dynadot GNAME等可PAYPAL支付 16.虚拟信用卡代开,代实名,可绑定大部分海外平台支付 17.香港流量卡,国内免翻墙上网 18.代办个体.企业营业执照,代刻公章,代签各种授权书 19.国际

1👏1

Showing the 12 most recent of 12 posts we hold for @zzzkkk. 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 — 85,217 of 1,478,351entries 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.

Forward network

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

“泽塔工作室实名接码代付自营地” (@zzzkkk), 1,683 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/zzzkkk.

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.