Telegram RegisterThe public register of Telegram
Telegram profile photo for 中国素材|国内素材

Channel

中国素材|国内素材

@jsjsbb110

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

2,548subscribers

-3 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-1001604964595
TypeChannel
Username@jsjsbb110
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/jsjsbb110

Growth

2,5482,5532,550.57 August 2026 — 2,551 subscribers7 August 2026 — 2,551 subscribers8 August 2026 — 2,548 subscribers11 August 2026 — 2,553 subscribers17 August 2026 — 2,548 subscribers7 August 202617 August 2026
5 measurements spanning 10 days, net -3. 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 2,547–2,554 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 15:582,548-5
11 Aug 2026, 06:062,553+5
8 Aug 2026, 12:352,548-3
7 Aug 2026, 17:032,551no change
7 Aug 2026, 16:512,551first reading

Engagement

10 posts held, back to 11 December 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
9.97%
avg views ÷ 2,548 subscribers
Avg views / post
254
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 10 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 23 July 2026
Posts held10 (11 December 202423 July 2026)
Views total254
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:03 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.

Recent posts

23 Jul 2026, 11:35 UTC254 viewsread 7 August 2026
Photo

📱『富贵转账免TRX能量助手 核心优势』📱 1⃣: 告别传统转账需频繁充值TRX的繁琐流程,有效避免因操作失误、地址填错导致的U资产损失。 2⃣: 智能托管、不限时间,随时随地即刻响应! 3⃣: 强大多功能集成:支持实时汇率查询、地址多签授权风险检测,全方位守护资金安全。 第四: 全网正规转账价格,真正做到高品质、低费率。 4⃣: 自有储备能量,无中间商赚差价,转错包退!全网担保30万U,百万级靓号ID认证@trx1 。 🔗能量租用·秒级到账⭐ 🖥官方客服: @fuguitrx0 ⤵️⤵️⤵️⤵️⤵️⤵️⤵️⤵️⤵️⤵️ 🚀立即体验: @fuguitrx1Bot

14 Jun 2026, 16:30 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

3 Jun 2026, 14:41 UTC914 viewsread 7 August 2026
Photo

🎊USDT转账手续费只要0.1TRX🎊 无论对方地址有没有USDT 转账都只要0.1TRX 闪电到账 超级省钱 绝对真实 业界良心推荐手续费品牌 点击下方开始使用0.1转账 ⤵️⤵️⤵️⤵️⤵️ @TRXpandabot @TRXpandabot @TRXpandabot ⤴️⤴️⤴️⤴️⤴️

9 Oct 2025, 11:48 UTC≈4,610 viewsread 7 August 2026
Photo

🚀Ai联盟中文板块正式上线🚀 🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊 我们的宗旨:将集合所有AI生态系统为TG用户服务/结合全球最先进AI群体给予用户体验🛒 ⤵️⤵️⤵️⤵️⤵️⤵️⤵️⤵️ 我们的覆盖:我们围绕工作,娱乐,社群管理,以及更多有利于用户的板块开发👌 ⤵️⤵️⤵️⤵️⤵️⤵️⤵️⤵️ 我们的产品优势:我们的联盟系统将为所有加盟我们的社群群主提供大量长期的收益。以及流量扶持技术。可以让所有加盟我们的用户自己搭建自己的品牌,我们提供技术扶持。做到真正意义上的共同进退,互利互惠的局面 加盟咨询热线:@JoinAIboss 最强AI联盟机器人:@JoinAIRobot

26 Mar 2025, 08:58 UTC≈6,890 viewsread 7 August 2026
Photo

✅海外盘招代理(外汇盘,币盘,商城盘,刷单盘,授权冷钱包盗U盘) ✅资金自管✅7*24H客服✅提供全球通道 ✅本公司总部直招各大代理商 🌐所有盘口均已上架应用商店❗️ ① 🔰外汇盘(合约+期权秒合约)功能:全盘可控,产品有外汇,大宗产品,加密货币,指数,可做秒合约,代理后台可控秒合约,已上架应用商店ios,谷歌均已上架 ②🔰币盘交易所(功能:全盘可控秒合约,合约,矿机,发售币)钱包可授权登录,免注册,0报毒风险,已上架应用商店ios,谷歌均已上架 ③🔰TikTok商城,facebook商城(内嵌)开店模式 ④🔰刷单盘(抢单,卡针) ⑤🔰 盗U盘(冷钱包授权盗U) ⭕️合作模式:资金自管,安全无忧,入金抽点,可挂代理地址(客户入金到你的地址,在按照平台抽成,返佣给平台) ⭕️好旺上压15000U,欢迎各界精英加入我们共同创造财富 📞发财热线 :@FFAA999

11 Dec 2024, 07:51 UTC≈6,130 viewsread 7 August 2026
Photo

海外全球源头引流粉商:@fxll6 【 可接交友粉/股民粉/网赚粉/币粉/各类交友软件定制上粉 】 海外全球源头数据渗透:@kanpianv2

11 Dec 2024, 07:51 UTC≈7,770 viewsread 7 August 2026
Photo

1,币盘(交易所) 2,国际股票盘 3,海外商城盘 4,外汇盘 SA7(外汇+黄金+期权秒合约) 四盘均已上架应用商店 ‼️招代理‼️ ‼️官方招代理‼️ 另外诚意招渠道商 一对一客服单独对接,24小时在线! 2️⃣4️⃣工作时间:三班倒-2️⃣4️⃣小时至🌞。 【全球支付通道已接入,支持接近200个国家货币支付】诚招东南亚各地大佬代理 支持个人-公司-机构代理商 条件:有实力你来开!合作共赢 💎【优势】💎:独立后台,多级体系,客户信息一眼明了!盘面易懂,不卡不滑!!! 💎【优势】💎:支持代理资金自管(你收钱,反给平台,0几率被黑)保障代理资金安全! ‼️市面上鱼龙混杂 各大招商盘均有渠道商 请各大代理商擦亮眼睛 不要为了高那几个点被黑‼️‼️ (全新平台)均已上架苹果商城和谷歌商城 联系方式 @C

11 Dec 2024, 07:21 UTC≈4,710 viewsread 7 August 2026
Photo

#山西 #旅游 #晋祠 👍东南亚华人交流群

11 Dec 2024, 07:21 UTC≈5,640 viewsread 7 August 2026
Photo

#雪乡 #下雪 #旅游 👍东南亚华人交流群

Showing the 10 most recent of 10 posts we hold for @jsjsbb110. 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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“中国素材|国内素材” (@jsjsbb110), 2,548 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/jsjsbb110.

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.