Technology — 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 10 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.
Growth
36 measurements spanning 62 days, net -3,376. 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 24,716–29,104 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)
Subscribers
Change
8 Oct 2026, 15:17
25,222
-134
4 Oct 2026, 01:00
25,356
-684
25 Sept 2026, 10:17
26,040
-324
17 Sept 2026, 10:59
26,364
-57
15 Sept 2026, 08:20
26,421
-40
13 Sept 2026, 20:38
26,461
-73
12 Sept 2026, 05:59
26,534
-79
9 Sept 2026, 22:21
26,613
-131
6 Sept 2026, 16:16
26,744
-83
4 Sept 2026, 08:18
26,827
-50
2 Sept 2026, 21:59
26,877
-58
1 Sept 2026, 19:55
26,935
-53
31 Aug 2026, 17:17
26,988
-33
30 Aug 2026, 16:43
27,021
-61
29 Aug 2026, 13:34
27,082
-56
28 Aug 2026, 15:45
27,138
-45
27 Aug 2026, 16:46
27,183
-38
26 Aug 2026, 19:33
27,221
-24
25 Aug 2026, 23:04
27,245
-83
24 Aug 2026, 22:35
27,328
first reading
Engagement
22 posts held, back to 8 June 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 84 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
7.33%
avg views ÷ 25,222 subscribers
Avg views / post
1,850
1 post measured
Reaction rate
0.378%
reactions ÷ views · ER floor
Posts in window
1
of 22 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
Window
Rolling 30 days · latest post in window 30 September 2026
Posts held
22 (8 June 2022 – 30 September 2026)
Views total
1,850
Reactions total
7
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Oct 2026, 11: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.
What this channel posts
Photos
33
Links
35
Lifetime counters from Telegram’s own channel header, read 10 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
1,756 reactions across 21 posts, in 11 distinct kinds. The most used accounts for 42.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
753
42.9%
👍
356
20.3%
😁
336
19.1%
😱
82
4.67%
🎉
77
4.38%
🤔
66
3.76%
🤯
34
1.94%
🔥
25
1.42%
🥰
18
1.03%
👏
8
0.456%
👎
1
0.057%
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 21 of the 22 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 1,756 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 8 June 2022 to 30 September 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.
📣 اطلاعیه نگهداری سرور تهران
🛠 به منظور ارتقای سخت افزاری و انجام عملیات نگهداری روی زیرساخت سرور تهران، روز پنجشنبه ۹ مهرماه در بازه ساعت 09:00 الی 12:00 عملیات فنی انجام خواهد شد.
📍 ایران | سرور تهران
⭕️ در طول این بازه ممکن است سرویس های مستقر روی این سرور برای مدت کوتاهی با قطعی یا عدم دسترسی مواجه شوند.
✅ تلاش می کنیم مدت اختلال به حداقل برسد و پس از پایان عملیات، سرویس ها به وضعیت عادی بازخواهند گشت.
از هم…
🌐 اتصال در هر شرایطی
⚡️ دسترسی محلی فعال شد
از این پس یک مسیر جایگزین برای اتصال به سرور مجازی خود در اختیار دارید.
بدون نیاز به تغییر IP سرور، میتوانید از طریق آدرس محلی به سرویس های Remote Desktop و SSH متصل شوید و مدیریت سرور خود را ادامه دهید.
برای فعالسازی دسترسی محلی، از طریق پورتال کاربری اقدام کنید:
portal.sarvdata.cloud
🌱 سرودیتا، زیر ساخت ابری همواره در دسترس، برای رشد بی وقفه
🌐 sarvdata.com
📯 @Sarvda
📣 کاربران گرامی سرودیتا،
🛠 به منظور انجام عملیات نگهداری دوره ای و به روزرسانی زیرساخت، در بامداد شنبه ۱۷ مرداد ماه سرویس های زیر تحت عملیات نگهداری قرار خواهند گرفت:
📍 هلند | سرور های مجازی SSD
📍 آمریکا | سرور های مجازی SSD
📍 ایران | سرور های مجازی NVME
⏰ عملیات در بازه ساعت 01:00 الی 03:00 بامداد انجام خواهد شد. در طول این بازه، سرورهای مجازی تحت تاثیر ریستارت شده و ممکن است برای مدتی از دسترس خارج شوند.
✅ پس از…
📣 کاربران گرامی سرودیتا،
⭕️ در راستای ارائه سرویس پایدارتر و رفع کامل اختلالات دسترسی ناشی از شرایط اینترنت، دامنه اصلی پورتال کاربری سرودیتا به صورت یکپارچه و دائمی به آدرس ابری ما منتقل شد.
📍 توجه داشته باشید که به دلیل تغییر نام دامنه، نیاز است اطلاعات ورود خود را یک بار دیگر وارد نمایید. چنانچه رمز عبور شما در مرورگر یا نرمافزارهای مدیریت رمز عبور (Password Managers) ذخیره شده است، با یک بار ورود دستی، اطلاعات…
📣 کاربران گرامی سرودیتا،
✅ پورتال کاربری مجددا از طریق آدرس جایگزین در دسترس قرار گرفت. چنانچه در دسترسی به آدرس اصلی با اختلال مواجه هستید، میتوانید از طریق لینک زیر وارد شوید.
🔗 https://portal.sarvdata.cloud
لازم به ذکر است که آدرس قبلی (portal.sarvdata.com) همچنان فعال است، اما با توجه به شرایط ناپایدار اینترنت، استفاده از آدرس جدید برای تجربه سرعت بالاتر و پایداری بیشتر توصیه میگردد.
📯 @SarvData
📣 کاربران گرامی سرودیتا،
با توجه به محدودیتهای اخیر اینترنت و بهمنظور تسهیل دسترسی شما عزیزان به پنل کاربری، آدرس جدیدی برای ورود به پورتال در نظر گرفته شده است.
چنانچه در دسترسی به آدرس اصلی با اختلال مواجه هستید، میتوانید از طریق لینک زیر وارد شوید:
✅ آدرس جدید:
🔗 https://portal.sarvdata.cloud
لازم به ذکر است که آدرس قبلی (portal.sarvdata.com) همچنان فعال است، اما با توجه به شرایط ناپایدار اینترنت، استفاده از …
📍 پیرو قطع برق دیتا سنتر های برج میلاد؛ ups سرور ها بالا رفته و باعث افزایش دمای سرور های دیتا سنتر های برج میلاد شده است.
📍 لازم به ذکر است که سرور های سرودیتا که در دیتا سنتر برج میلاد هستند کاملا پایدار بوده و مشکلی ندارند.
📯 @sarvdata
⭕️ طبق اعلام شرکت ارتباطات زیرساخت، یک اختلال روی ترافیک IXP ( داخل کشور ) در مرکز انقلاب اسلامی ( LCT ) به وجود آمده که در حال بررسی است. اختلال موجود روی ترافیک داخلی سرور ها و همین طور اینترنت خانگی مربوط به همین مسئله است و طی ساعات آتی برطرف خواهد شد.
📯 @sarvdata
Showing the 12 most recent of 22 posts we hold for @SarvData. 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.
Posts edited after publishing
@SarvData edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
8 August 2026
Most recent edit
9 August 2026
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 8 October 2026 — this
entry's latest reading, not the date you are reading this.
“Sarvdata | سرودیتا” (@SarvData), 25,222 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/SarvData.
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.