Posted without readable text
👎3👍2💩2🥰1😴1

Channel
@sdzymax
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
63,386subscribers
+11,061 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001099992681 |
|---|---|
| Type | Channel |
| Usernames | @rrrrw @sdzymax |
| Created | Between 1 November 2016 and 31 December 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/sdzymax |
Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 07:41 | 63,386 | +184 |
| 17 Sept 2026, 13:38 | 63,202 | +386 |
| 16 Sept 2026, 01:20 | 62,816 | +40 |
| 15 Sept 2026, 16:02 | 62,776 | +41 |
| 14 Sept 2026, 08:01 | 62,735 | -12 |
| 13 Sept 2026, 23:41 | 62,747 | +260 |
| 12 Sept 2026, 18:02 | 62,487 | -71 |
| 12 Sept 2026, 05:18 | 62,558 | -9 |
| 10 Sept 2026, 18:55 | 62,567 | +179 |
| 9 Sept 2026, 20:37 | 62,388 | +414 |
| 7 Sept 2026, 18:40 | 61,974 | +333 |
| 6 Sept 2026, 12:36 | 61,641 | +438 |
| 4 Sept 2026, 17:41 | 61,203 | +204 |
| 4 Sept 2026, 01:42 | 60,999 | +95 |
| 3 Sept 2026, 02:05 | 60,904 | -19,632 |
| 2 Sept 2026, 17:08 | 80,536 | +69 |
| 1 Sept 2026, 20:54 | 80,467 | +32 |
| 1 Sept 2026, 14:12 | 80,435 | +19 |
| 31 Aug 2026, 23:25 | 80,416 | +50 |
| 31 Aug 2026, 13:33 | 80,366 | first reading |
30 posts held, back to 25 June 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 60 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 30 (25 June 2026 – 2 September 2026) |
| Views total | 15,735 |
| Reactions total | 77 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 06:24 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.
249 reactions across 24 posts, in 11 distinct kinds. The most used accounts for 50.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 125 | 50.2% | |
| 👍 | 62 | 24.9% | |
| 💩 | 15 | 6.02% | |
| 🤣 | 10 | 4.02% | |
| 🖕 | 9 | 3.61% | |
| 👎 | 8 | 3.21% | |
| 🔥 | 6 | 2.41% | |
| 🥰 | 6 | 2.41% | |
| 🤡 | 4 | 1.61% | |
| 👏 | 3 | 1.20% | |
| 😴 | 1 | 0.402% |
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 25 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 249 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 25 June 2026 to 2 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sdzymax. 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 30 most recent posts we hold for this entry, published 25 June 2026 to 2 September 2026. 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.
Posted without readable text
👎3👍2💩2🥰1😴1
🎊金秋九月,硕果盈枝🚀 感谢您一直以来对「上帝之眼」的信任与支持。 愿新的九月, 愿您生意兴隆、财源广进, 所行皆坦途,所求皆如愿, 事业蒸蒸日上,生活顺遂安宁。 新的月份,我们也将继续秉持专业、稳定、负责的态度, 为每一份信任提供更好的服务。 上帝之眼团队敬上 🙏
👍3❤2🔥1
上帝之眼|官方公告@sdzymax pinned «»
Posted without readable text
Posted without readable text
👍24❤3🥰3👏2🔥2
⚠️外面骗子横行,谨防各种套路!⚠️ 市场鱼龙混杂,各种套路层出不穷: 👎 先交押金 👎 查完再收解密费 👎 签所谓保密协议才能查看 👎 查询过程中不断加价 👎 查不到不退款 👎 低价引流,后续层层收费 ➡️感谢你选择【上帝之眼】。 🔥我们始终坚持公开、透明、诚信的服务原则: ✔️全程无押金 ✔️全程无套路 ✔️无解密费 ✔️无保密协议 ✔️无任何隐形收费 ✔️明码标价,价格透明 ✔️查前确认,查后不加价 ⭐️ 在这里,你不用担心被套路,也不用担心临时加价。 ⭐️ 选择上帝之眼,就是选择一份安心与信任。 ⭐️ 上帝之眼|诚信经营,用实力赢得信任。 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️
👍10❤6🖕4🤡4🤣3💩1
☀️🎆上帝之眼查档专家🎆 🔥🔥公群上押150000u 🔥🔥 https://t.me/+mSULXpfBLrZlYjc0
👍5💩4❤2
全部恢复 优化查询速度 优化关联数据 🚀🚀上帝之眼最强社工库合集 📈📉 ⌨️MAX 一线:@sdzymaxbot 正常使用 ⌨️MAX 二线:@sdzymaxabot 正常使用 ⌨️PRO大头版: @sdzysgk_bot 正常使用 ⌨️ultra增强版: @sdzyultra_bot 正常使用 ⚡️⚡️⚡️ @sdzy01 @sdzy007 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️
❤12👍3
上帝之眼|官方公告@sdzymax pinned «🚀🚀上帝之眼最强社工库合集 📈📉 ⌨️MAX 一线:@sdzymaxbot 正常使用 ⌨️MAX 二线:@sdzymaxabot 正常使用 ⌨️PRO大头版: @sdzysgk_bot 正常使用 ⌨️ultra增强版: @sdzyultra_bot 正常使用 ⚡️⚡️⚡️ @sdzy01 @sdzy007 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️»
🟦🟦🟦 原@sdzymax_bot失效 换最新,数据不变 积分不变 @sdzymaxbot @sdzymaxabot
👍4👎2
🚀🚀上帝之眼最强社工库合集 📈📉 ⌨️MAX 一线:@sdzymaxbot 正常使用 ⌨️MAX 二线:@sdzymaxabot 正常使用 ⌨️PRO大头版: @sdzysgk_bot 正常使用 ⌨️ultra增强版: @sdzyultra_bot 正常使用 ⚡️⚡️⚡️ @sdzy01 @sdzy007 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️
❤1
⚠️外面骗子横行,谨防各种套路!⚠️ 市场鱼龙混杂,各种套路层出不穷: 👎 先交押金 👎 查完再收解密费 👎 签所谓保密协议才能查看 👎 查询过程中不断加价 👎 查不到不退款 👎 低价引流,后续层层收费 ➡️感谢你选择【上帝之眼】。 🔥我们始终坚持公开、透明、诚信的服务原则: ✔️全程无押金 ✔️全程无套路 ✔️无解密费 ✔️无保密协议 ✔️无任何隐形收费 ✔️明码标价,价格透明 ✔️查前确认,查后不加价 ⭐️ 在这里,你不用担心被套路,也不用担心临时加价。 ⭐️ 选择上帝之眼,就是选择一份安心与信任。 ⭐️ 上帝之眼|诚信经营,用实力赢得信任。 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️
❤6
Showing the 12 most recent of 30 posts we hold for @sdzymax. 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.
@sdzymax edited 3 posts 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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@sdzymax named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“上帝之眼|官方公告@sdzymax” (@sdzymax), 63,386 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/sdzymax.
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.