Telegram RegisterThe public register of Telegram
Telegram profile photo for 📣新开公群

Channel

📣新开公群

@app22

2 usernames

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

140,385subscribers

-17,788 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001981927738
TypeChannel
Usernames@app22 @DingJian
Created4 June 2023 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live27 October 2026
Measurements held82
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/app22

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 8 August 2026 and assigned it the closest of 31 fixed categories, at 54% 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

4158,71079,357140,3856 August 202627 October 2026
82 measurements spanning 82 days, net -17,788. 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, most recent 20 of 82
Measured (UTC)SubscribersChange
27 Oct 2026, 20:10140,385-332
26 Oct 2026, 20:17140,717-367
25 Oct 2026, 20:00141,084+133,674
25 Oct 2026, 19:297,410-133,946
24 Oct 2026, 18:08141,356-485
23 Oct 2026, 15:00141,841+134,388
22 Oct 2026, 19:377,453-134,798
22 Oct 2026, 13:36142,251-491
21 Oct 2026, 06:09142,742-378
20 Oct 2026, 04:26143,120+135,630
20 Oct 2026, 00:397,490-135,935
19 Oct 2026, 05:10143,425-206
18 Oct 2026, 08:29143,631-307
17 Oct 2026, 11:08143,938+136,402
16 Oct 2026, 20:277,536-136,616
16 Oct 2026, 13:49144,152-409
15 Oct 2026, 15:18144,561-388
14 Oct 2026, 17:51144,949+137,340
13 Oct 2026, 22:067,609-137,889
13 Oct 2026, 07:17145,498first reading

Engagement

188 posts held, back to 4 June 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 144 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.477%
avg views ÷ 140,385 subscribers
Avg views / post
670
94 posts measured
Reaction rate
1.79%
reactions ÷ views · ER floor
Posts in window
94
of 188 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 28 October 2026
Posts held188 (4 June 2023 – 28 October 2026)
Views total62,992
Reactions total1,125
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Oct 2026, 03:54 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

Links
83

Lifetime counters from Telegram’s own channel header, read 28 October 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

1,702 reactions across 183 posts, in 18 distinct kinds. The most used accounts for 87.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,48487.2%
❤1408.23%
😭170.999%
🤣170.999%
🖕100.588%
👎70.411%
👏70.411%
💩60.353%
🤔30.176%
😍20.118%
🦄20.118%
❤‍🔥10.059%
💯10.059%
😁10.059%
😱10.059%
🤩10.059%
🤬10.059%
🤮10.059%

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

Measured over the 188 most recent posts we hold, published 4 June 2023 to 28 October 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

28 Oct 2026, 02:54 UTC52 views2 reactionsread 28 October 2026

附近人全网最高价格200一单秒结账 欢迎大小团队带对接记录单价跳槽+10 +20 +30 😀😀😀即日起: 10单奖励金额💰👌👌 20单奖励金额💰👌👌👌 30单奖励金额💰👌👌👌 50单奖励金额💰👌👌👌 金牌客服 @Bhuahua22 @Bhuahua22 https://t.me/+GmYHHvOQs0FjYjc9 https://t.me/+K3Q6ze_Ec9tkZGQ1

👍2

27 Oct 2026, 14:46 UTC241 views16 reactionsread 28 October 2026

📱抖音关注📱 ⚠️⚠️⚠️长期项目,无限收人⚠️⚠️⚠️ 📱抖音关注回关发两张图片就得10元评论 一个账号一天账号可以关注30+稳定不封号 每天可做 ⚡️做单流程:我发送指定评论视频链接,然后你改头像名字,关注他的回复,回关了发两张图片就得10元,每天轻松300➕ ⬇️⬇️📱📱📱📱⬇️⬇️ ⚡️做单客服:@shun5189 ⚡️做单群:https://t.me/+Mo1120APUF01NTBk

👍14❤1😍1

27 Oct 2026, 13:29 UTC269 views11 reactionsread 28 October 2026

项目名称: 星辉空降se料招各种卡车/码车/下载付/登陆付/扫码付/链接付(空降大盘可测试任何入金方式) 项目介绍:空降料招京东公户/格力公户以及各种平台拉出来的公户 高价招扶贫卡盘/取现卡/储蓄卡/信用卡/商家卡等各种卡都要 可维护 招各大银行直扫/破额 单多不罚站 24小时招支付宝个人/经营/商家码车和各种APP拉出来的设置码/时效码都要全部色料 招各种链接付和冷门下载付(可保量)日量稳定 支持测试,来稳定的大小车合作 料不符合十倍赔付 招一切入金渠道 自身优势:稳定三年色料老牌空降/24小时营业,日量三百万 公司频道@qiye 单多不罚站 射速快服务好待遇优厚 联系人:@nuli @zige @guli @qipo 群组:https://t.me/+_mpyn-ENLWM0MzJl

👍11

27 Oct 2026, 12:19 UTC248 views11 reactionsread 28 October 2026

