Telegram RegisterThe public register of Telegram
Telegram profile photo for .

Channel

.

@VIGOROUS_RANKING

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3subscribers

-240 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1003983131398
TypeChannel
Username@VIGOROUS_RANKING
CreatedBetween 1 April 2026 and 9 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live15 November 2026
Measurements held5
Confirmed unchanged2 times, most recently 15 November 2026
On Telegramt.me/VIGOROUS_RANKING

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 5 November 2026 and assigned it the closest of 31 fixed categories, at 64% 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.

Growth

340920612 August 2026 — 243 subscribers12 August 2026 — 243 subscribers19 August 2026 — 402 subscribers26 August 2026 — 409 subscribers5 November 2026 — 3 subscribers12 August 20265 November 2026
5 measurements spanning 86 days, net -240. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 17:413-406
26 Aug 2026, 10:08409+7
19 Aug 2026, 05:56402+159
12 Aug 2026, 05:47243no change
12 Aug 2026, 01:01243first reading

Engagement

20 posts held, back to 9 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 20 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

81 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 37.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3037.0%
❤2733.3%
💘1214.8%
💋1012.3%
👻11.23%
🦄11.23%

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 19 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 81 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 9 August 2026 to 11 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.

Recent posts

11 Aug 2026, 19:22 UTC52 views4 reactionsread 12 August 2026

بدین‌وسیله از منیجرهای محترمی که با مدیریت صحیح و حضور به‌موقع، تیم خود را منظم و مطابق برنامه در اسلات تعیین‌شده مستقر نمودند، صمیمانه قدردانی به‌عمل می‌آید ⏺همچنین در صورت وجود هرگونه گزارش تخلف، رفتار مشکوک یا نیاز به بررسی داوری، لطفاً حداکثر تا ساعت 12 امشب مستندات مربوطه را از طریق پیام مستقیم به آی‌دی زیر ارسال فرمایید: 🤩@MILADPSYCHOO 🔴🔴🔴🔴🔴🔴🔴🔴🔴 با تشکر — واحد نظارت و تیم اجرایی ✅@VIGOROUS_RANKING

❤2👍1💘1

11 Aug 2026, 19:22 UTC57 views4 reactionsread 12 August 2026
Photo

🔤🔤🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤 🩵🩵🩵🩵🩵 : Old school 🩵🩵🩵🩵🩵 GROUP 🩵🩵 ✅@MILADPSYCHOO ✅@VIGOROUS_RANKING

❤2👍1💘1

11 Aug 2026, 19:21 UTC56 views4 reactionsread 12 August 2026
Photo

🔤🔤🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤 🩵🩵🩵🩵🩵 : Old school 🩵🩵🩵🩵🩵 GROUP 🩵🩵 ✅@MILADPSYCHOO ✅@VIGOROUS_RANKING

❤2👍1💋1

11 Aug 2026, 12:31 UTC98 views4 reactionsread 12 August 2026

✅VIGOROUS REPORT ✅ PLAYER : Rich • Sunless🗡 باتوجه به ارسال کامل موارد خواسته شده در تایم تعین شده و برسی کامل توسط لیدران این پلیر قوانین رعایت کرده و هیچگونه مشکلی ندارد . ✅𝐂𝐡𝐚𝐧𝐧𝐞𝐥: @VIGOROUS_RANKING ✅𝐔𝐧𝐢𝐨𝐧: @KINGDOM_UNION

👍2💋1💘1

11 Aug 2026, 07:06 UTCviews —

𝙑𝙄𝙂𝙊𝙍𝙊𝙐𝙎 pinned «🤩درود به همراهان تورنمنت ویگروس 🤩 🔹اومدم براتون توضیحاتی درباره تورنمنت بهتون بگم که نحو برگذاری چطوره و قوانین به این صورت هستش که 4 گروه 24 تیمه هست و دوره مقدماتی ( از هر گروه 12 تا تیم صعود میکنه ) و به نیمه نهایی دست پیدا میکنه و به صورت 2 مچ اتو…»

10 Aug 2026, 20:21 UTC121 views4 reactionsread 12 August 2026

