Photo, posted without a caption
😢213😱130😭67🥴27💔18🌚17💩15🤨13
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪

Channel
@ltscxk
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,313subscribers
-165 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001862264271 |
|---|---|
| Type | Channel |
| Username | @ltscxk |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/ltscxk |
Technology — 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 90% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 08:25 | 3,313 | -10 |
| 4 Nov 2026, 06:20 | 3,323 | -5 |
| 1 Nov 2026, 06:56 | 3,328 | -8 |
| 29 Oct 2026, 14:39 | 3,336 | -6 |
| 26 Oct 2026, 12:16 | 3,342 | -7 |
| 23 Oct 2026, 21:08 | 3,349 | -10 |
| 20 Oct 2026, 22:37 | 3,359 | -3 |
| 17 Oct 2026, 17:18 | 3,362 | -4 |
| 14 Oct 2026, 06:38 | 3,366 | -5 |
| 10 Oct 2026, 15:14 | 3,371 | -11 |
| 4 Oct 2026, 22:42 | 3,382 | -12 |
| 25 Sept 2026, 13:17 | 3,394 | -27 |
| 15 Sept 2026, 02:19 | 3,421 | -2 |
| 11 Sept 2026, 13:41 | 3,423 | -13 |
| 7 Sept 2026, 04:37 | 3,436 | -9 |
| 2 Sept 2026, 16:24 | 3,445 | -10 |
| 30 Aug 2026, 14:35 | 3,455 | -9 |
| 27 Aug 2026, 06:27 | 3,464 | -7 |
| 24 Aug 2026, 02:47 | 3,471 | -7 |
| 20 Aug 2026, 09:52 | 3,478 | first reading |
20 posts held, back to 12 May 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 20 posts for this entry, the most recent from 13 July 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
1,490 reactions across 20 posts, in 22 distinct kinds. The most used accounts for 38.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 568 | 38.1% | |
| 😢 | 213 | 14.3% | |
| 💩 | 188 | 12.6% | |
| 😱 | 130 | 8.72% | |
| ❤ | 110 | 7.38% | |
| 😭 | 90 | 6.04% | |
| 🥴 | 27 | 1.81% | |
| 👏 | 18 | 1.21% | |
| 💔 | 18 | 1.21% | |
| 🔥 | 18 | 1.21% | |
| 🌚 | 17 | 1.14% | |
| 🥰 | 15 | 1.01% | |
| 😘 | 13 | 0.872% | |
| 🤨 | 13 | 0.872% | |
| 🍌 | 12 | 0.805% | |
| 🤬 | 11 | 0.738% | |
| 😈 | 9 | 0.604% | |
| 😁 | 5 | 0.336% | |
| 🤩 | 5 | 0.336% | |
| 🫡 | 5 | 0.336% | |
| 2 further kinds | 5 | 0.336% |
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 20 of the 20 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,490 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 May 2024 to 13 July 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Photo, posted without a caption
😢213😱130😭67🥴27💔18🌚17💩15🤨13
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
瓜子加速器随机id 每次白嫖1天,官方有领会员活动还能再嫖1天 目前速度还不错速速白嫖
👍55❤5💩2😁2
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
网盘机器人原理及如何搭建同款机器人 源码看评论区
❤6💩4
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
网盘机器人 随便写了个玩玩 @pan_share_bot 使用方法:直接向机器人发送文件即可,会直接输出分享链接和文件专属uuid 说明: 是看到这个WangPanBOT机器人才写的,不是和这个机器人源码一样的!
❤37👍13🔥13👏12🥰12🤩5💩1😘1
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
猎豹加速器随机id教程 https://bbs.binmt.cc/thread-136014-1-1.html
💩6
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
狗急由于是朋友开的,所以就删掉啦
💩21🤬11👍4🤣1
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
𝙐𝙣𝙨𝙩𝙤𝙥𝙥𝙖𝙗𝙡𝙚 祝愿我在极品广附大联盟 获得个𝘪𝘯𝘤𝘳𝘦𝘥𝘪𝘣𝘭𝘦成绩呀 让我数学压轴1,2题稳如老狗,第三题也临危不乱 英语激发自己的潜力来个105/120,哈哈 Generally speaking , with 𝑐𝑜𝑛𝑓𝑖𝑑𝑒𝑛𝑐𝑒 and 𝑝𝑒𝑟𝑠𝑒𝑣𝑒𝑟𝑎𝑛𝑐𝑒, I am ready to conquer the challenges ahead, and I firmly believe that I will achieve 𝑜𝑢𝑡𝑠𝑡𝑎𝑛𝑑𝑖𝑛𝑔 results in the 大联盟 examination.
👍28💩7❤5🤣2
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
飞鱼vpn随机id 每次可以用2个小时 香港速度50兆左右,延迟很低 tg网盘下载 http://t.me/pan_share_bot?start=404ee6a1-9fc0-4059-b118-b9bff7343495
👍62💩10❤7⚡1😘1
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
华夏vpn破解 去除卡密效验 实际上是tube来的,开发者给它简化ui和破解
👍41💩12❤3😘1
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
v2ray内置订阅教程 冬瓜滴mt论坛账号,欢迎各位关注一下 https://bbs.binmt.cc/thread-134799-1-1.html?mobile=2
👍10💩5
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
team vpn破解会员 速度一般般,还能用 公告只是说不想,不是说不能干了,而且我现在在享乐中所以不算数啦
👍47💩10❤2
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
💨😤😤🥰 明天61了,我也要过最后一个61了记录一下哈哈
💩15👍5
Signed 𝓭𝓸𝓷𝓰𝓰𝓾𝓪
Showing the 12 most recent of 20 posts we hold for @ltscxk. 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.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“冬瓜滴小社” (@ltscxk), 3,313 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/ltscxk.
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.