Telegram RegisterThe public register of Telegram
Telegram profile photo for BΛƝÐRISH STØRE

Channel

BΛƝÐRISH STØRE

@bandrish

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Cite this entry

2,475subscribers

-8,801 since we began measuring on 25 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003632086222
TypeChannel
Username@bandrish
Created20 January 2026 — measured — dated from the channel’s first post
First recorded25 August 2026
Last confirmed live26 October 2026
Measurements held25
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/bandrish

Topic

Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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.

Growth

2,47556,69229,583.525 August 2026 — 11,276 subscribers25 August 2026 — 11,276 subscribers26 August 2026 — 56,692 subscribers27 August 2026 — 55,538 subscribers28 August 2026 — 53,648 subscribers29 August 2026 — 44,719 subscribers30 August 2026 — 42,968 subscribers31 August 2026 — 41,677 subscribers1 September 2026 — 40,828 subscribers2 September 2026 — 40,484 subscribers4 September 2026 — 40,438 subscribers6 September 2026 — 37,770 subscribers9 September 2026 — 31,021 subscribers12 September 2026 — 29,321 subscribers13 September 2026 — 21,082 subscribers15 September 2026 — 21,057 subscribers17 September 2026 — 19,728 subscribers25 September 2026 — 12,373 subscribers4 October 2026 — 5,479 subscribers10 October 2026 — 3,808 subscribers14 October 2026 — 3,581 subscribers16 October 2026 — 2,537 subscribers20 October 2026 — 2,523 subscribers23 October 2026 — 2,489 subscribers26 October 2026 — 2,475 subscribers25 August 202626 October 2026
25 measurements spanning 62 days, net -8,801. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
26 Oct 2026, 06:592,475-14
23 Oct 2026, 12:272,489-34
20 Oct 2026, 05:282,523-14
16 Oct 2026, 23:272,537-1,044
14 Oct 2026, 07:083,581-227
10 Oct 2026, 02:183,808-1,671
4 Oct 2026, 06:385,479-6,894
25 Sept 2026, 15:1712,373-7,355
17 Sept 2026, 08:3819,728-1,329
15 Sept 2026, 09:3921,057-25
13 Sept 2026, 20:1921,082-8,239
12 Sept 2026, 05:4029,321-1,700
9 Sept 2026, 21:1631,021-6,749
6 Sept 2026, 10:3637,770-2,668
4 Sept 2026, 02:1540,438-46
2 Sept 2026, 15:0340,484-344
1 Sept 2026, 15:5840,828-849
31 Aug 2026, 14:5841,677-1,291
30 Aug 2026, 16:4442,968-1,751
29 Aug 2026, 13:0844,719first reading

Engagement

114 posts held, back to 20 January 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 33 pages 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 114 posts for this entry, the most recent from 9 September 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12s
Average length
6s

Measured directly from 2 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

52 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 57.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3057.7%
🔥1019.2%
😭59.62%
❤‍🔥47.69%
💋35.77%

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 18 of the 114 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 52 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 114 most recent posts we hold, published 20 January 2026 to 9 September 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.

Advertising

Ad load
4.39%
5 of 114 posts carry an ad marker
Regulatory tokens
5
posts carrying an erid · 5 distinct tokens
Median views · ads
37.0
over 5 measured posts
Median views · rest
36.0
over 107 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
20260825101214537515010300166335593985312125 August 202625 August 2026
20260827101214529515010300166335594324906127 August 202627 August 2026
20260829101214974515010300166335594636486129 August 202629 August 2026
20260830101214575515010300166335594885072130 August 202630 August 2026
2026090210121487871501030016653869560946312 September 20262 September 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 114 most recent posts we hold, published 20 January 2026 to 9 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

9 Sept 2026, 05:17 UTC8 views1 reactionsread 9 September 2026

GAISS AKU LG RIDI NOKTEL KALIAN PDA MAUU GAA RIDI WARNA BIRU SAMA PINKK. RIDI 1/WARNAA. REACT DONGG KALO MAWUUU😘

🔥1

Signed vièlea 𝘣𝘶𝘧𝘧𝘺'𝘴♡

8 Sept 2026, 06:24 UTC13 viewsread 9 September 2026

GAIS KITA OPEN YUKK JAJAN LANGSUNG KE BOT YAA @Bandrish_Bot

Signed vièlea 𝘣𝘶𝘧𝘧𝘺'𝘴♡

7 Sept 2026, 09:37 UTC11 viewsread 7 September 2026
Sticker

Sticker, posted without a caption

Signed charlie [ فاسبر

7 Sept 2026, 09:37 UTC11 viewsread 7 September 2026

yu r star 4 slot aja soalnya gua lagi miskin, belum gajian

Signed charlie [ فاسبر

7 Sept 2026, 09:26 UTC11 viewsread 7 September 2026

mau hadiah daget, or react star?

Signed charlie [ فاسبر

7 Sept 2026, 08:48 UTC17 viewsread 7 September 2026
Sticker

Sticker, posted without a caption

Signed charlie [ فاسبر

7 Sept 2026, 08:48 UTC17 views1 reactionsread 7 September 2026
Photo

happy 100 rnk Yeay !

🔥1

Signed charlie [ فاسبر

6 Sept 2026, 12:52 UTC26 viewsread 9 September 2026

gaiss jajan yukk

Signed vièlea 𝘣𝘶𝘧𝘧𝘺'𝘴♡

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

Posts edited after publishing

@bandrish edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
25 August 2026
Most recent edit
25 August 2026

Mentions

Named by 5 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.

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

“BΛƝÐRISH STØRE” (@bandrish), 2,475 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/bandrish.

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.