✔️اشتراک تانل بخری هیچوقت قطع نمیشی‼️
🗿29❤7💔7👍2

Channel
@spdnet
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Telegram's recommendations · Cite this entry
1,538,632subscribers
+948,452 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1002004232165 |
|---|---|
| Type | Channel |
| Username | @spdnet |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/spdnet |
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 86% 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 2 other registered channels. This entry also sits inside a group of 3 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 |
|---|---|---|---|
| @spdnet/2122 · this entry14 Jul 2026, 21:17 UTC | @spdnetVIP/50314 Jul 2026, 21:19 UTC | 1.00 | 2 minutes |
| @spdnet/2123 · this entry14 Jul 2026, 21:31 UTC | @spdnetVIP/50414 Jul 2026, 21:31 UTC | 1.00 | under a minute |
| @spdnet/2143 · this entry5 Aug 2026, 20:52 UTC | @spdnetVIP/5065 Aug 2026, 20:53 UTC | 1.00 | under a minute |
| @spdnetVIP/51010 Sept 2026, 20:34 UTC | @spdnet/2156 · this entry10 Sept 2026, 20:35 UTC | 1.00 | under a minute |
| @spdnet/2158 · this entry9 Oct 2026, 11:25 UTC | @spdnetVIP/5129 Oct 2026, 11:25 UTC | 1.00 | under a minute |
| @spdnet/2154 · this entry6 Sept 2026, 20:04 UTC | @SvnV2ray/90726 Sept 2026, 20:07 UTC | 1.00 | 3 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @spdnetVIP | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (7–2) |
| @SvnV2ray | 12 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (12–0) |
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. 2 of the 2 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 68 comparable posts for this entry, running 26 June 2026 to 10 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 3 channels, the one whose matching posts we hold earliest is @spdnet — which is this entry. That is a statement about our reading window, not a claim of authorship.
On 16 of the 126 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.0024 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /24723 Nov 2026, 15:38 UTC | 31 minutes | 24,100 → 32,900at least +8,700 | 832 → 836at most +5 | +21.3 |
| /24723 Nov 2026, 15:38 UTC | 34 minutes | 32,900 → 38,800at least +5,800 | 836 → 838at most +3 | +14.2 |
| /24723 Nov 2026, 15:38 UTC | 55 minutes | 47,400 → 55,100at least +7,600 | 840 → 841at most +2 | +18.6 |
| /25096 Nov 2026, 17:27 UTC | 35 minutes | 31,500 → 36,700at least +5,100 | 65 → 66at most +2 | +12.5 |
| /25096 Nov 2026, 17:27 UTC | 35 minutes | 36,700 → 44,500at least +7,700 | 66 → 69at most +4 | +18.8 |
| /25096 Nov 2026, 17:27 UTC | 31 minutes | 44,500 → 54,700at least +10,100 | 69 → 72at most +4 | +24.7 |
| /24632 Nov 2026, 18:36 UTC | 34 minutes | 21,000 → 25,500at least +4,400 | 838 → 838at most +1 | +10.8 |
| /24632 Nov 2026, 18:36 UTC | 76 minutes | 42,100 → 48,700at least +6,500 | 844 → 844at most +1 | +15.9 |
| /24652 Nov 2026, 22:14 UTC | 76 minutes | 28,100 → 36,600at least +8,400 | 847 → 850at most +4 | +20.5 |
| /24652 Nov 2026, 22:14 UTC | 55 minutes | 50,100 → 58,600at least +8,400 | 854 → 858at most +5 | +20.5 |
| /24703 Nov 2026, 13:53 UTC | 35 minutes | 28,600 → 34,000at least +5,300 | 832 → 834at most +3 | +13.0 |
| /24703 Nov 2026, 13:53 UTC | 35 minutes | 34,000 → 41,000at least +6,900 | 834 → 835at most +2 | +16.9 |
| /239929 Oct 2026, 21:52 UTC | 4.6 hours | 85,100 → 98,800at least +13,600 | 157 → 157at most +1 | +33.2 |
| /241630 Oct 2026, 12:55 UTC | 51 minutes | 30,900 → 36,700at least +5,700 | 156 → 158at most +3 | +13.9 |
| /242030 Oct 2026, 16:09 UTC | 35 minutes | 27,100 → 31,800at least +4,600 | 48 → 49at most +2 | +11.2 |
| /242130 Oct 2026, 17:02 UTC | 35 minutes | 25,800 → 30,100at least +4,200 | 171 → 171at most +1 | +10.3 |
| /242330 Oct 2026, 18:09 UTC | 35 minutes | 14,100 → 19,300at least +5,100 | 19 → 21at most +3 | +12.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 keys clone_source · view_reaction_decoupling, last confirmed 11 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 3 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 19:00 | 1,538,632 | -9,029 |
| 9 Nov 2026, 23:11 | 1,547,661 | -672 |
| 8 Nov 2026, 15:56 | 1,548,333 | +9,541 |
| 7 Nov 2026, 08:56 | 1,538,792 | +19,501 |
| 6 Nov 2026, 09:16 | 1,519,291 | +54,567 |
| 5 Nov 2026, 09:00 | 1,464,724 | +58,316 |
| 4 Nov 2026, 10:25 | 1,406,408 | +41,626 |
| 3 Nov 2026, 07:08 | 1,364,782 | +33,707 |
| 2 Nov 2026, 04:29 | 1,331,075 | -656 |
| 1 Nov 2026, 01:10 | 1,331,731 | +84,003 |
| 30 Oct 2026, 23:16 | 1,247,728 | +77,359 |
| 29 Oct 2026, 23:46 | 1,170,369 | +77,151 |
| 29 Oct 2026, 02:57 | 1,093,218 | +83,717 |
| 27 Oct 2026, 22:49 | 1,009,501 | +15,901 |
| 27 Oct 2026, 01:58 | 993,600 | +6,550 |
| 25 Oct 2026, 23:49 | 987,050 | +7,750 |
| 25 Oct 2026, 01:20 | 979,300 | +9,125 |
| 23 Oct 2026, 23:18 | 970,175 | +7,118 |
| 23 Oct 2026, 01:36 | 963,057 | +18,640 |
| 22 Oct 2026, 02:29 | 944,417 | first reading |
273 posts held, back to 26 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 207 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 232 of 234 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 273 (26 June 2026 – 11 November 2026) |
| Views total | 19,396,567 |
| Reactions total | 69,242 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 19:50 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 2 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 146 of this channel’s own posts over the last 30 days: across 91 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 15 hours of being posted; a typical post has already reached 18.3% of its 24-hour view count within the first hour, and 52.6% within the first six; the median 24-hour reach across those posts is 68,100 views — 4.43% of this channel’s own subscriber count (90th percentile 114,000).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /253911 Nov 2026, 15:43 UTC | 817 minutes – 4.1 hours old | 18,700 views ~45 reactions | 60 minutes: 7,972 interp. → 3.0 hours: 15,500still climbing at last reading | not yet at 24h | 78 minutesprovisional — final view count still climbing |
| /253810 Nov 2026, 22:00 UTC | 295 minutes – 17 hours old | 34,200 views ~419 reactions | 60 minutes: 5,080 → 3.0 hours: 7,141 interp. → 6.0 hours: 11,400 → 12 hours: 23,600still climbing at last reading | not yet at 24h | 8.8 hoursprovisional — final view count still climbing |
| /253710 Nov 2026, 14:59 UTC | 4752 minutes – 29 hours old | 14,800 views ~170 reactions | 60 minutes: 833 interp. → 3.0 hours: 1,960 → 6.0 hours: 3,350 → 12 hours: 5,340 → 24 hours: 10,900still climbing at last reading | 10,900measured | 17 hours |
| /253610 Nov 2026, 10:56 UTC | 5334 minutes – 33 hours old | 61,400 views ~31 reactions | 60 minutes: 7,189 interp. → 3.0 hours: 13,506 interp. → 6.0 hours: 24,300 → 12 hours: 37,700 → 24 hours: 48,600still climbing at last reading | 48,600measured | 8.6 hours |
| /25359 Nov 2026, 18:34 UTC | 2815 minutes – 16 hours old | 31,500 views ~58 reactions | 60 minutes: 10,115 interp. → 3.0 hours: 17,500 → 6.0 hours: 20,300 → 12 hours: 25,200still climbing at last reading | not yet at 24h | 2.3 hoursprovisional — final view count still climbing |
| /25349 Nov 2026, 17:50 UTC | 125 minutes – 25 minutes old | 6,600 views ~9 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /25339 Nov 2026, 17:29 UTC | 8216 minutes – 2 days old | 89,400 views ~102 reactions | 60 minutes: 12,759 interp. → 3.0 hours: 24,200 → 6.0 hours: 29,300 → 12 hours: 33,100 → 24 hours: 55,700 → 2 days: 86,100still climbing at last reading | 55,700measured | 19 hours |
| /25329 Nov 2026, 11:55 UTC | 945 minutes – 4.9 hours old | 26,000 views ~247 reactions | 60 minutes: 8,826 interp. → 3.0 hours: 17,900still climbing at last reading | not yet at 24h | 1.8 hoursprovisional — 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.
71,663 reactions across 271 posts, in 8 distinct kinds. The most used accounts for 33.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23,636 | 33.0% | |
| 👍 | 21,326 | 29.8% | |
| 🔥 | 16,045 | 22.4% | |
| 🗿 | 4,625 | 6.45% | |
| 💔 | 4,121 | 5.75% | |
| custom 5834587469592400900 | 1,760 | 2.46% | |
| 👏 | 86 | 0.12% | |
| custom 5933984381600276863 | 64 | 0.089% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 271 of the 273 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 71,663 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 273 most recent posts we hold, published 26 June 2026 to 11 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: 15 of 234 posts held from the last 30 days (6.41%) 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).
✔️اشتراک تانل بخری هیچوقت قطع نمیشی‼️
🗿29❤7💔7👍2
قلب قرمز و بزن انرژی بگیریم 🫂♥️
❤363💔27🗿21👍4🔥4
کانفیگ اختصاصی رایگان ساخته شد ✅ برای استفاده از این فیلترشکن باید آخرین نسخه نپستر رو دانلود کرده باشید. 👈 آموزش اتصال برای اندروید 🤖 👈 آموزش اتصال برای آیفون 🍎 مناسب گیم 🎮| 💬 اینستاگرام و یوتیوب ▶️ @spdvpnbot ◀️
❤133💔20🔥8👍5🗿4
تخفیف ویژه رو از دست نده‼️ فیلترشکن اختصاصی خودتو بگیر دیگه قطع نشی ✅
❤27💔2🔥2
اگر رضایت داشتید میتونید سرویس اختصاصی خودتون رو تهیه کنید👇
💔28❤21🗿5👍4
😎
💔7❤2
کانفیگ اختصاصی رایگان ساخته شد ✅ برای استفاده از این فیلترشکن باید آخرین نسخه نپستر رو دانلود کرده باشید. 👈 آموزش اتصال برای اندروید 🤖 👈 آموزش اتصال برای آیفون 🍎 مناسب گیم 🎮| 💬 اینستاگرام و یوتیوب ▶️ @spdvpnbot ◀️
❤76🔥10🗿9💔7
قلب بزن انرژی بگیریم ؛ بوس بهت ❤️
❤220💔15🗿7👍4🔥1
کانفیگ اختصاصی رایگان ساخته شد ✅ برای استفاده از این فیلترشکن باید آخرین نسخه نپستر رو دانلود کرده باشید. 👈 آموزش اتصال برای اندروید 🤖 👈 آموزش اتصال برای آیفون 🍎 مناسب گیم 🎮| 💬 اینستاگرام و یوتیوب ▶️ @spdvpnbot ◀️
❤116🔥10🗿8💔4👍3
کانفیگ اختصاصی رایگان ساخته شد ✅ برای استفاده از این فیلترشکن باید آخرین نسخه نپستر رو دانلود کرده باشید. 👈 آموزش اتصال برای اندروید 🤖 👈 آموزش اتصال برای آیفون 🍎 مناسب گیم 🎮| 💬 اینستاگرام و یوتیوب ▶️ @spdvpnbot ◀️
❤194🔥11👍8🗿8💔7
کانفیگ اختصاصی رایگان ساخته شد ✅ برای استفاده از این فیلترشکن باید آخرین نسخه نپستر رو دانلود کرده باشید. 👈 آموزش اتصال برای اندروید 🤖 👈 آموزش اتصال برای آیفون 🍎 مناسب گیم 🎮| 💬 اینستاگرام و یوتیوب ▶️ @spdvpnbot ◀️
❤64🔥9👍4💔1
✔️اشتراک تانل بخری هیچوقت قطع نمیشی‼️
❤23🗿10💔5👍3
Showing the 12 most recent of 273 posts we hold for @spdnet. 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.
@spdnet edited 2 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.
We recorded 24 posts on @spdnet as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
به نظرتون تا 24 ساعت آینده جنگ میشه ؟
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
به عشق یک میلیونی شدن یک تخفیف ویژه فعال کنیم ؟
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
وضیعت اینترنتتون چطوره ؟
The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 273 most recent posts we hold, published 26 June 2026 to 11 November 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.
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.
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 11 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 10 seed channels' Telegram-generated recommendation lists in total, of which the 9 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“اینترنت آزاد | SPD Net” (@spdnet), 1,538,632 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/spdnet.
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.