7 Aug 2026, 20:31 UTC49 viewsread 8 August 2026
منم میدونم میگذره، دوست داشتم خوش بگذره.
Channel
-بَرگَرد بِخَندَم🌞
@bargard_bekhandammm
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
444subscribers
+10 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 | -1002374908533 |
|---|---|
| Type | Channel |
| Username | @bargard_bekhandammm |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/bargard_bekhandammm |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 17:00 | 444 | -2 |
| 6 Sept 2026, 17:19 | 446 | -6 |
| 29 Aug 2026, 13:13 | 452 | +2 |
| 22 Aug 2026, 08:53 | 450 | -5 |
| 15 Aug 2026, 20:06 | 455 | +14 |
| 8 Aug 2026, 05:05 | 441 | no change |
| 7 Aug 2026, 17:04 | 441 | +7 |
| 7 Aug 2026, 15:30 | 434 | first reading |
Engagement
18 posts held, back to 1 August 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 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 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
7 Aug 2026, 07:41 UTC182 viewsread 8 August 2026
روح من زیبا بود. تو در آن رنج کاشتی
7 Aug 2026, 06:40 UTC184 viewsread 8 August 2026
وقتی بفهمی آدما فقط بر اساس سطح درک خودشون همه چیزو میبینن از توضیح دادن دست میکشی.
6 Aug 2026, 20:30 UTC209 viewsread 8 August 2026
دنیا میچرخه، میچرخه و بعد دقیقا میذارتت تو اون موقعیتی که دربارهش راحت صحبت میکردی و بقیه رو قضاوت میکردی.
6 Aug 2026, 19:53 UTC205 viewsread 8 August 2026
Video message
Video message, posted without a caption
6 Aug 2026, 08:42 UTC194 viewsread 8 August 2026
زمان میبره بفهمی شاید هیچ ایرادی نداشتی، فقط کنار آدم درستی نبودی.
5 Aug 2026, 20:30 UTC920 viewsread 8 August 2026
ماهها و سالها در انتظار آدمِ درست بمونید، اما حتی یک دقیقه هم منتظر درست شدنِ آدمها نمونید.
5 Aug 2026, 19:53 UTC187 viewsread 8 August 2026
Photo
•
4 Aug 2026, 21:31 UTC181 viewsread 8 August 2026
خودت خودت را در آغوش بگیر کسی برای تو نخواهد جنگید.
4 Aug 2026, 09:43 UTC178 viewsread 8 August 2026
عیبی نداره عزیزم maybe in next universe
3 Aug 2026, 20:30 UTC185 viewsread 8 August 2026
تو دوره ای که کسی چشم دیدن خوشبختی کسی رو نداره؛ امیدوارم اول خدا به شما بده، بعد به ما.
3 Aug 2026, 13:47 UTC196 viewsread 8 August 2026
‘مدتیه که که چایی خوردن هم چیزی رو بهتر نمیکنه.’
Showing the 12 most recent of 18 posts we hold for @bargard_bekhandammm. 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.
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 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“-بَرگَرد بِخَندَم🌞” (@bargard_bekhandammm), 444 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/bargard_bekhandammm.
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.