Telegram RegisterThe public register of Telegram
Telegram profile photo for 【银图熊猫做图王】-转账做图-网银生成器

Channel

【银图熊猫做图王】-转账做图-网银生成器

@yintu_zuotui

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

93subscribers

-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-1001695340622
TypeChannel
Username@yintu_zuotui
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 November 2026
Measurements held7
Confirmed unchanged4 times, most recently 18 November 2026
On Telegramt.me/yintu_zuotui

Topic

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

Growth

9195937 August 2026 — 95 subscribers9 August 2026 — 95 subscribers15 August 2026 — 94 subscribers23 August 2026 — 93 subscribers13 September 2026 — 92 subscribers30 September 2026 — 91 subscribers24 October 2026 — 93 subscribers7 August 202624 October 2026
7 measurements spanning 78 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 90–96 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Oct 2026, 13:5893+2
30 Sept 2026, 12:1991-1
13 Sept 2026, 02:1992-1
23 Aug 2026, 04:2793-1
15 Aug 2026, 17:2394-1
9 Aug 2026, 12:3195no change
7 Aug 2026, 10:4395first reading

Engagement

7 posts held, back to 4 November 2023 — the 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 7 posts for this entry, the most recent from 27 August 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

7 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤342.9%
👍342.9%
🔥114.3%

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

Measured over the 7 most recent posts we hold, published 4 November 2023 to 27 August 2024, 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

27 Aug 2024, 17:46 UTC616 viewsread 9 August 2026
File

🌟 通知 通知 通知 🌟 🌟欢迎新老顾客服使用银图--熊猫做图王🌟 银图--熊猫做图王更新至9.0版本10月05更新🌟🌟🌟 本次新增Newton交易所、香港、新加坡、印度、印尼、越南、阿塞拜疆、澳大利亚、巴西、玻利维亚、俄罗斯、厄瓜多尔、菲律宾、哥伦比亚、哈萨克斯坦、韩国、加拿大、柬埔寨、马来西亚、美国、孟加拉、秘鲁、墨西哥、南非、尼日利亚、日本、台湾、泰国、土耳其、危地马拉、西班牙、英国多个界面 ✉️公告: 注意:软件下载或者使用过程可能被360等杀毒软件误杀,请不要阻止软件运行,将软件加入白名单即可。 ✉️公告: 注意:下载新版本请将旧版本文件删除,保存好自己原先的卡密,重新创建文件夹下载安装 新版本可测试,测试卡密请联系客服 购买卡密 续费联系客服: @yintu_keful 【只有这一个官方频道】htt…

8 Mar 2024, 13:21 UTC≈1,150 viewsread 9 August 2026
Photo

🎧🎧🎧🎧唯一客服号:@XMkefu_1 🎧🎧🎧🎧 新春到来之际,熊猫工作室全体员工向大家拜个早年 祝大家:幸福平安!阖家欢乐! 新版本可测试,测试卡密请联系客服 购买卡密 续费联系客服: @yintu_keful 【只有这一个官方频道】https://t.me/yintu_zuotui

5 Nov 2023, 09:38 UTC≈3,020 views3 reactionsread 9 August 2026

📌通知: 软件将于今日进行全面更新优化。 1️⃣新增酒店订单界面 💕艺龙,飞猪,携程💞 2️⃣新增平安银行回单最新界面 3️⃣新增多个国外页面 4️⃣新增安卓短信支持国外平台界面 5️⃣新增支付宝最新版支付宝聊天界面 6️⃣更新建设银行到最新 7️⃣更新国内所有银行到最新 8️⃣修复护照名称不能修改问题 9️⃣修复常用功能卡顿问题 🔟修复欧易部分用户显示图标问题 ⑪ 修复交通广告图新旧问题 ⑫ 修复微信账单不显示财付通问题 ⑬ 新增抖音充值,消费账单界面 ⑭ 新增数字人民币银行充值详情界面 ⑮ 新增欧易充值提现英文页面 ⑯ 新增币安中英文充提界面 🔴危地马拉🇬🇹,哈萨克🇰🇿,沙特,厄尔多瓜,约旦🇯🇴,玻利维亚🇧🇴,柬埔寨🇰🇭,土耳其🇹🇷,南非🇿🇦 🟠新增印尼🇮🇩到23个界面 🟡新增印度🇮🇳到36个界面 🟢新增越南🇻🇳到35个界面 🔵新增俄罗斯🇷🇺到11个界面 🟣新增阿塞拜疆🇦🇿到7个界面 ⚫️新增秘鲁到11个界面 其他反…

❤1👍1🔥1

5 Nov 2023, 09:38 UTC≈2,390 views2 reactionsread 9 August 2026
Photo

猫熊街機APP做图王、 转账作图 身份证 USDT 生成器 机票 结婚证 离婚证 营业执照 工作证.身份证 国内银行:可以做 转账 收款 余额 冻结 支付宝,可做 转账 收款 余额 口令红包 等 微信,可做 转账 收款 余额 冻结 等 软件购买联系客服: @yintu_keful 官方频道, https://t.me/yintu_zuotui

❤1👍1

5 Nov 2023, 09:37 UTC≈2,130 views1 reactionsread 9 August 2026
Photo

猫熊街機APP做图王、 转账作图 身份证 USDT 生成器 机票 结婚证 离婚证 营业执照 工作证.身份证 国内银行:可以做 转账 收款 余额 冻结 支付宝,可做 转账 收款 余额 口令红包 等 微信,可做 转账 收款 余额 冻结 等 软件购买联系客服: @yintu_keful 官方频道, https://t.me/yintu_zuotui

❤1

4 Nov 2023, 05:27 UTC≈1,660 views1 reactionsread 9 August 2026
Photo

猫熊街機APP做图王、 转账作图 身份证 USDT 生成器 机票 结婚证 离婚证 营业执照 工作证.身份证 国内银行:可以做 转账 收款 余额 冻结 支付宝,可做 转账 收款 余额 口令红包 等 微信,可做 转账 收款 余额 冻结 等 软件购买联系客服: @yintu_keful 官方频道, https://t.me/yintu_zuotui

👍1

4 Nov 2023, 05:27 UTC≈1,310 views0 reactionsread 9 August 2026
Photo

猫熊街機APP做图王、 转账作图 身份证 USDT 生成器 机票 结婚证 离婚证 营业执照 工作证.身份证 国内银行:可以做 转账 收款 余额 冻结 支付宝,可做 转账 收款 余额 口令红包 等 微信,可做 转账 收款 余额 冻结 等 软件购买联系客服: @yintu_keful 官方频道, https://t.me/yintu_zuotui

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

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

“【银图熊猫做图王】-转账做图-网银生成器” (@yintu_zuotui), 93 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/yintu_zuotui.

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.