Telegram RegisterThe public register of Telegram
Telegram profile photo for قفل بدردم خورد

Channel

قفل بدردم خورد

@BedardamKhord

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

497subscribers

+91 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002836197679
TypeChannel
Username@BedardamKhord
Created10 September 2025measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/BedardamKhord

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 25 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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

406113,69657,0517 August 2026 — 406 subscribers7 August 2026 — 414 subscribers8 August 2026 — 414 subscribers15 August 2026 — 97,974 subscribers17 August 2026 — 443 subscribers24 August 2026 — 105,677 subscribers25 August 2026 — 105,128 subscribers26 August 2026 — 104,811 subscribers27 August 2026 — 104,421 subscribers28 August 2026 — 459 subscribers4 September 2026 — 109,094 subscribers7 September 2026 — 451 subscribers14 September 2026 — 113,696 subscribers16 September 2026 — 113,044 subscribers18 September 2026 — 497 subscribers4977 August 202618 September 2026
15 measurements spanning 42 days, net +91. 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
Measured (UTC)SubscribersChange
18 Sept 2026, 17:55497-112,547
16 Sept 2026, 07:55113,044-652
14 Sept 2026, 16:41113,696+113,245
7 Sept 2026, 10:40451-108,643
4 Sept 2026, 17:59109,094+108,635
28 Aug 2026, 01:04459-103,962
27 Aug 2026, 01:24104,421-390
26 Aug 2026, 03:53104,811-317
25 Aug 2026, 04:07105,128-549
24 Aug 2026, 01:45105,677+105,234
17 Aug 2026, 09:53443-97,531
15 Aug 2026, 17:2797,974+97,560
8 Aug 2026, 05:34414no change
7 Aug 2026, 22:32414+8
7 Aug 2026, 17:31406first reading

Engagement

2 posts held, back to 10 September 2025the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
58.4%
avg views ÷ 497 subscribers
Avg views / post
290
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 2 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 September 2026
Posts held2 (10 September 20255 September 2026)
Views total290
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Sept 2026, 03:42 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

5 Sept 2026, 12:54 UTC290 viewsread 7 September 2026

برای ورود به چنل 👇🏻 https://t.me/+me42-uYF6yZkODQ0 https://t.me/+me42-uYF6yZkODQ0

Showing the 2 most recent of 2 posts we hold for @BedardamKhord. 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 26 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“قفل بدردم خورد” (@BedardamKhord), 497 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/BedardamKhord.

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.