Telegram RegisterThe public register of Telegram
Telegram profile photo for 吃鸡小分队精选榜(多人差评永久封杀)

Channel

吃鸡小分队精选榜(多人差评永久封杀)

@xmcjxfdhcpd1

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

9,137subscribers

+2,791 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1003918575360
TypeChannel
Username@xmcjxfdhcpd1
CreatedBetween 1 April 2026 and 18 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live8 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/xmcjxfdhcpd1

Growth

6,3469,1377,741.519 August 2026 — 6,346 subscribers19 August 2026 — 6,346 subscribers20 August 2026 — 6,503 subscribers24 August 2026 — 7,218 subscribers27 August 2026 — 7,649 subscribers30 August 2026 — 8,018 subscribers2 September 2026 — 8,429 subscribers8 September 2026 — 9,137 subscribers19 August 20268 September 2026
8 measurements spanning 20 days, net +2,791. 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 5,927–9,556 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 12:199,137+708
2 Sept 2026, 21:348,429+411
30 Aug 2026, 11:298,018+369
27 Aug 2026, 20:247,649+431
24 Aug 2026, 10:047,218+715
20 Aug 2026, 21:286,503+157
19 Aug 2026, 23:006,346no change
19 Aug 2026, 22:456,346first reading

Engagement

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

ERR · 30 days
15.2%
avg views ÷ 9,137 subscribers
Avg views / post
1,390
8 posts measured
Reaction rate
0.284%
reactions ÷ views · ER floor
Posts in window
8
of 8 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. It is computed over the 5 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held8 (18 August 202628 August 2026)
Views total11,142
Reactions total24
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 21:14 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

Video runtime
50s
Average length
13s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

24 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1875.0%
👍28.33%
🥰28.33%
💩14.17%
🤡14.17%

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

Measured over the 8 most recent posts we hold, published 18 August 2026 to 28 August 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 Aug 2026, 13:26 UTC757 viewsread 28 August 2026
Photo

夜色蜜镜,主打女友般陪伴和暧昧性陪玩,高颜值女仆店号称厦门女仆店颜值排名前三 照片请查看频道: https://t.me/yesemijingnvpu 介绍:专门做厦门市女仆的恋爱体验馆,主打高端私密,妹子都是18岁左右的学生,颜值高能聊,主动开放,🉑️🐍🉑️摸🉑️亲 地点:高崎艾德花园附近 服务价格:638/小时(小分队专属价格) 饮食:小食/饮料 营业时间:15:00-01:00 预约流程是: 预约时联系 @xmxiaohannvpu 双向 @xmhuawuquebot 选好妹子后,安排到店,都已安排好,不满意可更换,直接与前台沟通,停车方便,扫码现金都安全。

Signed 鱼 (小分队群主小分队之魂)

28 Aug 2026, 13:25 UTC695 viewsread 28 August 2026
Photo

草莓家园,主打女友般陪伴和暧昧性陪玩 照片请查看频道: https://t.me/xmhulinvpudian666 介绍:专门做厦门市女仆的恋爱体验馆,主打高端私密,妹子都是18岁左右的学生,颜值高能聊,主动开放,🉑️🐍🉑️摸🉑️亲🉑92 地点:湖边湾璟B区 服务价格:600/小时(小分队专属价格)(92需加钱) 饮食:小食/饮料 预约流程是: 预约时联系 @xmxiaohannvpu 双向 @xmhuawuquebot 选好妹子后,安排到店,都已安排好,不满意可更换,直接与前台沟通,停车方便,扫码现金都安全。

Signed 鱼 (小分队群主小分队之魂)

28 Aug 2026, 07:09 UTC≈1,230 viewsread 28 August 2026
Photo

#松韵 #海沧 #6米 #69 #kiss 海沧刚下海不久的嫩妹,服务内容:69,Kiss,鸳鸯浴无套口,激情爱爱。各种制服 三点粉嫩 可纯可欲水多多,顶级服务全能服务 联系 @XMdoubao 双向联系 @limzay89bot 个人频道:https://t.me/DB0000010

Signed 鱼 (小分队群主小分队之魂)

27 Aug 2026, 08:59 UTC≈2,060 views1 reactionsread 28 August 2026
Photo

#豆包 #6米 #湖里 #🐍吻 #69 #嫩妹 湖里新人初下海,主动听话,乖巧配合,制服诱惑,深情🐍吻,帮洗,69互舔,激情爱爱,情趣挑逗,白月光既视感 联系 @doub133 频道:https://t.me/doub1331 双向私聊: @limboub331bot

1

Signed 鱼 (小分队群主小分队之魂)

19 Aug 2026, 08:59 UTC≈1,160 views4 reactionsread 19 August 2026
Photo

#子欣 #同安 #6米 #嫩妹 已视频验证,同安新人今天刚开,服务待验,服务内容:共浴 调情 漫游 胸推滑臀 耳语挑逗 亲器 无套吹箫 性感黑丝 秘书服 高跟诱惑 各种姿势爱爱,姿势配合 不催 主打哥哥情绪价值 联系 @hujianzhou12 频道 https://t.me/huxiaoqian0 机器人@xiaoqiandjiqirbot

4

Signed 鱼 (小分队群主小分队之魂)

19 Aug 2026, 07:55 UTC≈1,190 views7 reactionsread 19 August 2026
Photo

#晓晓 #湖里 #7米 #69 #制服丝袜 已视频验证,服务态度好配合度高不催事,服务内容:浪漫波推臀推,指尖调情舌尖漫游 ,鸳鸯浴丝袜情趣内衣,🉑69🉑无套口,多种姿势激情爱爱 联系 @XXa6672 双向 @Xxj5673hjbot 频道 https://t.me/hhua62

5👍1🥰1

Signed 鱼 (小分队群主小分队之魂)

18 Aug 2026, 05:03 UTC≈2,080 views8 reactionsread 19 August 2026
Photo

#小m酱 #湖里 #8米 #69 #蟒🐍 #拍视频 之前上榜过,粉嫩皮肤,温柔可人,年轻有活力姿势多容易出水会调情,🉑69🉑🐍🉑拍视频🉑sm 分两种课程 联系 @ssee678 频道 https://t.me/zzccyyooiii123 双向: @xiaomm990_bot

5👍1💩1🥰1

Signed 鱼 (小分队群主小分队之魂)

18 Aug 2026, 04:48 UTC≈1,970 views4 reactionsread 19 August 2026
Photo

#陈奶油 #湖里金缘湾 #7米 #亲亲 #D🐻 之前上榜过,在校生温柔体贴,初恋女友傻白甜清小纯,服务内容:制服丝袜 胸推 指划驾鸯戏水 亲亲 69 口交 激情爱爱调情任君解锁 联系 @chenny88 频道 https://t.me/ndndbfnfnflox111 双向 @sjeijs39737_bot

3🤡1

Signed 鱼 (小分队群主小分队之魂)

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

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

“吃鸡小分队精选榜(多人差评永久封杀)” (@xmcjxfdhcpd1), 9,137 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/xmcjxfdhcpd1.

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.