🔴فوری نتانیاهو طبق آرا و نظرسنجی رسانه ها به شدت عقب افتاده و ایزنکوت پیشتاز شده ‼️
❤102🔥52👍50🥰38

Channel
@lordxau
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Polls · Citations · Domains linked from posts · Cite this entry
2,128,965subscribers
+666,792 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1002330760188 |
|---|---|
| Type | Channel |
| Username | @lordxau |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 October 2026 |
| Measurements held | 52 |
| Confirmed unchanged | 1 time, most recently 27 October 2026 |
| On Telegram | t.me/lordxau |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 84% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
On 3,632 of the 5,254 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0319 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /9354716 Oct 2026, 01:06 UTC | 30 minutes | 2,330 → 2,730at least +390 | 277 → 278at most +2 | +12.4 |
| /9354716 Oct 2026, 01:06 UTC | 30 minutes | 3,190 → 3,690at least +490 | 284 → 286at most +3 | +15.6 |
| /9354716 Oct 2026, 01:06 UTC | 30 minutes | 3,690 → 4,280at least +580 | 286 → 289at most +4 | +18.5 |
| /9354716 Oct 2026, 01:06 UTC | 34 minutes | 4,280 → 5,040at least +750 | 289 → 293at most +5 | +23.9 |
| /9354716 Oct 2026, 01:06 UTC | 30 minutes | 6,120 → 7,350at least +1,220 | 304 → 308at most +5 | +38.9 |
| /9354716 Oct 2026, 01:06 UTC | 24 hours | 10,100 → 12,200at least +2,000 | 327 → 341at most +15 | +63.8 |
| /9354516 Oct 2026, 01:06 UTC | 30 minutes | 3,080 → 3,580at least +490 | 282 → 284at most +3 | +15.6 |
| /9354516 Oct 2026, 01:06 UTC | 30 minutes | 3,580 → 4,140at least +550 | 284 → 287at most +4 | +17.5 |
| /9354516 Oct 2026, 01:06 UTC | 30 minutes | 5,900 → 7,130at least +1,220 | 302 → 306at most +5 | +38.9 |
| /9354516 Oct 2026, 01:06 UTC | 65 minutes | 8,440 → 9,780at least +1,330 | 324 → 329at most +6 | +42.4 |
| /9354516 Oct 2026, 01:06 UTC | 24 hours | 9,780 → 12,000at least +2,120 | 329 → 342at most +14 | +67.6 |
| /9479823 Oct 2026, 08:25 UTC | 35 minutes | 4,760 → 5,990at least +1,220 | 320 → 320at most +1 | +38.9 |
| /9479823 Oct 2026, 08:25 UTC | 35 minutes | 5,990 → 7,230at least +1,230 | 320 → 322at most +3 | +39.2 |
| /9479823 Oct 2026, 08:25 UTC | 30 minutes | 7,230 → 8,460at least +1,220 | 322 → 325at most +4 | +38.9 |
| /9479823 Oct 2026, 08:25 UTC | 35 minutes | 8,460 → 10,200at least +1,640 | 325 → 327at most +3 | +52.3 |
| /9479823 Oct 2026, 08:25 UTC | 3.2 hours | 19,700 → 23,100at least +3,300 | 335 → 335at most +1 | +105.2 |
| /8887829 Sept 2026, 17:52 UTC | 40 minutes | 13,600 → 16,900at least +3,200 | 453 → 468at most +16 | +102.0 |
| /8887829 Sept 2026, 17:52 UTC | 30 minutes | 16,900 → 23,100at least +6,100 | 468 → 475at most +8 | +194.5 |
| /8887829 Sept 2026, 17:52 UTC | 35 minutes | 23,100 → 29,600at least +6,400 | 475 → 479at most +5 | +204.1 |
| /8887829 Sept 2026, 17:52 UTC | 2.9 hours | 29,600 → 36,200at least +6,500 | 479 → 488at most +10 | +207.3 |
| /8888229 Sept 2026, 18:00 UTC | 40 minutes | 13,600 → 17,900at least +4,200 | 485 → 516at most +32 | +133.9 |
| /8888229 Sept 2026, 18:00 UTC | 30 minutes | 17,900 → 23,100at least +5,100 | 516 → 525at most +10 | +162.6 |
| /8888229 Sept 2026, 18:00 UTC | 35 minutes | 23,100 → 29,600at least +6,400 | 525 → 535at most +11 | +204.1 |
| /8888229 Sept 2026, 18:00 UTC | 3.5 hours | 29,600 → 36,100at least +6,400 | 535 → 553at most +19 | +204.1 |
| /8892530 Sept 2026, 05:55 UTC | 35 minutes | 7,530 → 9,580at least +2,040 | 318 → 320at most +3 | +65.0 |
| /8892530 Sept 2026, 05:55 UTC | 1.7 hours | 9,580 → 11,900at least +2,220 | 320 → 321at most +2 | +70.8 |
| /8892530 Sept 2026, 05:55 UTC | 2.7 hours | 11,900 → 14,000at least +2,000 | 321 → 322at most +2 | +63.8 |
| /8892530 Sept 2026, 05:55 UTC | 12 hours | 14,000 → 17,700at least +3,600 | 322 → 323at most +2 | +114.8 |
| /8892630 Sept 2026, 05:55 UTC | 35 minutes | 7,530 → 9,590at least +2,050 | 336 → 338at most +3 | +65.4 |
| /8892630 Sept 2026, 05:55 UTC | 1.7 hours | 9,590 → 11,500at least +1,810 | 338 → 339at most +2 | +57.7 |
| /8892630 Sept 2026, 05:55 UTC | 2.7 hours | 11,500 → 13,900at least +2,300 | 339 → 340at most +2 | +73.3 |
| /8892630 Sept 2026, 05:55 UTC | 12 hours | 13,900 → 17,100at least +3,100 | 340 → 340at most +1 | +98.8 |
| /8894630 Sept 2026, 06:14 UTC | 17 minutes | 11,700 → 13,700at least +1,900 | 316 → 316at most +1 | +60.6 |
| /8894630 Sept 2026, 06:14 UTC | 35 minutes | 13,700 → 16,100at least +2,300 | 316 → 316at most +1 | +73.3 |
| /8894630 Sept 2026, 06:14 UTC | 30 minutes | 16,100 → 18,900at least +2,700 | 316 → 317at most +2 | +86.1 |
| /8894630 Sept 2026, 06:14 UTC | 35 minutes | 18,900 → 22,600at least +3,600 | 317 → 317at most +1 | +114.8 |
| /894371 Oct 2026, 19:19 UTC | 35 minutes | 12,600 → 15,200at least +2,500 | 398 → 405at most +8 | +79.7 |
| /894371 Oct 2026, 19:19 UTC | 35 minutes | 15,200 → 20,000at least +4,700 | 405 → 420at most +16 | +149.9 |
| /894371 Oct 2026, 19:19 UTC | 30 minutes | 20,000 → 23,900at least +3,800 | 420 → 422at most +3 | +121.2 |
| /894371 Oct 2026, 19:19 UTC | 35 minutes | 23,900 → 29,100at least +5,100 | 422 → 428at most +7 | +162.6 |
| /896702 Oct 2026, 14:22 UTC | 55 minutes | 10,500 → 14,200at least +3,600 | 368 → 370at most +3 | +114.8 |
| /896702 Oct 2026, 14:22 UTC | 35 minutes | 14,900 → 17,600at least +2,600 | 370 → 371at most +2 | +82.9 |
| /896702 Oct 2026, 14:22 UTC | 35 minutes | 17,600 → 21,500at least +3,800 | 371 → 371at most +1 | +121.2 |
| /896702 Oct 2026, 14:22 UTC | 2.8 hours | 21,500 → 27,700at least +6,100 | 371 → 374at most +4 | +194.5 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the key view_reaction_decoupling, last confirmed 27 October 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Oct 2026, 13:27 | 2,128,965 | -7,897 |
| 26 Oct 2026, 16:36 | 2,136,862 | -8,186 |
| 25 Oct 2026, 14:51 | 2,145,048 | -2,308 |
| 24 Oct 2026, 17:38 | 2,147,356 | -3,169 |
| 23 Oct 2026, 19:40 | 2,150,525 | -7,540 |
| 22 Oct 2026, 17:50 | 2,158,065 | -3,765 |
| 21 Oct 2026, 14:19 | 2,161,830 | -5,863 |
| 20 Oct 2026, 13:11 | 2,167,693 | -6,898 |
| 19 Oct 2026, 14:46 | 2,174,591 | -5,946 |
| 18 Oct 2026, 15:17 | 2,180,537 | -7,211 |
| 17 Oct 2026, 13:19 | 2,187,748 | -8,079 |
| 16 Oct 2026, 15:08 | 2,195,827 | -11,815 |
| 15 Oct 2026, 16:35 | 2,207,642 | -10,354 |
| 14 Oct 2026, 15:38 | 2,217,996 | -16,757 |
| 13 Oct 2026, 06:49 | 2,234,753 | -52,430 |
| 9 Oct 2026, 00:15 | 2,287,183 | -105,310 |
| 4 Oct 2026, 17:17 | 2,392,493 | +1,068,303 |
| 26 Sept 2026, 14:37 | 1,324,190 | -35,543 |
| 19 Sept 2026, 16:19 | 1,359,733 | -14,044 |
| 17 Sept 2026, 03:58 | 1,373,777 | first reading |
11,567 posts held, back to 7 August 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 181 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. It is computed over the 6,126 of 6,129 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 October 2026 |
|---|---|
| Posts held | 11,567 (7 August 2026 – 27 October 2026) |
| Views total | 92,281,645 |
| Reactions total | 2,448,705 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Oct 2026, 14:25 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.
Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 5,476 of this channel’s own posts over the last 30 days (1,310 of the 24-hour readings behind this are interpolated, not measured directly): across 2,857 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 77 minutes of being posted; a typical post has already reached 45.8% of its 24-hour view count within the first hour, and 85.5% within the first six; the median 24-hour reach across those posts is 13,500 views — 0.634% of this channel’s own subscriber count (90th percentile 29,192).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /9533127 Oct 2026, 14:22 UTC | 13 minutes – 3 minutes old | 1,160 views ~242 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /9533027 Oct 2026, 14:16 UTC | 19 minutes – 9 minutes old | 3,310 views ~356 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /9532927 Oct 2026, 14:15 UTC | 19 minutes – 9 minutes old | 3,320 views ~310 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /9532827 Oct 2026, 14:15 UTC | 19 minutes – 9 minutes old | 3,320 views ~309 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /9532727 Oct 2026, 14:15 UTC | 110 minutes – 10 minutes old | 3,320 views ~281 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /9532627 Oct 2026, 14:14 UTC | 110 minutes – 10 minutes old | 3,320 views ~306 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /9532527 Oct 2026, 14:11 UTC | 114 minutes – 14 minutes old | 3,320 views ~322 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /9532427 Oct 2026, 14:10 UTC | 115 minutes – 15 minutes old | 4,320 views ~327 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
382,107 reactions across 1,000 posts, in 4 distinct kinds. The most used accounts for 43.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 167,917 | 43.9% | |
| 👍 | 78,005 | 20.4% | |
| 🔥 | 70,514 | 18.5% | |
| 🥰 | 65,671 | 17.2% |
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 1,000 of the 1,000 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 382,107 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 October 2026 to 27 October 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.
🔴فوری نتانیاهو طبق آرا و نظرسنجی رسانه ها به شدت عقب افتاده و ایزنکوت پیشتاز شده ‼️
❤102🔥52👍50🥰38
برایند امروز: +640pip -20 +90 -20 +60 +60 +70 +60 -20 +70 +100 +60 +50 -20 +100
❤158🔥76👍65🥰57
+100pip
❤114🔥69👍65🥰62
Xau:4033
❤117🔥67🥰65👍60
Photo, posted without a caption
👍88❤73🔥67🥰53
ببندش
❤128🥰62👍60🔥56
Xau:4036
❤125🥰76🔥63👍58
اگر فری زد بگیرید باز
❤150🔥68👍60🥰49
برگشت نزندیک ورود
❤120🥰67👍65🔥63
Xau:4036
❤134🔥68🥰60👍52
فری کن مجدد
❤116👍71🔥62🥰60
ریخت
❤109🔥69👍68🥰58
Showing the 12 most recent of 11,567 posts we hold for @lordxau. 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.
@lordxau edited 27 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
در صورتی قطعی نت کجا ادامه بدیم؟
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 October 2026 to 27 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 2 registered channels — 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.
One domain this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“𝗟𝗢𝗥𝗗 𝗖𝗟𝗨𝗕- 𝐖𝐀𝐑-☠️𝐑𝐎𝐎𝐌/ اسکلپ ویژه رفرال ها سیگنال طلا بیتکوین کریپتو فارکس” (@lordxau), 2,128,965 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/lordxau.
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.