LEECO1111 已补充 200个
❤2🥰2🤣1
Signed Leeco

Channel
@xuehuashe
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
12,024subscribers
-463 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001304915829 |
|---|---|
| Type | Channel |
| Username | @xuehuashe |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/xuehuashe |
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 98% 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 |
|---|---|---|
| 17 Nov 2026, 13:18 | 12,024 | -11 |
| 14 Nov 2026, 07:10 | 12,035 | -15 |
| 11 Nov 2026, 12:05 | 12,050 | -3 |
| 9 Nov 2026, 14:39 | 12,053 | -5 |
| 8 Nov 2026, 08:21 | 12,058 | -14 |
| 7 Nov 2026, 03:30 | 12,072 | -3 |
| 6 Nov 2026, 03:19 | 12,075 | -1 |
| 5 Nov 2026, 04:17 | 12,076 | -4 |
| 4 Nov 2026, 05:17 | 12,080 | -5 |
| 3 Nov 2026, 03:16 | 12,085 | -1 |
| 1 Nov 2026, 02:38 | 12,086 | -6 |
| 31 Oct 2026, 01:37 | 12,092 | -5 |
| 29 Oct 2026, 23:38 | 12,097 | -6 |
| 28 Oct 2026, 20:55 | 12,103 | -5 |
| 27 Oct 2026, 16:39 | 12,108 | -7 |
| 26 Oct 2026, 14:27 | 12,115 | -6 |
| 25 Oct 2026, 13:16 | 12,121 | -2 |
| 24 Oct 2026, 12:34 | 12,123 | -2 |
| 23 Oct 2026, 10:50 | 12,125 | -7 |
| 22 Oct 2026, 11:46 | 12,132 | first reading |
27 posts held, back to 18 March 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 76 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 27 (18 March 2024 – 10 November 2026) |
| Views total | 4,340 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 10:20 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.
204 reactions across 25 posts, in 11 distinct kinds. The most used accounts for 42.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 86 | 42.2% | |
| 👍 | 69 | 33.8% | |
| 👏 | 22 | 10.8% | |
| 😁 | 13 | 6.37% | |
| 🔥 | 5 | 2.45% | |
| 💋 | 2 | 0.98% | |
| 🤣 | 2 | 0.98% | |
| 🥰 | 2 | 0.98% | |
| 🎉 | 1 | 0.49% | |
| 😇 | 1 | 0.49% | |
| 🤔 | 1 | 0.49% |
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 25 of the 27 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 204 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 18 March 2024 to 10 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.
Telegram’s own ‘edited’ marker: 0 of 4 posts held from the last 30 days (0%) 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).
LEECO1111 已补充 200个
❤2🥰2🤣1
Signed Leeco
没想到那么快就没了,等我补充。。
🤣1
Signed Leeco
Leeco-雪花社 ❄️ pinned a photo
最近花了一点时间,做了个AI小工具,叫许个价,目前内测中 🎯 说一句想买什么、多少钱才买,比如「猫砂 6L,一袋 20 以内」。许个价替你看京东、淘宝的线报: · AI 来判断是不是你要的那件 · 算出到你手上的价(按袋、按包换算;凑单、PLUS、88VIP 你够不够) · 没到价、不是你要的,一条都不推 · 未来会越来越懂你 到价了推到你的企业微信群、飞书群或 Bark,推送里写清价格怎么算的。推到家里的群,家里人也能一起看。 之前一直想做这个,无奈太忙一直搁置,现在赶上线了,希望能帮大家节省到时间。 邀请码:LEECO1111,共200个名额 用 Google 账号在 xugejia.com 注册时填,后续开放更多第三方登录 用这个码注册,还会送你 1个邀请码。 用着有问题直接留言或来群里说:@xuehuashe_chat
❤3
Signed Leeco
gpt 16点重置,赶紧蹬。
👍1
Signed Leeco
https://x.com/leecobaby/status/2101954931829645588?s=20 做了个概念验证, 简单一句话: 留个心愿单,想要什么,排除淘金币,排除拍多件,单件价格低于多少元提醒我。 🙈会有人需要吗?可能会做成开放平台,谁都能接入进来。
👍10❤3
Signed Leeco
冒个泡,证明我还在,如果能给我加点访问,很感谢。 https://x.com/leecobaby/status/2095541196571697228?s=20
❤6😇1
Signed Leeco
我不会私聊任何人 如果私聊了一定是骗子不是我.
❤7
Signed Leeco
Happy 牛 Year ~🎇📈
👏20👍3❤2🎉1
Signed Leeco
别人维护的,感觉挺好,分享下
👍12❤3
Signed Leeco
https://0xallen.notion.site/c38f97a75f2a4fbbac3cb2eaa257d791?v=ab5f015e8c0e466197622e6750b89a68
❤16👏1🔥1
Signed Leeco
BTC 突破 10W, 见证历史 📈
🔥4❤2👍1
Signed Leeco
Showing the 12 most recent of 27 posts we hold for @xuehuashe. 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Leeco-雪花社 ❄️” (@xuehuashe), 12,024 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/xuehuashe.
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.