7 measurements spanning 17 days, net -51. 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 4,604โ4,674 and does not start at zero.
Measurement log โ every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
24 Aug 2026, 09:18
4,612
-14
20 Aug 2026, 19:27
4,626
-19
17 Aug 2026, 12:55
4,645
-11
14 Aug 2026, 13:53
4,656
-8
11 Aug 2026, 08:53
4,664
-2
8 Aug 2026, 05:07
4,666
+3
7 Aug 2026, 18:02
4,663
first reading
Engagement
7 posts held, back to 2 October 2025 โ the reader has reached the start of this channelโs public history, so this is the full archive Telegram still exposes. Read across 6 pagesof 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 7 posts for this entry, the most recent from 14 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
7m 04s
Average length
2m 21s
Measured directly from 3 videos 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
1,331 reactions across 6 posts, in 18 distinct kinds. The most used accounts for 45.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
โค
605
45.5%
๐
171
12.8%
๐คฌ
167
12.5%
๐คก
141
10.6%
๐ฉ
42
3.16%
๐
39
2.93%
๐
30
2.25%
๐
28
2.10%
๐คฃ
24
1.80%
๐ฅ
20
1.50%
๐
18
1.35%
๐
16
1.20%
๐ฅฐ
8
0.601%
๐
6
0.451%
๐ฑ
5
0.376%
โก
4
0.301%
๐
4
0.301%
๐คฉ
3
0.225%
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 7 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,331reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 7 most recent posts we hold, published 2 October 2025 to 14 May 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 7 most recent of 7 posts we hold for @BSSTOREHACK. 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.
Citation-graph rank
Citation-graph rank โ 347,593 of 1,604,161entries in the measured graph. A weighted position computed from the forward and mention edges below โ republished posts weigh more than named mentions โ and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channelโs name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page โ a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
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.
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 24 August 2026 โ this
entry's latest reading, not the date you are reading this.
โBS STORE X PYTHON ๐โ (@BSSTOREHACK), 4,612 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/BSSTOREHACK.
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.
