Telegram RegisterThe public register of Telegram
Telegram profile photo for 会员贴纸/表情/图标/贴纸表情/宝藏资源

Channel

会员贴纸/表情/图标/贴纸表情/宝藏资源

@bansui1

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

11,036subscribers

+3,018 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1004339149626
TypeChannel
Username@bansui1
Description优质频道推荐 @TGCD18 #表情包 #头像 #图标 #Emoji #sicker #png #壁纸 #贴纸 #宝藏 #资源 #高清 #像素 #电报 #bot
CreatedBetween 1 June 2026 and 1 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live13 November 2026
Measurements held40
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/bansui1

Topic

Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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

7,76311,0369,399.511 August 2026 — 8,018 subscribers11 August 2026 — 8,018 subscribers11 August 2026 — 8,037 subscribers15 August 2026 — 8,339 subscribers18 August 2026 — 7,763 subscribers21 August 2026 — 7,872 subscribers25 August 2026 — 8,176 subscribers28 August 2026 — 8,362 subscribers31 August 2026 — 8,519 subscribers3 September 2026 — 8,705 subscribers8 September 2026 — 9,021 subscribers12 September 2026 — 9,136 subscribers16 September 2026 — 9,304 subscribers28 September 2026 — 8,964 subscribers5 October 2026 — 9,210 subscribers12 October 2026 — 9,569 subscribers15 October 2026 — 9,872 subscribers18 October 2026 — 10,042 subscribers19 October 2026 — 10,074 subscribers20 October 2026 — 10,118 subscribers21 October 2026 — 10,156 subscribers22 October 2026 — 10,150 subscribers23 October 2026 — 10,236 subscribers24 October 2026 — 10,294 subscribers25 October 2026 — 10,415 subscribers26 October 2026 — 10,441 subscribers27 October 2026 — 10,454 subscribers28 October 2026 — 10,475 subscribers29 October 2026 — 10,499 subscribers30 October 2026 — 10,512 subscribers31 October 2026 — 10,546 subscribers1 November 2026 — 10,647 subscribers3 November 2026 — 10,717 subscribers4 November 2026 — 10,744 subscribers5 November 2026 — 10,809 subscribers6 November 2026 — 10,827 subscribers7 November 2026 — 10,840 subscribers8 November 2026 — 10,857 subscribers11 November 2026 — 10,900 subscribers13 November 2026 — 11,036 subscribers11 August 202613 November 2026
40 measurements spanning 94 days, net +3,018. 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 7,272–11,527 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 40
Measured (UTC)SubscribersChange
13 Nov 2026, 23:5511,036+136
11 Nov 2026, 07:3710,900+43
8 Nov 2026, 21:2210,857+17
7 Nov 2026, 10:5510,840+13
6 Nov 2026, 10:1010,827+18
5 Nov 2026, 08:4610,809+65
4 Nov 2026, 04:5810,744+27
3 Nov 2026, 01:1610,717+70
1 Nov 2026, 23:0610,647+101
31 Oct 2026, 22:2810,546+34
30 Oct 2026, 20:2710,512+13
29 Oct 2026, 20:0110,499+24
28 Oct 2026, 17:4110,475+21
27 Oct 2026, 20:1010,454+13
26 Oct 2026, 19:2010,441+26
25 Oct 2026, 19:5110,415+121
24 Oct 2026, 16:2810,294+58
23 Oct 2026, 19:4710,236+86
22 Oct 2026, 21:1710,150-6
21 Oct 2026, 16:0110,156first reading

Engagement

47 posts held, back to 1 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 41 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.344%
avg views ÷ 11,036 subscribers
Avg views / post
38.0
23 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
23
of 47 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 13 November 2026
Posts held47 (1 August 2026 – 13 November 2026)
Views total873
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 02:52 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
96

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

7 reactions across 3 posts, in 4 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%
🍌228.6%
❤114.3%
👎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 3 of the 47 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 47 most recent posts we hold, published 1 August 2026 to 13 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 23 posts held from the last 30 days (4.35%) 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).

13 Nov 2026, 06:09 UTC28 viewsread 15 November 2026

