Telegram RegisterThe public register of Telegram
Telegram profile photo for Черкашня Ксяоми

Channel

Черкашня Ксяоми

@Xiaomi_blenb

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

45subscribers

+2 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002446159028
TypeChannel
Username@Xiaomi_blenb
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held3
Confirmed unchanged5 times, most recently 18 September 2026
On Telegramt.me/Xiaomi_blenb

Growth

4345449 August 2026 — 43 subscribers10 August 2026 — 43 subscribers16 August 2026 — 45 subscribers9 August 202616 August 2026
3 measurements spanning 7 days, net +2. 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 43–45 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 22:3445+2
10 Aug 2026, 16:1643no change
9 Aug 2026, 18:4643first reading

Engagement

17 posts held, back to 10 June 2026the 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 17 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

68 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 61.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4261.8%
custom 53595304441759951061319.1%
custom 534615561966349133957.35%
custom 522423153546863332522.94%
custom 527151946040504799222.94%
custom 544486760894171750022.94%
custom 546772268470190878122.94%

Custom emoji. 6 of the rows above are 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 counts beside them are 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 10 of the 17 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 68 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 10 June 2026 to 31 July 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

31 Jul 2026, 18:32 UTC25 views6 reactionsread 10 August 2026
Photo

Photo, posted without a caption

6

Signed Ксяоме😵

21 Jul 2026, 16:51 UTC52 views6 reactionsread 10 August 2026

Че может нахуй эти скетчи и уйти работать фурри/брони художником на западную аудиторию??? Вроде неплохо получается

4custom 54677226847019087812

Signed Ксяоме😵 #𝑷𝔄𝑻 ‌͍۫۫ ࣪𝔗𝑬𝔑٬︎݄𝑻

19 Jul 2026, 16:13 UTC57 viewsread 10 August 2026

Реакции?🌟

Signed Ксяоме😵 #𝑷𝔄𝑻 ‌͍۫۫ ࣪𝔗𝑬𝔑٬︎݄𝑻

19 Jul 2026, 15:57 UTC55 viewsread 10 August 2026

Потом лоэна ему может дорисую Не факт

Signed Ксяоме😵 #𝑷𝔄𝑻 ‌͍۫۫ ࣪𝔗𝑬𝔑٬︎݄𝑻

19 Jul 2026, 15:57 UTC53 views11 reactionsread 10 August 2026
Photo

Второе пришествие Иисуса Христа Мне лень дорисовывать ему что то, так что жрите че дадут #скетч #геншин

6custom 53595304441759951063custom 52715194604050479922

Signed Ксяоме😵 #𝑷𝔄𝑻 ‌͍۫۫ ࣪𝔗𝑬𝔑٬︎݄𝑻

5 Jul 2026, 19:46 UTC87 views6 reactionsread 10 August 2026
Video

Video, posted without a caption

5custom 53595304441759951061

Signed Ксяоме😵

2 Jul 2026, 04:23 UTC98 views9 reactionsread 10 August 2026
Photo

Продолжение банкета Я их так сука люблю😊 хочу с ними парную теперь пожалуйста Еще раз спасибо чуву!! #скетч #Геншин

5custom 52242315354686333251custom 53461556196634913391custom 53595304441759951061custom 54448676089417175001

Signed Ксяоме😵

23 Jun 2026, 05:41 UTC103 views6 reactionsread 10 August 2026
Photo

Естественно это рисовала не я, поэтому просто похвастаюсь. Заказывала у Чуву две коммишечки с Иллуэнами и своими осами, спасибо ей большое, я более чем довольна👅👅👅 #скетч(к сожалению или к счастью не мои) #Геншин #Сны_Иных_Миров

4custom 53595304441759951062

Signed Ксяоме😵

18 Jun 2026, 16:38 UTC113 views4 reactionsread 10 August 2026
Photo

Хз че вам вкинуть, смотрите чему меня научили Я хотела попробовать порисовать в дидже спустя хуеву кукуеву времени, но у меня сел планшет пока #другое

custom 53595304441759951063custom 53461556196634913391

Signed Ксяоме😵

Showing the 12 most recent of 17 posts we hold for @Xiaomi_blenb. 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

Named by 4 registered channels — 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.

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

“Черкашня Ксяоми” (@Xiaomi_blenb), 45 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Xiaomi_blenb.

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.