Telegram RegisterThe public register of Telegram

Channel

دیدنی...

@bejnord

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

158subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001080796078
TypeChannel
Username@bejnord
CreatedBetween 1 September 2016 and 30 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/bejnord

Growth

1586 August 2026 — 158 subscribers8 August 2026 — 158 subscribers6 August 20268 August 2026
2 measurements spanning 3 days. 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 157–159 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 18:00158no change
6 Aug 2026, 01:09158first reading

Engagement

20 posts held, back to 28 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.2%
avg views ÷ 158 subscribers
Avg views / post
19.3
9 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
9
of 20 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 7 August 2026
Posts held20 (28 June 20267 August 2026)
Views total174
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18:00 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.

What this channel posts

Photos
4,960
Videos
9,980
Links
3,550

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
29m 44s
Average length
1m 34s

Measured directly from 19 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.

Recent posts

7 Aug 2026, 22:41 UTC9 viewsread 8 August 2026
Forwarded from @kianmeli1Video

🔴صداوسیما: گرانی بیداد میکند رفتم میوه بخرم نتونستم https://t.me/kianmeli1

25 Jul 2026, 17:45 UTC29 viewsread 8 August 2026
Forwarded from @bojnourdonlineeVideo

📛پایان کار کایروپراکتور جنجالی اینستاگرام؛ «ص.ی» بازداشت شد این فرد که با انتشار ویدیوهای میلیونی تحت عنوان «آچارکشی» در اینستاگرام به شهرت رسیده بود، به دستور مقام قضایی به اتهام مداخله غیرمجاز در امور درمانی بازداشت و کلینیک وی به‌طور کامل پلمب گردید. Talkhand #بجنورد_آنلاین @bojnourdonlinee

25 Jul 2026, 16:58 UTC24 viewsread 8 August 2026
Forwarded from @channelnagoftehaVideo

این همه بیداد و این همه تباهی همه به گردن جمهوری اسلامی است البته جمهوری اسلامی یک شریک جرم هم دارد : قشر خاکستری !

25 Jul 2026, 12:42 UTC15 viewsread 8 August 2026
Forwarded from @kianmeli1Video

🔴شهریاری، عضو کمیسیون امنیت ملی مجلس وسط پخش زنده خطاب به ثابتی : بدید برررره، تنگه مال ننت بوده که بدید بره؟ مال عمه‌تونه؟ مال کیه؟ ارث باباته؟ https://t.me/kianmeli1

25 Jul 2026, 12:42 UTC19 viewsread 8 August 2026
Forwarded from @kianmeli1Video

🔴شهروند کویتی: بخاطر حمله این مجوس ها (ایرانی ها) از وحشت اسهال گرفتم! دیشب ۱۷ بار وضویم باطل شد هر موشکی که میزد یک بار به سمت دستشویی می دویدم. (چرا به ایرانی ها مجوس میگویند ریشه تاریخی داره که از روی تحقیر است…). https://t.me/kianmeli1

25 Jul 2026, 12:37 UTC16 viewsread 8 August 2026
Forwarded from @kianmeli1Video

🔴اکبر عبدی بازیگر سینما درگذشت https://t.me/kianmeli1

25 Jul 2026, 00:07 UTC22 viewsread 8 August 2026
Forwarded from @radicalliVideo

چه دانستم که این سودا،مرا اینسان کند مجنون دلم را دوزخی سازد، دو چشمم را کند جیحون چه دانستم؟ که سیلابی ناگاه ، مرا به رباید چو کشتی ام در اندازد، میان قلزم پرخون @khandanikarimane

24 Jul 2026, 23:36 UTC21 viewsread 8 August 2026
Video

لانه را مادر سازد عشق را مادر بازد آه مادر مادر مادر خانه را مادر باید @radicalli یاد مادر

7 Jul 2026, 11:43 UTC55 viewsread 8 August 2026
Video

با مزه ترین ویزیت در عالم پزشکی! @radicalli

7 Jul 2026, 11:28 UTC26 viewsread 8 August 2026
Forwarded from @bavarhVideo

🌹🌷هزینه سنگین دروغگویی در کشور سوئد!!!! http://telegram.me/bavarh مسؤلان نظام ولایت خطیب ارزش کشور خودتون را بدانید!!! http://telegram.me/bavarh

6 Jul 2026, 11:00 UTC23 viewsread 8 August 2026
Forwarded from @bavarhVideo

🌹🌷چمدان های تیم ملی ژاپن و تیم ملی ایران بعد از بازگشت از آمریکا به این میگن دستاورد :) http://telegram.me/bavarh

Showing the 12 most recent of 20 posts we hold for @bejnord. 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 — 955,352 of 1,151,006entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 3 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“دیدنی...” (@bejnord), 158 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/bejnord.

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.