چون دلت با من نباشد همنشینی سود نیست

Channel
هَِمَِــَِیَِنَِ؛
@hamin56i
On this record: Topic · Previous handles · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
2,278subscribers
+129 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001895128351 |
|---|---|
| Type | Channel |
| Username | @hamin56i |
| Created | Between 1 November 2022 and 31 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/hamin56i |
Topic
Literature — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 the other topics.
Previous handles
@hamin56i was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 7 August 2026 – 7 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 06:00 | 2,278 | -4 |
| 3 Nov 2026, 11:10 | 2,282 | +3 |
| 31 Oct 2026, 08:06 | 2,279 | +7 |
| 27 Oct 2026, 22:06 | 2,272 | +4 |
| 25 Oct 2026, 04:48 | 2,268 | +3 |
| 21 Oct 2026, 23:40 | 2,265 | -1 |
| 15 Oct 2026, 23:15 | 2,266 | +3 |
| 12 Oct 2026, 19:38 | 2,263 | -1 |
| 6 Oct 2026, 02:20 | 2,264 | +6 |
| 29 Sept 2026, 02:41 | 2,258 | +32 |
| 16 Sept 2026, 06:39 | 2,226 | +2 |
| 15 Sept 2026, 08:22 | 2,224 | no change |
| 15 Sept 2026, 07:47 | 2,224 | +18 |
| 11 Sept 2026, 14:41 | 2,206 | +2 |
| 6 Sept 2026, 23:18 | 2,204 | -5 |
| 2 Sept 2026, 15:34 | 2,209 | +5 |
| 30 Aug 2026, 04:46 | 2,204 | -8 |
| 27 Aug 2026, 14:57 | 2,212 | -3 |
| 24 Aug 2026, 16:58 | 2,215 | -10 |
| 21 Aug 2026, 00:14 | 2,225 | first reading |
Engagement
40 posts held, back to 3 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 2 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 40 posts for this entry, the most recent from 14 September 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
ما ادبیات دوست داشتیم، ما عاشق میشدیم، ما قدری احساس برای ادامهیِ زندگی داشتیم اما اکنون بر همه حسهایمان قدری خستگی، مقداری ملال و یک مشت سردرگمی پاشیدهاند..
همه چیز در آخرین آدمی خلاصه میشود که در تنگنای شب به یاد میآورید قلب شما آنجاست.
روی چون ماهِ تو را محتاجِ آرایش نبود
«از چشم افتاده را میلِ دیدار دوباره نیست!»
"خاطراتی که آدمهایش رفته اند،درناکاند ولی خاطراتی که آدمهایش حضور دارند اما شبیه گذشته نیستند، به مرتب دردناک ترند..."
مهم نیست بعدش بیای بگی ببخشید، مهم اینه که میدونستی ناراحت میشم و انجامش دادی.
آمده بود از دل ما رَد بشود دل ما انگار محل گذرست.
خطاب به تمام خستگان جهان: باشد که اشک بعدی شما اشک شوق باشد.
File, posted without a caption
هرچیزی که مورد توجه قرار نگیرد، میمیرد. احساسات، روابط، حتی گلها.
File, posted without a caption
Showing the 12 most recent of 40 posts we hold for @hamin56i. 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@seepyyy · 25,559
Telegram ranks this channel #16 of 41 here — alongside 40 others — read 15 September 2026
@acccrd · 27
Telegram ranks this channel #58 of 70 here — alongside 69 others — read 11 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“هَِمَِــَِیَِنَِ؛” (@hamin56i), 2,278 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/hamin56i.
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.