Telegram RegisterThe public register of Telegram
Telegram profile photo for 猪猪发卡商户通知群

Channel

猪猪发卡商户通知群

@QinTanov

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

17,450subscribers

-1,357 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002470212151
TypeChannel
Username@QinTanov
Created3 March 2025 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/QinTanov

Topic

Gaming — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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

17,45018,80718,128.57 August 202612 November 2026
62 measurements spanning 97 days, net -1,357. 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 17,246–19,011 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
12 Nov 2026, 13:1917,450-47
10 Nov 2026, 08:1017,497-49
8 Nov 2026, 17:1617,546-59
7 Nov 2026, 09:4517,605-48
6 Nov 2026, 07:3817,653-39
5 Nov 2026, 06:5017,692-28
4 Nov 2026, 07:2117,720-62
3 Nov 2026, 09:3517,782-78
2 Nov 2026, 10:3517,860-126
1 Nov 2026, 08:2017,986-5
31 Oct 2026, 08:3517,991-12
30 Oct 2026, 08:5718,003-6
29 Oct 2026, 10:4818,009-4
28 Oct 2026, 12:3118,013-8
27 Oct 2026, 14:1618,021-8
26 Oct 2026, 17:3618,029-8
25 Oct 2026, 20:3818,037-14
24 Oct 2026, 22:2718,051-20
23 Oct 2026, 21:2018,071+2
22 Oct 2026, 23:5818,069first reading

Engagement

15 posts held, back to 3 March 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 78 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.1%
avg views ÷ 17,450 subscribers
Avg views / post
4,030
3 posts measured
Reaction rate
0.322%
reactions ÷ views · ER floor
Posts in window
3
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 14 November 2026
Posts held15 (3 March 2025 – 14 November 2026)
Views total12,099
Reactions total39
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 05:31 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

Photos
1
Links
1

Lifetime counters from Telegram’s own channel header, read 15 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

56 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 82.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4682.1%
❤712.5%
🕊11.79%
🤬11.79%
🥰11.79%

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 8 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 56 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 3 March 2025 to 14 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: 1 of 3 posts held from the last 30 days (33.3%) 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).

14 Nov 2026, 12:20 UTC293 views12 reactionsread 15 November 2026

1.优化了支付响应的速度 2.新增抖音支付接口 通知群 1134291781 一键加入我们

👍12

2 Nov 2026, 17:10 UTC206 views11 reactionsread 3 November 2026
Forwarded from @XFchart

1.修复敌方回城飞过去bug 2.bp查询回退成查历史 3.优化XF驱动通信 增加安全性 4.修复自瞄角度调节无效 5.适配抢先服所有功能 6.增加经济差绘制标识 7.启动器新增驱动刷录失败自动收集日志可一键上传 以上均可直接在启动器直接更新 点我下载启动器

👍11

1 Nov 2026, 15:35 UTC≈11,600 views16 reactionsread 15 November 2026
Photo

🐷 猪猪发卡|你负责成交,猪猪负责发货! 🎁 新商户注册即送 18.8 元! 💰 低费率|稳定结算|支持 U 结算 ⚡ 自动发货|微信/支付宝|一键搬家 🤖 绑定 TG 机器人,成交及时提醒 🌐 官网:zhuzhufaka.cn 📢 官方频道:@QinTanov 🤖 通知机器人:@zhuzhufaka_assist_bot 🐧 商户通知群:1134291781 点我一键加入商户通知群

👍12❤4

2 Sept 2026, 16:43 UTC142 views4 reactionsread 3 September 2026
Forwarded from @XFchartFile

更新内容: 1.更新指定海克斯 2.更新指定重铸 这两功能准确率均不可能达到100% 有错误的概率 自行判断使用 海克斯指定选好了它会自动刷新 重铸 你选好了它会自动重铸等待即可 3.完美修复连接失败问题 4.优化自动刷新以及拿牌 完美解决刷新速度太快漏牌问题 5.∞∞∞ 等等 支持平板 手机 模拟器 模拟器推荐使用mumu 安15

