Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗧𝗥𝗢𝗬 𝗚𝗔𝗧𝗘|تِروی گِیت

Channel

𝗧𝗥𝗢𝗬 𝗚𝗔𝗧𝗘|تِروی گِیت

@TROYGATE

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

4,241subscribers

-1,029 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003575787716
TypeChannel
Username@TROYGATE
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/TROYGATE

Growth

4,2415,2704,755.57 August 2026 — 5,270 subscribers7 August 2026 — 5,270 subscribers7 August 2026 — 5,216 subscribers11 August 2026 — 5,018 subscribers14 August 2026 — 4,859 subscribers17 August 2026 — 4,650 subscribers20 August 2026 — 4,530 subscribers23 August 2026 — 4,493 subscribers26 August 2026 — 4,441 subscribers29 August 2026 — 4,343 subscribers1 September 2026 — 4,300 subscribers5 September 2026 — 4,241 subscribers7 August 20265 September 2026
12 measurements spanning 29 days, net -1,029. 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”. The vertical axis spans 4,087–5,424 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 13:014,241-59
1 Sept 2026, 16:134,300-43
29 Aug 2026, 12:374,343-98
26 Aug 2026, 14:544,441-52
23 Aug 2026, 07:154,493-37
20 Aug 2026, 03:174,530-120
17 Aug 2026, 11:174,650-209
14 Aug 2026, 03:184,859-159
11 Aug 2026, 04:215,018-198
7 Aug 2026, 23:555,216-54
7 Aug 2026, 13:035,270no change
7 Aug 2026, 12:495,270first reading

Engagement

30 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.18%
avg views ÷ 4,241 subscribers
Avg views / post
50.0
1 post measured
Reaction rate
12.0%
reactions ÷ views · ER floor
Posts in window
1
of 30 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held30 (31 July 202611 August 2026)
Views total50
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:56 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

108 reactions across 23 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥108100.0%

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 23 of the 30 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 108 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 30 most recent posts we hold, published 31 July 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, 21:59 UTC50 views6 reactionsread 12 August 2026

به اندازه موهای سر،درحال حاظر شاپ وی‌پی‌ان داریم که 70درصد بدون شک اسکم و دزدی بقیه هم قیمتای بالا با پشتیبانی افتضاح اندکی از این تعداد واقعا مقید به کار و مشتری هستن یکیشون ما هستیم ولی بدلیل قیمت پایین خیلیا شک میکنن که نکنه دزدی باشه این تعرفه یا حرفهایی ازاین دسته! درصورتی که اگر میخواستم رضایت مشتری قرار بدم روزانه حداقل 50نفر دارن به من رضایت مشتری میدن،چه در پشتیبانی چه در ربات من اخلاق شخصیتم باعث شده این

❤‍🔥6

10 Aug 2026, 16:16 UTC86 viewsread 12 August 2026
Photo

پنل جدید و خفن به ربات اضافه شد💚 نکته مهم:دوستانی که قبل از اضافه شدن پنل سرویس خریداری کردید ولی چیزی براتون ارسال نشده به آیدی پشتیبانی پیام بدید تا کیف پولتون رو شارژ کنه و مجدد خرید بزنید @TROYVIPBOT تهیه سرویس پرسرعت🩵

10 Aug 2026, 15:00 UTC85 views2 reactionsread 12 August 2026
File

مطلب مهمی رو خدمت رفقای عزیز عرض میکنم هر سرویسی از هرکجا تهیه کردید اگر گواهی TLS رو نداشت باید بدونید که اون سرویس اصلا امن نیست برای همینم تمام سرورهایی که در اشتراکتون اضافه کردیم دارای این گواهی امنیتی هستن و نیازی نیست نگران نشت دیتا یا لورفتن آیپی باشید چون ما از قبل فکر همه چیزش رو برای شماکردیم🤝

❤‍🔥2

9 Aug 2026, 18:39 UTC109 viewsread 12 August 2026

همراه اول و ایرانسل پرسرعت متصل بقیه اپراتورها رو تست نکردم،اکر مشکلی بود پشتیبانی بگید

9 Aug 2026, 18:37 UTC109 viewsread 12 August 2026
Photo

کارای سرویس مستقیم تقریبا تمومه،فقط مونده اضافه کردن چند پروتکل دیگه که سازگاری با همراه اول هم داره برای دریافت آخرین سرورها،اشتراکتون رو بروزرسانی کنید حتما داخل آخرین نسخه V2box وارد کنید دقت کنید،آخرین نسخه از کلاینت V2Box

8 Aug 2026, 15:42 UTC125 views7 reactionsread 12 August 2026
Voice message

چرا این چند روز قطع بودیم؟ دلیل اینکه این ویس رو گذاشتم این بوده که حس کردم حق مطلب رو نمیشود با متن ادا کرد بالاخره مشکلی هست که از سمت ما نبوده و صفرتاصد بنابر نحوه فیلترینگ شکل گرفته و خب خوشبختانه مشکل تقریبا خل شده و بزودی سرورهای جدیدتر اضافه خواهند شد تا کماکان کیفیتی که قولش رو داده بودیم رو بتونیم حفظ کنیم من از همه شما معذرت می‌خوام بابت این قطعی و امیدوارم بتونم برای تک تک شما عزیزان جبران بکنم مخلص همه

❤‍🔥7

8 Aug 2026, 15:37 UTC124 views3 reactionsread 12 August 2026
Photo

درود بر همراهان گرامی بدلیل سفت تر شدن پیو فیلترینگ توسط فیلترچی بی پدرومادر،این چند روز خیلی مشکلات داشتیم برای اتصال مجدد چون منطقه ای شده و روش مستقیم ممکنه برای شما کار نکنه اما خبر خوب اینه که سرویس مجدد متصل شد فقط کافیه اشتراکتون رو بروزرسانی کنید

❤‍🔥3

7 Aug 2026, 14:08 UTC138 views7 reactionsread 12 August 2026

لطفا پشتیبانی اسپم نکنید درحال پیگیری مشکل هستیم صبور باشید🤝

❤‍🔥7

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

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

“𝗧𝗥𝗢𝗬 𝗚𝗔𝗧𝗘|تِروی گِیت” (@TROYGATE), 4,241 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/TROYGATE.

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.