Telegram RegisterThe public register of Telegram
Telegram profile photo for Exa Service | اِگزا سرویس

Channel

Exa Service | اِگزا سرویس

@Exa_Service

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

9,106subscribers

-1,228 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-1002089160555
TypeChannel
Username@Exa_Service
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held13
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/Exa_Service

Growth

9,10610,3349,7207 August 2026 — 10,334 subscribers7 August 2026 — 10,324 subscribers8 August 2026 — 10,259 subscribers9 August 2026 — 10,209 subscribers10 August 2026 — 10,142 subscribers11 August 2026 — 10,099 subscribers12 August 2026 — 10,042 subscribers14 August 2026 — 9,945 subscribers17 August 2026 — 9,767 subscribers20 August 2026 — 9,660 subscribers24 August 2026 — 9,346 subscribers27 August 2026 — 9,203 subscribers30 August 2026 — 9,106 subscribers7 August 202630 August 2026
13 measurements spanning 23 days, net -1,228. 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 8,922–10,518 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 07:139,106-97
27 Aug 2026, 13:039,203-143
24 Aug 2026, 04:089,346-314
20 Aug 2026, 06:539,660-107
17 Aug 2026, 12:389,767-178
14 Aug 2026, 03:269,945-97
12 Aug 2026, 18:0710,042-57
11 Aug 2026, 20:4810,099-43
10 Aug 2026, 22:3310,142-67
9 Aug 2026, 23:3210,209-50
8 Aug 2026, 23:5610,259-65
7 Aug 2026, 23:4810,324-10
7 Aug 2026, 15:1510,334first reading

Engagement

45 posts held, back to 16 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 35 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.43%
avg views ÷ 9,106 subscribers
Avg views / post
130
31 posts measured
Reaction rate
2.33%
reactions ÷ views · ER floor
Posts in window
31
of 45 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. It is computed over the 13 of 31 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 August 2026
Posts held45 (16 July 202629 August 2026)
Views total4,039
Reactions total39
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 13:39 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

45 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 42.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1942.2%
👍817.8%
🔥817.8%
👏48.89%
💯36.67%
24.44%
🤩12.22%

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

Measured over the 45 most recent posts we hold, published 16 July 2026 to 29 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

28 Aug 2026, 21:15 UTC47 viewsread 29 August 2026

ببخشید یادم رفت فردا شب رأس ساعت 24

28 Aug 2026, 16:05 UTC52 views2 reactionsread 29 August 2026

راس ساعت 24 امشب یه چالش داریم 🥰 سه تا 10 گیگ هم جایزشه 🙂

🔥2

26 Aug 2026, 21:42 UTC48 viewsread 29 August 2026

✨ هدیه‌ای به پاس قدردانی از همراهی شما به پاس اعتماد و همراهی شما، یک کد تخفیف ویژه برای تمدید سرویس در نظر گرفتیم 👍 🟢 کد تخفیف: tamdid 💰 ۲۰٪ تخفیف برای تمدید ✔️ قابل استفاده برای سرویس‌های حجمی و نامحدود ❗️ محدود به ۲۰ استفاده ممنون که همراه ما هستید ❤️‍🔥

26 Aug 2026, 21:42 UTC57 viewsread 29 August 2026

🎁 نام کد تخفیف: offexa 🛍 درصد کد تخفیف: 20 📍پنل : حجمی ❗️ محدودیت استفاده :‌ 20 دریافت تست رایگان و خرید از طریق ربات : 👾 @exaservice_bot

24 Aug 2026, 20:26 UTC84 views2 reactionsread 29 August 2026

💎 شب بخیر رفقا؛ اگزا سرویس اینجاست 💙 اگه دنبال یه سرویس پایدار، سریع و مطمئن هستی، قبل از خرید می‌تونی کاملاً رایگان تستش کنی. 👌 ━━━━━━━━━━━━━━ 🚀 چرا اگزا سرویس؟ 🔹 تست رایگان قبل از خرید 🔹 ☄️ سرورهای سریع و پایدار 🔹 ⭐️ سرویس‌های حجمی و نامحدود 🔹 🏪 پشتیبانی در صورت بروز مشکل ━━━━━━━━━━━━━━ 💬 اول تست کن، بعد تصمیم بگیر. لازم نیست بدون اینکه از کیفیت سرویس مطمئن بشی، خرید کنی. تست رایگان رو بگیر و خودت کیفیت اتصال ر

2

24 Aug 2026, 12:53 UTC77 viewsread 29 August 2026

📣 خبر خوب برای دریافت تست رایگان! محدودیت دریافت تست رایگان ریست شد 🆓 از این لحظه می‌تونید مجدداً تست رایگان سرویس‌ها رو دریافت و قبل از خرید، کیفیت و سرعت اتصال رو بررسی کنید. 🚀 ✔️ فرصت خوبیه برای تست و انتخاب سرویس مناسب ~ دریافت تست رایگان و خرید از طریق ربات : 👾 @exaservice_bot

21 Aug 2026, 20:29 UTC100 viewsread 29 August 2026

در صورت وجود هرگونه مشکل، سؤال یا نیاز به راهنمایی، می‌تونید از طریق آیدی زیر با ما در ارتباط باشید. 👍 👑 : @amiirtaha

21 Aug 2026, 15:52 UTC111 viewsread 29 August 2026

📣 دعوت به همکاری با اِگزاسرویس اگر در زمینه فروش سرویس‌های اینترنتی، کانفیگ و VPN فعالیت دارید و دنبال یک همکاری مطمئن و پایدار هستید، می‌تونید به جمع همکاران اِگزاسرویس اضافه بشید. 🤝 ~ قیمت همکاری مناسب ~ پنل اختصاصی و مدیریت آسان ~ پشتیبانی و پاسخگویی سریع ~ سرویس‌های پایدار و متنوع ~ امکان همکاری بلندمدت 💬 برای دریافت شرایط همکاری و تعرفه‌ها، پیام بدید: 👑: @amiirtaha

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

Mentions

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

“Exa Service | اِگزا سرویس” (@Exa_Service), 9,106 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/Exa_Service.

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.