Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗕𝗘𝗘𝗠

Channel

𝗕𝗘𝗘𝗠

@KashmShab

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

23subscribers

-4 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003498425768
TypeChannel
Username@KashmShab
Created14 November 2025measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/KashmShab

Growth

23272512 August 2026 — 27 subscribers12 August 2026 — 27 subscribers20 August 2026 — 26 subscribers26 August 2026 — 25 subscribers10 September 2026 — 24 subscribers17 September 2026 — 23 subscribers12 August 202617 September 2026
6 measurements spanning 36 days, net -4. 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 22–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 12:3923-1
10 Sept 2026, 00:3724-1
26 Aug 2026, 07:3525-1
20 Aug 2026, 08:0226-1
12 Aug 2026, 22:0127no change
12 Aug 2026, 21:4927first reading

Engagement

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

Reaction mix

5,357 reactions across 2 posts, in 10 distinct kinds. The most used accounts for 15.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 509843056897923747582015.3%
custom 536866072001355688474814.0%
custom 53664759302796245395189.67%
custom 53687670591088371045149.59%
custom 58415295411970459715089.48%
custom 58412695109920438135039.39%
custom 53688004181198264734859.05%
custom 53665954463345700794498.38%
custom 53664002400709656414287.99%
custom 53663440833735699633847.17%

Custom emoji. Every 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 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 2 of the 4 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 5,357 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 4 most recent posts we hold, published 14 November 2025 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.

Recent posts

5 Jun 2026, 12:07 UTC≈1,850 views1,259 reactionsread 12 August 2026

𝑳𝒐𝒔𝒕 𝒊𝒏 𝒔𝒊𝒍𝒆𝒏𝒄𝒆 𝒇𝒐𝒖𝒏𝒅 𝒊𝒏 𝒑𝒆𝒂𝒄𝒆🙍🏻‍♂

custom 5366595446334570079145custom 5098430568979237475142custom 5366475930279624539133custom 5368767059108837104132custom 5366400240070965641123custom 5841269510992043813123custom 5366344083373569963121custom 5368660720013556884121

4 Jun 2026, 16:35 UTC≈3,700 views4,098 reactionsread 12 August 2026
Photo

𝒏𝒆𝒘 𝒄𝒉𝒂𝒏𝒏𝒆𝒍👇🏻 t.me/iPI001

custom 5098430568979237475678custom 5368660720013556884627custom 5841529541197045971389custom 5366475930279624539385custom 5368800418119826473385custom 5368767059108837104382custom 5841269510992043813380custom 5366400240070965641305

Showing the 4 most recent of 4 posts we hold for @KashmShab. 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 2 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“𝗕𝗘𝗘𝗠” (@KashmShab), 23 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/KashmShab.

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.