Channel
@yugecjxinde55440
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,229subscribers
+368 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002644790211 |
|---|---|
| Type | Channel |
| Username | @yugecjxinde55440 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/yugecjxinde55440 |
Giveaways & airdrops — 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 14 September 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 00:56 | 3,229 | +22 |
| 14 Sept 2026, 12:19 | 3,207 | +6 |
| 11 Sept 2026, 00:38 | 3,201 | +16 |
| 5 Sept 2026, 15:38 | 3,185 | +9 |
| 1 Sept 2026, 12:33 | 3,176 | +15 |
| 29 Aug 2026, 09:47 | 3,161 | +19 |
| 26 Aug 2026, 08:32 | 3,142 | +30 |
| 23 Aug 2026, 15:07 | 3,112 | +27 |
| 20 Aug 2026, 01:12 | 3,085 | +47 |
| 16 Aug 2026, 16:25 | 3,038 | +36 |
| 12 Aug 2026, 20:13 | 3,002 | +55 |
| 10 Aug 2026, 06:47 | 2,947 | +64 |
| 7 Aug 2026, 11:57 | 2,883 | +22 |
| 6 Aug 2026, 21:16 | 2,861 | first reading |
8 posts held, back to 30 July 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 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
12 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 91.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 91.7% | |
| 👍 | 1 | 8.33% |
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 4 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 12 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 30 July 2026 to 6 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.
🎉 玉哥向粉丝派发福利啦~ 🎁 奖品清单 • 卤蛋2.88元 × 10 • 鸡腿6.66元 × 5 • 标准版猪脚饭18.88元 × 3 • 豪华版猪脚饭28.88元 × 3 • 顶配版猪脚饭50元 × 1 🛡️ 参与条件 • 加入 广州佛山修车出击大队🦅 • 加入 抽奖专栏 • 加入 玉哥的出击心得与日记🍀 • 参加抽奖后需在 广州佛山修车出击大队🦅 内发言30次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10无限宝石 • 祝福上限：10次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 开奖时间 • 2026-08-12 15:30:00 📜 抽奖说明 🈲 自言自语 左右互搏 满屏盖楼 脚本凑数 兑奖联系 @verdant55440 ✨ 愿好运伴随每一位参与者，祝大家好运！
今晚是甜啦啦：@ouo_003 （婉崽）
@aaaggg6688此号已被盗，目前在骗定，我是从来不收定的，千万别信拉黑他！！！！！😭
❤2
🕊请教一下大家，周五的时候约了周日（今晚），但是老师账号显示最近上线时间是昨天晚上，也就是说今天一天没上线，老师频道今天也没发任何信息，我今天下午四点钟发信息给老师，目前还是显示未读状态。请问我还需要先过去吗？这种是什么情况？？😂😂
【永乐报告】https://t.me/guangfoyongle2020 【所在位置】南海 【老师艺名】小小 【联系方式】@Xxiao0720 【验证留名】玉哥是城市玩家（@verdant55440） 【验证时间】2026.8.1 【上课价位】600p 【人照几成】8.5成 【颜值分数】8.5分（满分10分，朱茵王祖贤之流算10分） 【身材分数】8分（满分10分，车模超模般的身材可打10分） 【课表服务】全做，洗催做，水中萧，深喉，制服，69，事后萧，舔蛋等（全做，做大部分，做一半，几乎全没做） 【态度分数】10分（满分10分） 【优点缺点】 优点：颜值高。态度极好！主动！热情！女友感强！情绪价值满满，自来熟，健谈。服务好，口交深喉技术很好！大蟒蛇！服务主动做足做满，穴紧。600p性价比高。 缺点：黄皮，不是三点粉。 【推荐程度】很推荐！ 【体验细节】 很久没做工兵的我，今天，破例做了一次！其实说起来也是…
❤2
Photo, posted without a caption
小小老师：@Xxiao0720
❤3👍1
【嫩妹报告】https://t.me/GZNMHEJI 【老师艺名】77 【联系方式】@qiqi888871 【所在位置】黄埔 【验证留名】玉哥是城市玩家（ @verdant55440 ） 【验证时间】7月底 【修车费用】700p 【颜值身材】人照8成，完美胸型，极品身材。 【服务内容】xcz🐍吻 【服务态度】听话、配合，态度好，服务好。 【优点缺点】 优点：极品身材，完美胸型，听话，配合，蛇饱，看着你舌吻，新科室安全。 缺点：课室较小 【推荐程度】推荐 【体验细节】 又是一个10k粉丝的老师，依稀记得，我上一次去的一个有10k粉丝的老师是。。。。咳咳咳，算鸟算鸟~，往事不再提了。 好，言归正传，我准时到达课室，是新环境，是新小区，新公寓，什么都比较新，新到旁边的房门的塑料纸都还没扯下来，虽然是偏了一点，但胜在比较安全！个人感觉宁愿偏一点，更安全更好一点。 开门后，公寓房间较小，还有是映入眼帘的是…
❤4
Showing the 8 most recent of 8 posts we hold for @yugecjxinde55440. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 1 registered channel — 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“玉哥的出击心得与日记🍀” (@yugecjxinde55440), 3,229 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/yugecjxinde55440.
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.