Channel
@welove_liubai
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
334subscribers
-7 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001587729336 |
|---|---|
| Type | Channel |
| Username | @welove_liubai |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 12 September 2026 |
| On Telegram | t.me/welove_liubai |
Gaming — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 5 Sept 2026, 07:55 | 334 | -3 |
| 29 Aug 2026, 08:44 | 337 | -2 |
| 21 Aug 2026, 14:28 | 339 | -2 |
| 14 Aug 2026, 08:00 | 341 | no change |
| 14 Aug 2026, 07:48 | 341 | first reading |
14 posts held, back to 21 October 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 1 page 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 14 posts for this entry, the most recent from 5 August 2025. An engagement rate over an empty window would be a number about nothing.
478 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 39.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5447161525204695089 | 189 | 39.5% | |
| ❤🔥 | 109 | 22.8% | |
| ❤ | 83 | 17.4% | |
| 💋 | 59 | 12.3% | |
| 🍓 | 30 | 6.28% | |
| 💘 | 8 | 1.67% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 13 of the 14 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 478 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 21 October 2024 to 5 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @welove_liubai. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 14 most recent posts we hold for this entry, published 21 October 2024 to 5 August 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Наверное,мне стоило написать об этом раньше,но лучше поздно,чем никогда Я уже не увлекаюсь хонкаем так,как раньше,но смелости так и не нашлось написать об этом,да и оставлять аудиторию без контента тоже не особо хотелось. Всем тем,кто играет на данный момент желаю удачи в крутках,любите Любай дальше!!! Канал останется как архив. Ваша владелица @nsttxq
❤🔥33❤12💋6💘3🍓2
Снова анонс мерча с лучшей женщиной !!! 🤩🤩🤩
custom 544716152520469508963❤6💋6
😚⋆⁺｡˚⋆˙‧₊☀︎ ʟɪᴜʙᴀɪ ☽₊‧˙⋆˚｡⁺⋆😎 - #Liubai cr: ??? on lofter.
❤16custom 54471615252046950899💋6
😚⋆⁺｡˚⋆˙‧₊☀︎ ʟɪᴜʙᴀɪ ☽₊‧˙⋆˚｡⁺⋆😎 - #Liubai cr: faguojinkouxiaob... on lofter.
❤🔥21custom 54471615252046950899💋1
😚⋆⁺｡˚⋆˙‧₊☀︎ ʟɪᴜʙᴀɪ ☽₊‧˙⋆˚｡⁺⋆😎 - #Liubai cr: moyuart on lofter.
custom 544716152520469508923💋2💘1
😚⋆⁺｡˚⋆˙‧₊☀︎ ʟɪᴜʙᴀɪ ☽₊‧˙⋆˚｡⁺⋆😎 - #Liubai cr: meitianshihuobul... on lofter.
❤20custom 54471615252046950897💘1
😚⋆⁺｡˚⋆˙‧₊☀︎ ʟɪᴜʙᴀɪ ☽₊‧˙⋆˚｡⁺⋆😎 - #Liubai cr: genzhexinyangkeh… on lofter.
❤16❤🔥10custom 54471615252046950896🍓1
Liubai ˗ˋˏ ♡ ˎˊ˗ pinned a photo
➖➖➖➖➖ ➖ ➖➖➖ Все что от вас требуются это ;; 1.Написать псевдо + местоим. 2.Прислать каналы в которых вы адм/владелец 3.Должность (вп или контент,можно оба!) 4.Какими приложениями пользуйтесь для поиска контента Присылать анкеты в лс (@nsttxq) или комментарий!!
custom 544716152520469508913
😚⋆⁺｡˚⋆˙‧₊☀︎ ʟɪᴜʙᴀɪ ☽₊‧˙⋆˚｡⁺⋆😎 - #Liubai cr: @kuroo_riin on twt.
custom 544716152520469508925❤9❤🔥1🍓1
😚⋆⁺｡˚⋆˙‧₊☀︎ ʟɪᴜʙᴀɪ ☽₊‧˙⋆˚｡⁺⋆😎 - #Liubai cr: @yaevako_ on twt.
🍓19custom 544716152520469508910💋6💘3
😚⋆⁺｡˚⋆˙‧₊☀︎ ʟɪᴜʙᴀɪ ☽₊‧˙⋆˚｡⁺⋆😎 - #Liubai cr:@Rh_canaanaa on twt.
💋22❤4custom 54471615252046950893❤🔥1
Showing the 12 most recent of 14 posts we hold for @welove_liubai. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@welove_liubai named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“Liubai ˗ˋˏ ♡ ˎˊ˗” (@welove_liubai), 334 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/welove_liubai.
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.