Channel
@ManagersCafe
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
222subscribers
+13 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001305191836 |
|---|---|
| Type | Channel |
| Username | @ManagersCafe |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/ManagersCafe |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 |
|---|---|---|
| 25 Sept 2026, 16:37 | 222 | +2 |
| 27 Aug 2026, 22:59 | 220 | +4 |
| 21 Aug 2026, 02:08 | 216 | +2 |
| 14 Aug 2026, 20:15 | 214 | +3 |
| 7 Aug 2026, 21:08 | 211 | +2 |
| 7 Aug 2026, 03:46 | 209 | no change |
| 6 Aug 2026, 21:16 | 209 | first reading |
20 posts held, back to 25 July 2025 — 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
هکشدن تلگرام آگاهیبخشی امنیت اینترنت اگر اکانت تلگرام ما هک شد چه کنیم؟ راهنمای عملی، گامبهگام و کامل بیرون انداختن هکر و امنسازی حساب. اکانت تلگرام شما ممکن است به دلایل مختلفی هک شود یا بهدست دیگران بیفتد. مثلا حواستان نباشد و یک اپلیکیشن آلوده روی گوشیتان نصب کرده باشید یا خیلی ساده، تلفنتان را برای چند دقیقه بهدست یک دوست یا تعمیرکار موبایل داده باشید و او از فرصت استفاده کرده و بهسرعت با یک گوشی د…
هیچ وقت از بزرگ فکر کردن نترسید سعی کنید آنقدر کارهایتان بزرگ باشد که دیگران آن ها را باور نکنند چه برسد که بخواهند حسادت کنند...
دریافت راه حل های الهی ⚡️ امروز، در آغاز روز، ذهن و قلبت را به سوی هدایت الهی باز کن. در هر چالشی، در هر بنبستی، راهحلهایی وجود دارند که از جنس خرد بیکران هستی هستند. امروز، فرصتی است تا با آرامش، گوش بسپاری و آن پیامهای هدایتگر را دریافت کنی. باور داشته باش که هر مشکلی، با نوری از بالا، روشن و راهگشا میشود. 🌟 با عشق و اطمینان بگو: 🔑 من آمادهی دریافت راهحلهای الهی هستم. خرد بیکران هستی در من جاریست و من ب…
استراتژی درست امروزه؛ انجام ندادن کار اشتباه است #مایکل_پورتر
Video, posted without a caption
مدیریت خلاقانه زمان
صبحتون با نور خدا روشن و نور خدا بر قلبتون جاری صبحی سرشار از انرژی مثبت اتفاقهای بی نظیر و جدید و پراز خیر و برکت تن درستی و شادی براتون آرزومندم سلام صبح شنبه تون بخیرو نیکی 🌞❤️🌞
Video, posted without a caption
خدا نزدیکه تو حواست باشه دور نشی ازش الهی به امید تو🤲 سلام صبح طلایی تون بخیر ❤️
Video, posted without a caption
خبر خوب برای دوندگان: دویدن دوست مفاصل زانوست! 🏃♂️🦵 شاید فکر کنی دویدن طولانی، زانوها رو داغون میکنه؛ اما تحقیقات جدید چیز دیگهای میگن! باور عموم اینه که ورزشهایی مثل دویدن باعث ساییدگی مفاصل و درد زانو میشن، ولی علم نظر متفاوتی داره. 🔸 دویدن و آرتروز؟ برخلاف تصور، پژوهشها نشون میده که دوندگان معمولاً نسبت به افراد غیر فعال، کمتر دچار آرتروز زانو میشن! چون دویدن با شدت مناسب، به بافتهای مفصل کمک میکنه باز…
💫خواستن توانستن است تو می تونی هیچ وقت اجازه نده …
Showing the 12 most recent of 20 posts we hold for @ManagersCafe. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“کانال انگیزشی مدیران” (@ManagersCafe), 222 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/ManagersCafe.
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.