4 measurements spanning 22 days, net -6. 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 170โ178 and does not start at zero.
Measurement log โ every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
2 Sept 2026, 06:44
171
-3
26 Aug 2026, 14:07
174
-2
12 Aug 2026, 03:32
176
-1
11 Aug 2026, 09:46
177
first reading
Engagement
10 posts held, back to 20 July 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 10 posts for this entry, the most recent from 25 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
1m 14s
Average length
1m 14s
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.
Reaction mix
11 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 36.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
โคโ๐ฅ
4
36.4%
๐ค
3
27.3%
๐
2
18.2%
โค
1
9.09%
๐
1
9.09%
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 6 of the 10 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 11 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 10 most recent posts we hold, published 20 July 2024 to 25 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.
Showing the 10 most recent of 10 posts we hold for @lsbxibwnpant. 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.
Forward network
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.
Mentions
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.
Appears in Telegramโs recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly โ each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone elseโs query is independent of having been queried itself.
ุญูููุฉ ุงููุงูุน.โ ๐ค ูููุงููู ุงูุดุชุงุก @U_4_qq ยท 23,267 Telegram ranks this channel #7 of 72 here โ alongside 71 others โ read 18 September 2026
ูุง ุจุฃุณ. @dndn096 ยท 211,119 Telegram ranks this channel #19 of 86 here โ alongside 85 others โ read 11 August 2026
ุซูููุบููุฑโฆย เช๐ฅ @ThAGer7 ยท 24,223 Telegram ranks this channel #24 of 76 here โ alongside 75 others โ read 16 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegramโs list for THAT channel, not this one โ see how this is measured.
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 2 September 2026 โ this
entry's latest reading, not the date you are reading this.
โ๐ผ๐ฃ๐ค๐ฃ๐ฎ๐ข๐ค๐ช๐จ ๐๐ฎ๐ง๐๐โ (@lsbxibwnpant), 171 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/lsbxibwnpant.
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.