#频道互推 #相似推荐 ------------------------------ 📢 热搜吃瓜 - SOSO吃瓜🔥 📢 【东南亚猎奇新闻】抖音吃瓜悬赏曝光 📢 猎奇吃瓜榜💯(吃瓜 美女 沙雕 搞笑 ) 📢 社工库机器人推荐频道分享开户🤖开盒 📢 缅甸缅北柬埔寨菲律宾-华人中文新闻骗子曝光 📢 中文吃瓜中心沙雕日常 🍉 📢 发布悬赏交易频道 📢 混剪小屋🫦 抖音风裸舞抖音曝光 📢 全球新闻头条/吃瓜/全网曝光 投稿骗子曝光频道 📢 东南亚搜索工具丨吃瓜头条丨搞笑段子丨内涵视频 📢 星耀【海外担保】业务大厅 📢 吃瓜ღ猎奇【抖音吃瓜】 📢 社工库机器人 推荐聊天群 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励

6 Nov 2026, 17:15 UTC85 viewsread 15 November 2026

#频道互推 #相似推荐 ------------------------------ 📢 社工库机器人推荐频道 📢 货多多号铺🛒 📢 海外社交账户数据筛选平台 📢 吃瓜ღ猎奇【抖音吃瓜】 📢 武汉学生会 (重生版) 📢 猎奇吃瓜榜💯(吃瓜 美女 沙雕 搞笑 ) 📢 吴哥时报 📢 💬东南亚华人社区出海交流群 📢 暗网赚钱项目灰产骗局曝光🪬 📢 中文反差萝莉母狗探花偷拍吃瓜🔞 📢 🔍中文搜索 超级索引 全能搜片 📢 会员贴纸/表情/图标/贴纸表情 📢 星耀出海 优质供需 海外项目资源 📢 精选福利AI短剧AI成人短剧AI机器人 📢 吃瓜色色 📢 中文吃瓜中心沙雕日常 🍉 📢 海的那边有什么 📢 📣【U盟供需】限时免费 📢 混剪小屋🫦 抖音风裸舞抖音曝光 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励

4 Nov 2026, 09:06 UTC65 viewsread 15 November 2026

搞笑贴纸 使用链接 https://t.me/addstickers/pack_f24bd610_by_stickerporter_bot

4 Nov 2026, 09:06 UTC40 viewsread 15 November 2026

搞怪表情包 使用链接 https://t.me/addstickers/pack_94b86a0e_by_stickerporter_bot

4 Nov 2026, 09:06 UTC37 viewsread 15 November 2026

美女跳舞来了 使用链接 https://t.me/addstickers/pack_a96dfee8_by_stickerporter_bot

4 Nov 2026, 09:06 UTC27 viewsread 15 November 2026

超级可爱小猫 使用链接 https://t.me/addstickers/pack_461dffd0_by_stickerporter_bot

4 Nov 2026, 09:06 UTC27 viewsread 15 November 2026

😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😄😄😄😃😃😀😄😃😄😃😄😃😄😃😄😃😄😃😄😀😃😄😃😄😃😄😃😄😃😀😄 点击查看完整版 添加使用 https://t.me/addemoji/pack_b9c91b0e_by_stickerporter_bot

4 Nov 2026, 09:06 UTC26 viewsread 15 November 2026

😃😄😀😃😄😃😄😃😄😃😄😃😃😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😄😃😃😀😄😃😄😃😄😃😄😃😄😄😄 点击查看完整版 添加使用 https://t.me/addemoji/pack_70ef43f5_by_stickerporter_bot

4 Nov 2026, 09:06 UTC52 viewsread 15 November 2026

搞怪 使用链接 https://t.me/addstickers/pack_94b86a0e_by_stickerporter_bot

4 Nov 2026, 09:06 UTC41 viewsread 15 November 2026

无厘头 使用链接 https://t.me/addstickers/pack_94b86a0e_by_stickerporter_bot

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

Posts edited after publishing

@bansui1 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
11 November 2026
Most recent edit
11 November 2026

Posts recorded as deleted after publishing

We recorded 6 posts on @bansui1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
3 November 2026
Most recent seen missing
13 November 2026
Median time before seen missing
37 hours
Seen missing in the last 30 days
6

Mentions

Named by 13 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.

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

“会员贴纸/表情/图标/贴纸表情/宝藏资源” (@bansui1), 11,036 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/bansui1.

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.