11 measurements spanning 17 days, net -45. 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 6,864–6,923 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
24 Aug 2026, 07:04
6,871
-6
21 Aug 2026, 08:16
6,877
-4
20 Aug 2026, 16:42
6,881
-9
17 Aug 2026, 22:02
6,890
+2
17 Aug 2026, 16:38
6,888
-8
14 Aug 2026, 17:23
6,896
-6
14 Aug 2026, 00:17
6,902
-11
11 Aug 2026, 04:01
6,913
no change
10 Aug 2026, 22:03
6,913
-3
7 Aug 2026, 14:46
6,916
no change
7 Aug 2026, 14:36
6,916
first reading
Engagement
6 posts held, back to 29 July 2020 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 12 pagesof 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 6 posts for this entry, the most recent from 24 May 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
330 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 58.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤🔥
192
58.2%
🔥
138
41.8%
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 5 of the 6 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 330reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 29 July 2020 to 24 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
Stars received
2,313
across the posts below
Posts paid on
4
of 5 we hold a reading for · 80%
Most on one post
2,020
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Zero_Creator. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 6 most recent posts we hold for this entry, published 29 July 2020 to 24 May 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🍑 گزارش آپدیت: فعالسازی سیستم کسب درآمد
🌟 از این پس، علاوهبر اشتراک در تبلیغات ممبری آپلودری، میتوانید از طریق بخش کسب درآمد در رباتساز، سرویسهای تکمیلی خود را فعال کرده و بدون نیاز به انجام مراحل اضافی، بهصورت خودکار از رباتهای خود درآمدزایی کنید.
💰 خدمات قابلفعالسازی برای درآمدزایی:
🔸 سین و ریاکشن
🔸 تبلیغات دکمهای
🔸 تبلیغات بنری
🔸 تبلیغات کپشن فایلها
✅ فقط کافیه آپشن موردنظر رو فعال کنید؛ تمام تبلیغ…
📢 آغاز همکاری رسمی گسترده @Uploaderi با رباتساز Zero
به اطلاع کاربران محترم میرسد که از این پس، خدمات گسترده آپلودری با رباتساز Zero بهصورت یکپارچه و هوشمند ارائه خواهد شد.
این ادغام با هدف ارتقای کیفیت تبلیغات، کنترل دقیقتر و افزایش درآمد کاربران انجام شده است.
📌 امکانات و تسهیلات این همکاری ویژه:
🔹 امکان اشتراک در تبلیغات گسترده از طریق پنل رباتساز
🔹 قابلیت ستکردن لینک تبلیغات مستقیم روی رباتها
🔹 حذف خود…
گزارش رونمایی ربات - نسخه 0.3.5 Beta
🔔 با سلام خدمت شما دوستان عزیز , با افتخار نسخه 0.3.5 Beta ربات را معرفی میکنیم , این آپدیت شامل بهبودها و قابلیتهای جدیدی است که تجربه کاربران را ارتقا میدهد! در ادامه ویژگیهای کلیدی این نسخه را میبینید :
1. بهینهسازی عملکرد
- سرعت بارگذاری فایلها و دسترسی به بخشهای مختلف ربات افزایش یافته است!
2. افزودن قابلیتهای جدید
- قابلیت مدیریت پیشرفته فایلها و گزینهه…
اعضای محترم مجموعه،
از این لحظه، بنده به عنوان مالک جدید این مجموعه آپلودرساز GSV سابق در خدمت شما هستم. در راستای بهبود کیفیت و حفظ امنیت، رعایت چند مورد زیر ضروری است:
1. حفظ حقوق و اصالت آپشنهای رباتها: کپی کردن و استفاده از آپشنهای اختصاصی رباتهای آپلودری این مجموعه ممنوع است و در صورت مشاهده هرگونه تخلف، برخورد لازم انجام خواهد شد.
2. مالکیت مستقل: این مجموعه هیچ ارتباطی با مالکیت قبلی ندارد و تمامی حقوق …
رباتساز Zero 🚀
💎 استخراج پیشرفته با دو متد اختصاصی و همگانی
سرعت فوقالعاده در انتقال و استخراج ممبر،
پشتیبانی از گستردههای معتبر آپلودری
💰 فرصتی برای درآمدزایی
با قفلهای ممبری و خدمات تکمیلی، بهسادگی کسب درآمد کنید و از امکانات ربات به بهترین شکل بهره ببرید
با رباتساز Zero، ابزار کامل و حرفهای برای ساخت و مدیریت رباتهای درآمدزا را در اختیار دارید
🌟 @ZeroCreator
🌟 @ZeroCreatorBot
Showing the 6 most recent of 6 posts we hold for @Zero_Creator. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 24 August 2026 — this
entry's latest reading, not the date you are reading this.
“𝗭ᴇʀᴏ 𝗖ʀᴇᴀᴛᴏʀ | آپلودرساز” (@Zero_Creator), 6,871 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/Zero_Creator.
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.