👍4

16 Aug 2026, 13:51 UTC860 views7 reactionsread 3 September 2026
Forwarded from @XFchartFile

【XF记牌器】金铲铲之战 · 全赛季通用 别人还在猜对手,你已经看到他的站位了 别人还在手动搜牌,你的英雄已经自动到手了 别人还在纠结三星,你早就知道该不该追了 🎯 对手预测 — 100%准确 🗺️ 站位透视 — 不用切屏 ⭐ 三星预警 — 实时监控 📦 自动拿牌 — 解放双手 🃏 牌堆显示 — 心中有数 🔮 海克斯预测 — 先人一步 所有功能支持观战 · Root设备/模拟器通用 全面开放公益 所有Bug均已修复完毕 如有问题请及时反馈给客服 @xfzong

👍4❤2🥰1

14 Aug 2026, 04:02 UTC≈1,050 viewsread 3 September 2026
Forwarded from @XFchartFile

XF公益内核v24.0.更新内容: 1.适配王者最新版本 支持双版本一个包 局内换肤美化等所有功能均已更新完毕 2.优化发烫性能等问题 赞助版算法已同步更新完毕 点我加入XF官方频道 点我加入XF官方交流群

13 Aug 2026, 19:08 UTC≈1,080 views3 reactionsread 3 September 2026
Forwarded from @yuzhou86File

更新日志: 适配最新版王者,无效果用户请去应用商店更新最新版王者 ------------------------ 点击此频道头像即可验证电报或使用过验证文件 点击加入宇宙交流群

👍2🕊1

11 Aug 2026, 18:53 UTC≈1,260 viewsread 3 September 2026
Forwarded from @A6neihe123File

解密已经更新 适配全部机型全部设备 无需专属驱动 最新算法解密,bug留言 国际服并未同步解密更新 A6的驱动已经被特征,请不要使用加载

4 Aug 2026, 08:13 UTC≈1,210 viewsread 3 September 2026
Forwarded from @A6neihe123File

🅰️6️⃣ 【A6 王者荣耀】🥰 公益 纯算法解密 ⚠️纯外部算法解密 不修改任何内存 ⚠️ ✅不三方 ✅不异常 ✅无视加密 📲丝滑流畅 Ui简洁好看 支持全安卓 ✅支持全英雄内核触摸自瞄 动态算法自瞄 ✅支持全皮肤美化 一键体验全皮肤 ✔️官方频道 ❤️官方交流

2 Aug 2026, 10:19 UTC≈1,550 views2 reactionsread 3 September 2026
Forwarded from @yuzhou86Photo

8月1,一个版本稳定到姥姥家

👍1🤬1

1 Aug 2026, 13:51 UTC526 views1 reactionsread 3 September 2026
Forwarded from @A6neihe123File

🅰️6️⃣ 【A6 王者荣耀】🥰 公益 纯算法解密 ⚠️纯外部算法解密 不修改任何内存 ⚠️ ✅不三方 ✅不异常 ✅无视加密 📲丝滑流畅 Ui简洁好看 支持全安卓 ✅支持全英雄内核触摸自瞄 动态算法自瞄 ✅支持全皮肤美化 一键体验全皮肤 ✔️官方频道 ❤️官方交流

❤1

30 Jul 2026, 21:00 UTC≈1,190 viewsread 3 September 2026
Forwarded from @XFchartFile

XFJCC记牌器-v460.更新内容: 1.新增自动卡牌[开启后可自动识别牌库进行卡牌 比如说 对手A某个棋子子已经有7张了可自动进行锁定拿牌] 2.修复对手预测和网页共享 3.优化脚下显示逻辑[只有在备战时间的时候显示] 4.优化整体hub点击屏幕显示穿透 5.修复闪退 6.修复验证问题 7.修复自动拿牌bug 8.修复自动解绑失效 9.自动对齐重新适配mumu电脑手机和平板 ️ 💙一键了解XF赞助

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

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 7 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.

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

“猪猪发卡商户通知群” (@QinTanov), 17,450 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/QinTanov.

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.