#شبتون_خوش_تاجیا 💙🤞 🌟@Zapas_havadaran🌟
❤🔥27👎2
Signed Mohammad Mahdi 🖐🏻

Channel
@ss_2e
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
2,214,830subscribers
+293,924 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001942350755 |
|---|---|
| Type | Channel |
| Username | @ss_2e |
| Description | بزرگترین رسانه هوادارن ارتش آبی💙🔥👑 تبلیغات 👇 @meyssk 🏆 هفته اول لیگ برتر 🔵 استقلال 🟡 مس شهربابک 🗓 جمعه ۲۳ مرداد ⏰ ساعت ۱۹:۳۰ 🏟 ورزشگاه شهر قدس 🖥 شبکه سه |
| Created | 24 March 2023 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/ss_2e |
Sports — 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 99% 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.
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 word for word on 12 other registered channels. They sit inside a group of 464 channels that share the same post bodies 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 |
|---|---|---|---|
| @ss_2e/27956 · this entry29 May 2025, 19:21 UTC | @es_qb/19117429 May 2025, 19:27 UTC | 1.00 | 7 minutes |
| @es_qb/20265929 Aug 2025, 08:40 UTC | @ss_2e/40549 · this entry29 Aug 2025, 08:53 UTC | 1.00 | 13 minutes |
| @ss_2e/57673 · this entry28 Dec 2025, 16:02 UTC | @es_qb/21737528 Dec 2025, 16:02 UTC | 1.00 | under a minute |
| @es_qb/2183505 Jan 2026, 22:27 UTC | @ss_2e/58660 · this entry5 Jan 2026, 22:27 UTC | 1.00 | under a minute |
| @ss_2e/62131 · this entry9 Mar 2026, 14:33 UTC | @es_qb/2215679 Mar 2026, 14:33 UTC | 1.00 | under a minute |
| @ss_2e/62910 · this entry12 Apr 2026, 18:25 UTC | @es_qb/22247912 Apr 2026, 18:25 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @es_qb | 4,053 (8/8 hand-verifiable sample passed) | 0.99 | 3 minutes | @es_qb (2,510–1,543) |
| @km_ap | 993 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @km_ap (690–303) |
| @esteghlalfan | 852 (8/8 hand-verifiable sample passed) | 0.95 | 47 minutes | this entry (511–341) |
| @ga_os | 631 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @ga_os (399–232) |
| @se_pz | 589 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @se_pz (451–138) |
| @ir_b0 | 531 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (287–244) |
| @ba_z1 | 354 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @ba_z1 (204–150) |
| @fo_rk | 67 (8/8 hand-verifiable sample passed) | 0.97 | 8.4 hours | @fo_rk (46–21) |
| @khabarfouri | 65 (8/8 hand-verifiable sample passed) | 0.95 | 23 minutes | this entry (34–31) |
| @ne_wg | 61 (8/8 hand-verifiable sample passed) | 0.97 | 14 hours | @ne_wg (36–25) |
| @Perspolisirfans | 53 (8/8 hand-verifiable sample passed) | 0.98 | 2.3 hours | @Perspolisirfans (27–26) |
| @khabari | 48 (8/8 hand-verifiable sample passed) | 0.95 | 20 minutes | this entry (28–20) |
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. 8 of the 5,222 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 20,231 comparable posts for this entry, running 31 July 2024 to 7 August 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.
Across the whole group of 464, the earliest publisher we hold is @akharinkhabar. That is a statement about our reading window, not a claim of authorship.
On 36 of the 391 posts we watched over 30days, 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.0104 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /694326 Aug 2026, 15:51 UTC | 18 minutes | 3,130 → 4,640at least +1,500 | 43 → 45at most +3 | +15.6 |
| /694326 Aug 2026, 15:51 UTC | 1.6 hours | 5,260 → 8,090at least +2,820 | 46 → 52at most +7 | +29.3 |
| /694876 Aug 2026, 21:02 UTC | 11 minutes | 3,750 → 5,650at least +1,890 | 41 → 43at most +3 | +19.6 |
| /694876 Aug 2026, 21:02 UTC | 18 minutes | 5,880 → 7,370at least +1,480 | 51 → 51at most +1 | +15.4 |
| /696389 Aug 2026, 14:22 UTC | 35 minutes | 6,860 → 15,100at least +8,140 | 82 → 85at most +4 | +84.6 |
| /696389 Aug 2026, 14:22 UTC | 35 minutes | 15,100 → 25,000at least +9,800 | 85 → 94at most +10 | +101.8 |
| /6980611 Aug 2026, 19:59 UTC | 35 minutes | 3,350 → 5,220at least +1,860 | 46 → 47at most +2 | +19.3 |
| /6980611 Aug 2026, 19:59 UTC | 30 minutes | 5,990 → 8,040at least +2,040 | 54 → 56at most +3 | +21.2 |
| /694316 Aug 2026, 15:41 UTC | 21 minutes | 5,840 → 7,360at least +1,510 | 37 → 38at most +2 | +15.7 |
| /694816 Aug 2026, 19:41 UTC | 10 minutes | 5,620 → 6,680at least +1,050 | 129 → 130at most +2 | +10.9 |
| /694846 Aug 2026, 20:11 UTC | 10 minutes | 5,580 → 6,890at least +1,300 | 41 → 42at most +2 | +13.5 |
| /695297 Aug 2026, 16:03 UTC | 17 minutes | 5,070 → 7,470at least +2,390 | 30 → 31at most +2 | +24.8 |
| /695327 Aug 2026, 16:57 UTC | 17 minutes | 2,710 → 5,370at least +2,650 | 62 → 65at most +4 | +27.5 |
| /695457 Aug 2026, 20:16 UTC | 35 minutes | 5,990 → 8,400at least +2,400 | 176 → 180at most +5 | +24.9 |
Expectedis 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 12 August 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’s posts match, word for word or near enough, posts on 463 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
413 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 00:23 | 2,214,830 | -5,596 |
| 10 Aug 2026, 21:21 | 2,220,426 | -17,379 |
| 10 Aug 2026, 00:28 | 2,237,805 | -15,612 |
| 8 Aug 2026, 23:51 | 2,253,417 | -11,408 |
| 7 Aug 2026, 20:16 | 2,264,825 | +39,053 |
| 6 Aug 2026, 22:20 | 2,225,772 | +304,866 |
| 6 Aug 2026, 01:31 | 1,920,906 | first reading |
53,420 posts held, back to 24 March 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 6,754 pagesof 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 1,635 of 1,657 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 53,420 (24 March 2023 – 12 August 2026) |
| Views total | 18,948,081 |
| Reactions total | 186,842 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 23:41 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 12 August 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 29 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 392 of this channel’s own posts over the last 30 days (26 of the 24-hour readings behind this are interpolated, not measured directly): across 310of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 50 minutes of being posted; a typical post has already reached 57.6% of its 24-hour view count within the first hour, and 90.2% within the first six; the median 24-hour reach across those posts is 9,380 views — 0.424% of this channel’s own subscriber count (90th percentile 11,900).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /6986012 Aug 2026, 21:20 UTC | 57 minutes – 2.4 hours old | 7,500 views ~29 reactions | 60 minutes: 4,895 interp.still climbing at last reading | not yet at 24h | 52 minutesprovisional — final view count still climbing |
| /6985912 Aug 2026, 20:35 UTC | 620 minutes – 3.1 hours old | 8,920 views ~47 reactions | 60 minutes: 4,736 interp. → 3.0 hours: 8,920still climbing at last reading | not yet at 24h | 41 minutesprovisional — final view count still climbing |
| /6985812 Aug 2026, 20:24 UTC | 632 minutes – 3.3 hours old | 7,650 views ~96 reactions | 60 minutes: 3,300 → 3.0 hours: 7,611 interp.still climbing at last reading | not yet at 24h | 1.6 hoursprovisional — final view count still climbing |
| /6985712 Aug 2026, 20:16 UTC | 74 minutes – 3.4 hours old | 7,880 views ~74 reactions | 60 minutes: 3,483 interp. → 3.0 hours: 7,831 interp.still climbing at last reading | not yet at 24h | 79 minutesprovisional — final view count still climbing |
| /6985612 Aug 2026, 20:05 UTC | 715 minutes – 3.6 hours old | 7,840 views ~61 reactions | 60 minutes: 3,214 interp. → 3.0 hours: 7,780still climbing at last reading | not yet at 24h | 1.5 hoursprovisional — final view count still climbing |
| /6985512 Aug 2026, 19:45 UTC | 85 minutes – 3.9 hours old | 6,440 views ~41 reactions | 60 minutes: 4,798 interp. → 3.0 hours: 6,334 interp.still climbing at last reading | not yet at 24h | 43 minutesprovisional — final view count still climbing |
| /6985412 Aug 2026, 19:36 UTC | 815 minutes – 4.1 hours old | 8,740 views ~69 reactions | 60 minutes: 4,066 interp. → 3.0 hours: 8,620still climbing at last reading | not yet at 24h | 65 minutesprovisional — final view count still climbing |
| /6985312 Aug 2026, 19:05 UTC | 911 minutes – 4.6 hours old | 49,500 views ~67 reactions | 60 minutes: 21,813 interp. → 3.0 hours: 40,900still climbing at last reading | not yet at 24h | 72 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 viewsis 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.
47,281 reactions across 405 posts, in 28 distinct kinds. The most used accounts for 37.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17,921 | 37.9% | |
| 🔥 | 10,373 | 21.9% | |
| 😁 | 5,776 | 12.2% | |
| 👎 | 3,622 | 7.66% | |
| ❤🔥 | 3,027 | 6.40% | |
| 🤬 | 2,576 | 5.45% | |
| 💔 | 1,625 | 3.44% | |
| 🤯 | 520 | 1.10% | |
| 🥰 | 386 | 0.816% | |
| 😐 | 369 | 0.78% | |
| 😭 | 222 | 0.47% | |
| 💯 | 193 | 0.408% | |
| 🤔 | 149 | 0.315% | |
| 🗿 | 141 | 0.298% | |
| 🤩 | 104 | 0.22% | |
| 👏 | 96 | 0.203% | |
| 🥴 | 84 | 0.178% | |
| 👌 | 35 | 0.074% | |
| 😍 | 14 | 0.03% | |
| 🥱 | 9 | 0.019% | |
| 8 further kinds | 39 | 0.082% |
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 985 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 124,889reactions 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 24 July 2026 to 12 August 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.
#شبتون_خوش_تاجیا 💙🤞 🌟@Zapas_havadaran🌟
❤🔥27👎2
Signed Mohammad Mahdi 🖐🏻
لیگ شروع شده اینا تازه یادشون افتاده کادر فنی وتقویت کنن پنجره که بسته بود و نقل و انتقالات خرجی نکردن کادر فنی هم که تقویت نکردن دقیقا دارن چیکار میکنن تاجرنیا انگار یادش رفته نخبگان بازی داریم ن محلات چنین وضعیتی حتی در دوران سلطانی فر هم کم سابقه بوده کاری که تاجرنیا با استقلال کرد سلطانی فر نکرد لعنت بر مدیران خائن 🌟@Zapas_havadaran🌟
👍45😭2
Signed ⓡᵃĤ𝐀
🚨 حضور مربی اسپانیایی در استقلال منتفی شد 🔹حضور خواکین گیل، مربی اسپانیایی مدنظر استقلال برای حضور در کادر فنی، منتفی شده و مدیران این باشگاه اکنون با یک مربی کروات برای حضور در کادر سهراب بختیاریزاده مذاکره میکنند/ ایسنا 🌟@Zapas_havadaran🌟
🤬75😐11👎3👍2💯2🥰2😁1
Signed ⓡᵃĤ𝐀
آوای استقلال: ماشاریپوف چون فقط به دلایل پزشکی فصل پیش از لیست استقلال کنار نرفته بود، از لحاظ حقوقی مشکلی بابت بازی برای استقلال نداره 🌟@Zapas_havadaran🌟
👍72💯2
Signed ⓡᵃĤ𝐀
مطالبات فصل گذشته آنتونیو آدان به طور کامل پرداخت شد. قرار است این دروازهبان اسپانیایی بهزودی وارد ایران میشود تا در جلسات با مدیران باشگاه درباره ادامه همکاری و مبلغ قرارداد فصل جدید مذاکره کند/ ایسنا 🌟@Zapas_havadaran🌟
👎35👍23🔥1🗿1🤯1
Signed ⓡᵃĤ𝐀
استقلال تا الان یک میلیون و ۴۰۰ هزار یورو به نازون داده که ۱۱۰ هزار تاش واسه ایجنت ها بوده! قرارداد سال دوم نازون هم یک میلیون و ۴۰۰ هزار تاس که ۴۰۰ هزار تاش پیش پرداخت باید بهش داده بشه. نازون میگه از فصل پیش ۲۰۰ هزار تا هم طلب دارم و ۴۰۰ تا پیش پرداختم رو برای فصل بعد بدید تا بیام؛ استقلال هم میگه فصل پیش لیگ نیمه تمام مونده و چیزی نباید بهت بدیم و این باعث شده فعلا استقلال و نازون تو بلاتکلیفی باشن!/فارس 🌟@Zapa…
🔥31🤯6😁3👍1
Signed ⓡᵃĤ𝐀
🏆ترکیب ۴ تا تیم مدعی این فصل لیگ ایران 🌟@Zapas_havadaran🌟
🤬55🔥9👍2👏1💯1😍1
Signed ⓡᵃĤ𝐀
تو این وضعیت بد اقتصادی تو این شرایط مردم و تورم قیمت بلیت های روبه رو جایگاه ۳۰۰ هزار تومن قیمت بلیت های وی آی پی ۷۰۰ هزار تومن؟؟ چه خبره تونه آخه ورزشگاه آزادی هم نیست که بگیم حداقل ورزشگاه درست حسابی بازی قراره برگزار بشه برای ورزشگاه قدس ۳۰۰ هزار تومن پول بلیت؟ ✅امیدوارم از بازی با سپاهان قیمت بلیت ها کاهش پیدا کنه تا هواداران با شرایطی راحت تر بتونن خودشون برای حمایت تیم محبوب شون به ورزشگاه برسونن💙💙 🌟@Zap…
👍54🤬8👎2👏1💯1🔥1
Signed Mohammad Mahdi 🖐🏻
آخرین باری که بیژن حیدری دیدار تیم حکومتی رو سوت زد بازی برابر تراکتور در جام حذفی بود که این گل خطای آشکار رو با وجود VAR در دقیقه ۹۶ قبول کرد. 🌟@Zapas_havadaran🌟
👍42👎2
Signed ⓡᵃĤ𝐀
《وبشرالصابرین الذین اذا اصابتهم مصیبه قالو انالله و انا الیه راجعون》 خانواده محترم: #رضایی با نهایت تاثر و تاسف درگذشت همکار محترم خانم سودا[اعظم رضایی] :را تسلیت عرض نموده و از درگاه خداوند منان برای آن عزیزان سفرکرده علو درجات و برای سایر بازماندگان صبر جمیل و اجر جزیل مسئلت دارم ازطرف : #مدیرت محترم رسانه مربوطه 🌟@Zapas_havadaran🌟
💔46👏2🔥1🗿1🥰1😁1
🔵🔴✔️زمان دربی پایتخت مشخص شد 🔺بر اساس اعلام امیرحسین روشنک مسئول کمیته مسابقات سازمان لیگ، داربی پایتخت از هفته پنجم لیگ برتر فوتبال ایران، ۱۱ یا ۱۲ شهریور برگزار خواهد شد. 🔺هنوز ورزشگاه میزبان مشخص نشده است. 🌟@Zapas_havadaran🌟
👎15💯4👍1
⭕️⭕️ 🕛🕛 ⭕️⭕️ از بی پولی خسته شدی؟ دنبال درآمد بالا ⬆️🔝⬆️ هستی؟ شاید دیدن این ویدیو زندگیت رو تغییر بده! پس روی این لینک ضربه بزن 📱 کـانـال تـلـگـرام 👇👇👇 🆔 @Kingofdarkesm 🚨💝 مـشـاوره و ثـبـت سـفـارش ✅ 👩🏻💻@BlackpnatherXm2 🛑 👧 از این پیام، ساده رد نشو !! شاید تنها فرصت طلایی 🎁 زندگیت باشه ! 1️⃣4️⃣0️⃣5️⃣❗️5️⃣❗️2️⃣1️⃣
Showing the 12 most recent of 53,420 posts we hold for @ss_2e. 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.
@ss_2e 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.
Citation-graph rank — 467,723 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
@ss_2e named 77 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.
27 more handles are in this same list but not shown individually here — capped at 50.
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 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
132 domainsthis 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.
1 of 132 shown as text only, not a link. The exact host, not merely a domain it shares a registrable root with, matches a threat-intelligence blocklist this register already checks elsewhere (see methodology) — the link still appearing in a post is still a measured fact and is still shown, but no anchor is rendered here, so no click and no link equity passes to it from this page.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“کانال هواداران ارتش آبی استقلال” (@ss_2e), 2,214,830 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ss_2e.
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.