Telegram里找资源,还在一个群一个群地翻? 群组、频道、电影、视频、音乐、文件…… 直接发送关键词,几秒帮你从海量 Telegram 内容中找到结果。 ✅ 中文关键词直接搜索 ✅ 频道、群组、视频、图片、文件分类筛选 ✅ 支持收藏、翻页和每日推荐 ✅ 还能邀请好友赚 USDT 🔍 你负责输入关键词,剩下的交给 TG 中文搜索。 👉 立即体验

👍11

27 Oct 2026, 10:27 UTC276 views11 reactionsread 28 October 2026

涨价啦📱涨价啦📱 散户 1️⃣号保底利润2️⃣5️⃣0️⃣ 团队 1️⃣号保底利润3️⃣0️⃣0️⃣-4️⃣0️⃣0️⃣ ✅当天上三个号奖励38.88 ✅当天上五个号奖励88.88 ✅当天上十个号奖励188.88 ✈️唯一一家不做虚假宣传的附近人,能显示附近人就来找我换钱,外面的代挂普遍都是一两个小时就挂逼了,来登号给我上,直接利润拉满,简单省事无限续租!没有任何套路,上号能显示秒射立结! 做单客服:@vz66688 做单群:https://t.me/+8bpjKDBFgRcwNWEx 上押群:https://t.me/+WYvyGRSJH-04NDU1

👍11

27 Oct 2026, 02:20 UTC353 views4 reactionsread 28 October 2026

需:点位2️⃣0️⃣%招拿现车队零风险模式,菠菜直盘,公司赌客人民币换U上分,小白可全程指导,手把手带你赚钱,保证做一周本金翻倍,准备1万U起做,支持验盘100%保证 纯充值菠菜款,因反诈部门,银行机构,监管日益严重,各种限额,风控,卡款,车队苦不堪言,特开线下取现业务,此项目在市场上己开放两个月很稳定,0风险0司法 优 势:【把你包成U商去交易,可以问客户买U用途,可以签订免责合同,确认料性后再交易,专群双押作业,每天保量,罚站补贴388U起】 【菠菜面交U商模式】 专群双押鸽子费500U锁单后出发→添加微信/qq走U商流程后 见面→拿现金→转小额U测试地址→钱在手里验钞没问题扣除利润转尾款给客户→拿钱走人→利润提前拿到手里,利润差我们会补给客户再上分 对接人: @CSZF8860 @CSZF8860 发单频道 https://t.me/yaoqianshu6888

👍4

26 Oct 2026, 21:20 UTC372 views3 reactionsread 28 October 2026

【需】 内容:色料直盘招 8折帮还京东白条中邮贷款 维维卡贷 美团借款 二道小额还花呗 各类车贷房贷网贷 各种商城礼品卡 招各类卡车码车 小额0-1000 123存个人微信支付宝码车 联系人:@Plhny @PLHyy @PLHpaofenba

👍3

26 Oct 2026, 18:57 UTC374 views6 reactionsread 28 October 2026

精聊自营盘诚招实物车 业务需求:手机 黄金 显卡 手表等各种核销 已落地 无尾叨 料性透明 车队无一被按 汇率置顶 量大不罚站 所有物品保真保到货[量大可当面验货] 安全至上 共同致富 对接人:@M1996312

👍6

26 Oct 2026, 15:28 UTC439 views15 reactionsread 28 October 2026

👋👋需求😀😃😀😀😀😀码接回U 卡接回U 24小时有料 【招】支付宝个码 经营码 微信个码 经营码 聚合码 【招】万内个人卡 平台卡 公户 扫街 【招】各种能进款通道 通通来 上车就射 【發】招各种链接付丝滑通道 【發】小车扶持,大车包养。 联系人:@zs68689 @mc786678 频道(群):https://t.me/+SySqPqgDwRpjZGFl

👍15

26 Oct 2026, 14:24 UTC423 views12 reactionsread 28 October 2026

机房团队寻苹果换汇IM,任小聊,发票,bc等盘口,一手支持担保,稳定结算的来,日发十万起,保质保量联系 @offo66 https://t.me/+LfN8BX-9rztiZWVl

👍12

26 Oct 2026, 13:22 UTC448 views14 reactionsread 28 October 2026

招几个私人微信一天300一天24小时结账不要用市面上的那些业务微信跟我们比我们是私人用 一般续租都是十多天想赚钱的小弟也可以联系@Xy_22222222 @xyxyxy12325

👍14

26 Oct 2026, 05:30 UTC522 views12 reactionsread 28 October 2026

😣🤩😟😣 全天真地址机器人秒出 白天假地址1️⃣👍秒 全天真地址6️⃣👍秒 (19:30后卡10分钟回单) 夜间真地址1️⃣1️⃣❤️5️⃣👍秒 客服👌@luosen666

👍11❤1

Showing the 12 most recent of 188 posts we hold for @app22. 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 8 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 27 October 2026 — this entry's latest reading, not the date you are reading this.

“📣新开公群” (@app22), 140,385 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/app22.

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.