سپاه پاسداران: دقایقی قبل دوتا نفتکش رو توی تنگه زدیم @NPROXY
❤166🤣44🖕22👏18🔥9👍3

Channel
@NPROXY
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
2,259,383subscribers
-325,644 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001237450487 |
|---|---|
| Type | Channel |
| Username | @NPROXY |
| Description | Get the strongest Telegram proxies here ! ☇ Collection of MTProto Proxies for Telegram.☀️ Desktop v1.2.18+ macOS v3.8.3+ Android v4.8.8+ X Android v0.20.10.931+ iOS v4.8.2+ |
| Created | 20 July 2018 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/NPROXY |
Other / unclassifiable — 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 64% 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.
Posts published here appear in near-verbatim form on 12 other registered channels. This entry also sits inside a group of 245 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @pezeshkian_com/332937 Mar 2026, 19:39 UTC | @NPROXY/20072 · this entry7 Mar 2026, 19:39 UTC | 0.99 | under a minute |
| @pezeshkian_com/4524615 May 2026, 22:37 UTC | @NPROXY/29115 · this entry15 May 2026, 22:45 UTC | 0.99 | 8 minutes |
| @pezeshkian_com/4206218 Apr 2026, 21:52 UTC | @NPROXY/28753 · this entry18 Apr 2026, 22:00 UTC | 0.99 | 8 minutes |
| @pezeshkian_com/3777831 Mar 2026, 16:33 UTC | @NPROXY/24523 · this entry31 Mar 2026, 16:33 UTC | 0.99 | under a minute |
| @pezeshkian_com/3526319 Mar 2026, 16:48 UTC | @NPROXY/22025 · this entry19 Mar 2026, 16:48 UTC | 0.99 | under a minute |
| @pezeshkian_com/3410711 Mar 2026, 19:39 UTC | @NPROXY/20876 · this entry11 Mar 2026, 19:39 UTC | 0.99 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @pezeshkian_com | 2,894 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | @pezeshkian_com (2,881–13) |
| @akhbarefori | 684 (8/8 hand-verifiable sample passed) | 0.99 | 4 minutes | @akhbarefori (594–90) |
| @farsna | 468 (8/8 hand-verifiable sample passed) | 0.98 | 7 minutes | @farsna (442–26) |
| @emrooz | 421 (8/8 hand-verifiable sample passed) | 0.97 | 10 minutes | @emrooz (367–54) |
| @khabarfori | 399 (8/8 hand-verifiable sample passed) | 0.98 | 6 minutes | this entry (242–157) |
| @khabarfouri | 397 (8/8 hand-verifiable sample passed) | 0.97 | 9 minutes | this entry (229–168) |
| @newsbin | 373 (8/8 hand-verifiable sample passed) | 0.94 | under a minute | @newsbin (367–6) |
| @LinkdoniXe | 296 (8/8 hand-verifiable sample passed) | 0.95 | under a minute | this entry (288–8) |
| @akharinkhabar | 290 (8/8 hand-verifiable sample passed) | 0.95 | 7 minutes | @akharinkhabar (201–89) |
| @km_ap | 286 (8/8 hand-verifiable sample passed) | 0.97 | 17 minutes | this entry (243–43) |
| @itsEnded | 266 (8/8 hand-verifiable sample passed) | 0.94 | under a minute | this entry (266–0) |
| @akhbareisfahan | 188 (8/8 hand-verifiable sample passed) | 0.98 | 17 minutes | this entry (143–45) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 457 of the 5,821 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 18,319 comparable posts for this entry, running 19 November 2022 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 245 channels, the one whose matching posts we hold earliest is @akharinkhabar. That is a statement about our reading window, not a claim of authorship.
On 45 of the 1,457 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.0067 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /3491018 Oct 2026, 12:51 UTC | 35 minutes | 10,500 → 12,400at least +1,800 | 55 → 57at most +3 | +12.1 |
| /3491018 Oct 2026, 12:51 UTC | 4.2 hours | 25,600 → 29,900at least +4,200 | 117 → 123at most +7 | +28.2 |
| /3508322 Oct 2026, 05:30 UTC | 4.0 hours | 25,400 → 30,800at least +5,300 | 168 → 174at most +7 | +35.6 |
| /3508322 Oct 2026, 05:30 UTC | 6 days | 40,100 → 46,400at least +6,200 | 195 → 203at most +9 | +41.7 |
| /3476015 Oct 2026, 06:33 UTC | 30 minutes | 7,210 → 9,110at least +1,890 | 44 → 45at most +2 | +12.7 |
| /3486517 Oct 2026, 11:53 UTC | 35 minutes | 7,370 → 9,100at least +1,720 | 27 → 27at most +1 | +11.6 |
| /3487317 Oct 2026, 15:22 UTC | 56 minutes | 10,900 → 15,100at least +4,100 | 39 → 43at most +5 | +27.6 |
| /3498919 Oct 2026, 20:13 UTC | 55 minutes | 14,100 → 17,600at least +3,400 | 64 → 67at most +4 | +22.9 |
| /3502220 Oct 2026, 14:10 UTC | 31 minutes | 8,850 → 11,400at least +2,450 | 33 → 36at most +4 | +16.5 |
| /3505021 Oct 2026, 12:11 UTC | 55 minutes | 17,800 → 21,400at least +3,500 | 138 → 139at most +2 | +23.5 |
| /3505121 Oct 2026, 12:31 UTC | 4.3 hours | 20,300 → 25,200at least +4,800 | 198 → 202at most +5 | +32.3 |
| /3505221 Oct 2026, 12:50 UTC | 4.8 hours | 17,300 → 22,500at least +5,100 | 71 → 76at most +6 | +34.3 |
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 keys clone_copy · clone_mutual · clone_source · view_reaction_decoupling, last confirmed 13 November 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.
This channel is in a group of 245 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
194 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 21:39 | 2,259,383 | -4,941 |
| 10 Nov 2026, 02:56 | 2,264,324 | -3,314 |
| 8 Nov 2026, 16:56 | 2,267,638 | -3,507 |
| 7 Nov 2026, 08:38 | 2,271,145 | -2,974 |
| 6 Nov 2026, 09:05 | 2,274,119 | -2,937 |
| 5 Nov 2026, 06:39 | 2,277,056 | -2,429 |
| 4 Nov 2026, 06:35 | 2,279,485 | -2,666 |
| 3 Nov 2026, 02:46 | 2,282,151 | -2,418 |
| 2 Nov 2026, 04:49 | 2,284,569 | -2,403 |
| 1 Nov 2026, 06:50 | 2,286,972 | -2,633 |
| 31 Oct 2026, 03:16 | 2,289,605 | -2,845 |
| 30 Oct 2026, 04:58 | 2,292,450 | -2,282 |
| 29 Oct 2026, 07:38 | 2,294,732 | -3,004 |
| 28 Oct 2026, 03:57 | 2,297,736 | -2,736 |
| 27 Oct 2026, 01:37 | 2,300,472 | -2,487 |
| 26 Oct 2026, 01:20 | 2,302,959 | -2,579 |
| 25 Oct 2026, 03:07 | 2,305,538 | -2,675 |
| 24 Oct 2026, 04:48 | 2,308,213 | -3,363 |
| 23 Oct 2026, 04:58 | 2,311,576 | -2,664 |
| 22 Oct 2026, 01:27 | 2,314,240 | first reading |
29,419 posts held, back to 20 July 2018 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,007 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 13 November 2026 |
|---|---|
| Posts held | 29,419 (20 July 2018 – 13 November 2026) |
| Views total | 48,635,500 |
| Reactions total | 365,475 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 01:10 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.
Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 129 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 1,457 of this channel’s own posts over the last 30 days (4 of the 24-hour readings behind this are interpolated, not measured directly): across 1,412 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.7 hours of being posted; a typical post has already reached 27.6% of its 24-hour view count within the first hour, and 71.3% within the first six; the median 24-hour reach across those posts is 28,000 views — 1.24% of this channel’s own subscriber count (90th percentile 34,400).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /3622613 Nov 2026, 21:17 UTC | 628 minutes – 3.9 hours old | 10,200 views ~262 reactions | 60 minutes: 7,260 → 3.0 hours: 9,686 interp.still climbing at last reading | not yet at 24h | 28 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /3622513 Nov 2026, 20:59 UTC | 711 minutes – 4.2 hours old | 12,600 views ~134 reactions | 60 minutes: 8,799 interp. → 3.0 hours: 12,028 interp.still climbing at last reading | not yet at 24h | 35 minutesprovisional — final view count still climbing |
| /3622413 Nov 2026, 20:49 UTC | 721 minutes – 4.4 hours old | 14,600 views ~249 reactions | 60 minutes: 10,267 interp. → 3.0 hours: 13,800still climbing at last reading | not yet at 24h | 36 minutesprovisional — final view count still climbing |
| /3622313 Nov 2026, 20:11 UTC | 829 minutes – 5.0 hours old | 18,400 views ~190 reactions | 60 minutes: 10,900 → 3.0 hours: 17,304 interp.still climbing at last reading | not yet at 24h | 49 minutesprovisional — final view count still climbing |
| /3621913 Nov 2026, 19:52 UTC | 848 minutes – 5.3 hours old | 19,700 views ~138 reactions | 60 minutes: 11,560 interp. → 3.0 hours: 18,500still climbing at last reading | not yet at 24h | 48 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /3622013 Nov 2026, 19:52 UTC | 848 minutes – 5.3 hours old | 20,600 views ~76 reactions | 60 minutes: 11,872 interp. → 3.0 hours: 19,400still climbing at last reading | not yet at 24h | 48 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /3622113 Nov 2026, 19:52 UTC | 848 minutes – 5.3 hours old | 20,800 views ~94 reactions | 60 minutes: 11,872 interp. → 3.0 hours: 19,600still climbing at last reading | not yet at 24h | 49 minutesprovisional — final view count still climbing |
| /3622213 Nov 2026, 19:52 UTC | 848 minutes – 5.3 hours old | 21,400 views ~317 reactions | 60 minutes: 11,993 interp. → 3.0 hours: 20,100still climbing at last reading | not yet at 24h | 51 minutesprovisional — final view count still climbing |
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.
236,342 reactions across 1,000 posts, in 18 distinct kinds. The most used accounts for 37.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 87,940 | 37.2% | |
| ❤ | 50,908 | 21.5% | |
| 👍 | 46,350 | 19.6% | |
| 🖕 | 18,012 | 7.62% | |
| 😭 | 9,386 | 3.97% | |
| 👎 | 5,836 | 2.47% | |
| 👏 | 5,588 | 2.36% | |
| 🔥 | 3,310 | 1.40% | |
| 😡 | 3,126 | 1.32% | |
| 😨 | 2,824 | 1.19% | |
| 💯 | 891 | 0.377% | |
| 🙏 | 629 | 0.266% | |
| 🤝 | 457 | 0.193% | |
| 🤗 | 345 | 0.146% | |
| 🫡 | 331 | 0.14% | |
| 😘 | 214 | 0.091% | |
| ✍ | 103 | 0.044% | |
| 😇 | 92 | 0.039% |
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 236,342 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 25 October 2026 to 13 November 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.
Telegram’s own ‘edited’ marker: 0 of 1,471 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
سپاه پاسداران: دقایقی قبل دوتا نفتکش رو توی تنگه زدیم @NPROXY
❤166🤣44🖕22👏18🔥9👍3
فاکس نیوز: به دلیل بروز مشکلات فنی در سیستمهای ارتباطی کنترل ترافیک هوایی در سراسر ایالات متحده، تمامی پروازها لغو شدهاند @NPROXY
🤣98❤16🔥8🖕6👍4🙏2
ناو گروه هواپیمابر روزولت به 800 کیلومتری ایران رسیده @NPROXY
🖕177❤46👏7🤣7👍6😭6
سازمان رادیو و تلویزیون اسرائیل: رئیس ستاد کل ارتش این کشور از انجام عملیات نظامی علیه ایران حمایت میکند. @NPROXY
🖕133❤34👏10😡6🤣3👍2🔥2
سقاب اصفهانی؛ مدیر سازمان بهینه سازی انرژی : از این به بعد اگه میخواید برید سفر باید برنامه ریزی کنید و از سه ماه قبل بنزین ذخیره کنید. چون کارت سوخت جایگاه دیگه نداریم. @NPROXY
🖕92😡42❤2👎2
کانال 15 عبری: آیزنکوت همچنان بر موضع قبلی خود مبنی بر غیرضروری بودن آغاز فوری جنگ علیه ایران تأکید دارد و نظرش را تغییر نداده است. @NPROXY
🖕45❤25👏3👎2🔥1
محسن رضایی: اگر آمریکا حمله کند، جنگ حداکثر 5 روز طول میکشد. @NPROXY
🤣178👏87🖕28❤16💯4👎3😨1
گزارشات اولیه از انفجار در جاسک @NPROXY
😡62❤19🔥5🤣5👍3
“اشکال نداره بجاش صبح بیدار میشم میخونم” @NPROXY
🤣218❤11👍9😭2😡1
ترامپ: نابودکردن زیرساختها، صنعت و انرژی ایران فقط سه روز طول میکشد! @NPROXY
😡126🖕114👎26🤣22🙏12❤11🔥5👍4
بارون بیاد و هوس خوندن به سرت نزنه!!! @NPROXY
❤227👏46🤣13👍3👎3🔥3
عبدالله گنجی: تحویل مریم رجوی و مسیح علینژاد باید جزء شروط اصلی مذاکره با آمریکا قرار گیرد. @NPROXY
👍255🤣166👏20🖕8❤4
Showing the 12 most recent of 29,419 posts we hold for @NPROXY. 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.
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 17 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.
@NPROXY named 17 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 7 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 549 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
23 domains 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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“پروکسی ملی | Nova Proxy” (@NPROXY), 2,259,383 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/NPROXY.
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.