🤩VIGOROUS REPORT🤩 به دلیل عدم ارسال ریکورد و اوپن اپ به موارد خواسته شده پوینت پلیر صفر شده و در صورت تکرار بن از رنکینگ و اتحادیه همراه خواهد داشت .🌟 𝐂𝐡𝐚𝐧𝐧𝐞𝐥: @VIGOROUS_RANKING 𝐔𝐧𝐢𝐨𝐧: @KINGDOM_UNION

👍2❤1💘1

10 Aug 2026, 20:21 UTC121 views4 reactionsread 12 August 2026

🤩VIGOROUS REPORT🤩 به دلیل عدم ارسال ریکورد و اوپن اپ به موارد خواسته شده پوینت پلیر صفر شده و در صورت تکرار بن از رنکینگ و اتحادیه همراه خواهد داشت .🌟 𝐂𝐡𝐚𝐧𝐧𝐞𝐥: @VIGOROUS_RANKING 𝐔𝐧𝐢𝐨𝐧: @KINGDOM_UNION

👍2❤1💘1

10 Aug 2026, 19:36 UTC128 views4 reactionsread 12 August 2026

❌ 𝐑𝐄𝐏𝐎𝐑𝐓 ❌ PLAYER : P.A SOORI Team:ZYRAXIS ⏳𝗧𝗜𝗠𝗘: 13:00 PM 2 MATCH ⏺ طبق قانون رنکینگ و اتحادیه پلیر موظف به ارسال ( اوپن اپ /فول ریکورد ) میباشد . According to the law of ranking and player union, he is obliged to send (open app/highlight kill) OWNER @MILADPSUCHOO 𝐂𝐡𝐚𝐧𝐧𝐞𝐥: @VIGOROUS_RANKING 𝐔𝐧𝐢𝐨𝐧: @KINGDOM_UNION

❤2👍1💘1

10 Aug 2026, 19:33 UTC126 views4 reactionsread 12 August 2026

❌ 𝐑𝐄𝐏𝐎𝐑𝐓 ❌ PLAYER : LázaroMRX Team:ZYRAXIS ⏳𝗧𝗜𝗠𝗘: 13:00 PM 1 MATCH ⏺ طبق قانون رنکینگ و اتحادیه پلیر موظف به ارسال ( اوپن اپ /فول ریکورد ) میباشد . According to the law of ranking and player union, he is obliged to send (open app/highlight kill) OWNER @MILADPSUCHOO 𝐂𝐡𝐚𝐧𝐧𝐞𝐥: @VIGOROUS_RANKING 𝐔𝐧𝐢𝐨𝐧: @KINGDOM_UNION

👍2❤1💋1

10 Aug 2026, 19:33 UTC112 views4 reactionsread 12 August 2026

بدین‌وسیله از منیجرهای محترمی که با مدیریت صحیح و حضور به‌موقع، تیم خود را منظم و مطابق برنامه در اسلات تعیین‌شده مستقر نمودند، صمیمانه قدردانی به‌عمل می‌آید ⏺همچنین در صورت وجود هرگونه گزارش تخلف، رفتار مشکوک یا نیاز به بررسی داوری، لطفاً حداکثر تا ساعت 2 امشب مستندات مربوطه را از طریق پیام مستقیم به آی‌دی زیر ارسال فرمایید: 🤩@MILADPSYCHOO 🔴🔴🔴🔴🔴🔴🔴🔴🔴 با تشکر — واحد نظارت و تیم اجرایی ✅@VIGOROUS_RANKING

❤2💋1💘1

10 Aug 2026, 19:31 UTC119 views6 reactionsread 12 August 2026
Photo

🔤🔤🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤 🩵🩵🩵🩵🩵 : Doje | Nova 🩵🩵🩵🩵🩵 GROUP 🩵🩵 ✅@MILADPSYCHOO ✅@VIGOROUS_RANKING

👍3💋2💘1

10 Aug 2026, 19:31 UTC126 views6 reactionsread 12 August 2026
Photo

🔤🔤🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤 🩵🩵🩵🩵🩵 : Syndicates Youngsters 🩵🩵🩵🩵🩵 GROUP 🩵🩵 ✅@MILADPSYCHOO ✅@VIGOROUS_RANKING

❤3💋2👍1

Showing the 12 most recent of 20 posts we hold for @VIGOROUS_RANKING. 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

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.

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.

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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“.” (@VIGOROUS_RANKING), 3 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/VIGOROUS_RANKING.

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.