Channel
@vakilhamrah2
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
728subscribers
-12 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002001897979 |
|---|---|
| Type | Channel |
| Username | @vakilhamrah2 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/vakilhamrah2 |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 08:41 | 728 | -3 |
| 3 Sept 2026, 09:37 | 731 | -9 |
| 27 Aug 2026, 21:53 | 740 | -4 |
| 21 Aug 2026, 18:46 | 744 | -1 |
| 15 Aug 2026, 03:16 | 745 | +7 |
| 7 Aug 2026, 09:38 | 738 | -2 |
| 6 Aug 2026, 18:49 | 740 | first reading |
20 posts held, back to 20 July 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
207 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 46.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 96 | 46.4% | |
| 👌 | 66 | 31.9% | |
| 💔 | 26 | 12.6% | |
| 😢 | 7 | 3.38% | |
| 🤷♂ | 5 | 2.42% | |
| 🤔 | 4 | 1.93% | |
| 🤓 | 3 | 1.45% |
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 20 of the 20 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 207 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 20 July 2026 to 5 August 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.
دوم اینکه: اگر اطلاعات ثبتشده در سامانه صیاد (مثل مبلغ، تاریخ یا ذینفع) با اطلاعات روی برگه چک مغایرت داشته باشه، ملاک، اطلاعات ثبتشده در سامانهست. پس قبل از تأیید و دریافت چک، حتماً اطلاعات سامانه رو با متن چک تطبیق بدید؛ چون همین مغایرت میتونه بعدها برای وصول چک دردسرساز بشه.
❤8
اول اینکه: چک صیادی را بدون ثبت تحویل نگیرید! حتماً قبل از قبول چک، از ثبت چک در سامانه صیاد مطمئن بشید و بهتره در قرارداد یا صورتجلسه جداگانه هم قید کنید: «در صورت عدم ثبت چک در سامانه صیاد توسط صادرکننده، ایشان موظف است علاوه بر اصل مبلغ چک، مبلغ ……ریال روزانه به عنوان وجه التزام را پرداخت نماید.»
❤10
امروزمونو با چندتا نکتهی کاربردی درخصوص چک شروع کنیم:
❤7
Photo, posted without a caption
❤4
اگر از خرید اینترنتیتون پشیمون شدید، قانون ازتون حمایت میکنه. طبق قانون تجارت الکترونیکی، اگر اینترنتی خرید کرده باشید، تا ۷ روز حق دارید از خریدتون انصراف بدید و کالا رو بدون پرداخت جریمه یا خسارت به فروشنده برگردونید. فقط هزینه ارسال کالا برای مرجوع کردنش، به عهده شماست. نکته: این حق انصراف برای خرید از سایتهای دارای اینماد قابل استناده و شامل خرید از پیجهای اینستاگرامی نمیشه.
❤8👌3🤷♂2🤔1
Photo, posted without a caption
❤4🤓3
اگر سیمکارتی به نام شماست، در صورت مفقودی یا سرقت حتماً و فوراً مسدودش کنید. تا زمانی که سیمکارت به نام شماست، هر استفاده مجرمانه باعث میشه، شما هم در روند رسیدگی قضایی مورد بررسی و پاسخگویی قرار بگیرید.
❤16👌3
Photo, posted without a caption
❤7
دوست دارید بیشتر در خصوص کدوم مسائل حقوقی صحبت کنیم؟اینجا برام بنویسید.
❤11
به جاش بنویسید: «طرفین توافق کردند در صورت عدم انجام تعهد، متخلف مبلغ ………. ریال بهعنوان وجه التزام به طرف مقابل پرداخت کند.»
👌14
دوم اینکه: ننویسید: «در صورت عدم انجام تعهد، متعهد مسئول جبران خسارت خواهد بود.» این عبارت کلی، شما رو درگیر اثبات میزان خسارت میکنه.
👌12
اول اینکه: داخل قراردادهاتون به هیچ عنوان شرط داوری ننویسید، جز دردسر و طولانی شدن فرآیند رسیدگی، سودی نداره! مرجع حل اختلاف: دادگستری قرار بدید، اگرهیچی هم در خصوص مرجع حل اختلاف ننویسید، به دادگستری ارجاع میشه.
👌9
Showing the 12 most recent of 20 posts we hold for @vakilhamrah2. 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.
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.
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“وکیل همراه” (@vakilhamrah2), 728 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/vakilhamrah2.
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.