Telegram RegisterThe public register of Telegram

Channel

SATFEED

@satfeed

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry

1,670subscribers

+13 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001096412095
TypeChannel
Username@satfeed
CreatedBetween 1 September 2016 and 30 November 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/satfeed

Topic

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Observations

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.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@farfar25400/63769 Oct 2025, 20:20 UTC@satfeed/33606 · this entry9 Oct 2025, 20:20 UTC1.00under a minute
@farfar25400/63779 Oct 2025, 20:23 UTC@satfeed/33607 · this entry9 Oct 2025, 20:23 UTC1.00under a minute
@farfar25400/637910 Oct 2025, 10:33 UTC@satfeed/33613 · this entry10 Oct 2025, 10:33 UTC1.00under a minute
@satfeed/33614 · this entry10 Oct 2025, 10:43 UTC@farfar25400/638010 Oct 2025, 10:43 UTC1.00under a minute
@satfeed/33616 · this entry10 Oct 2025, 12:46 UTC@farfar25400/638210 Oct 2025, 12:46 UTC1.00under a minute
@farfar25400/638410 Oct 2025, 13:24 UTC@satfeed/33618 · this entry10 Oct 2025, 13:24 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@farfar2540016 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (106)

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. None of the 6 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 9 October 2025 to 10 October 2025. 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @farfar25400. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.

Growth

1,6541,6701,6626 August 2026 — 1,657 subscribers6 August 2026 — 1,657 subscribers6 August 2026 — 1,654 subscribers10 August 2026 — 1,670 subscribers6 August 202610 August 2026
4 measurements spanning 4 days, net +13. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,652–1,672 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 03:561,670+16
6 Aug 2026, 19:001,654-3
6 Aug 2026, 07:181,657no change
6 Aug 2026, 01:121,657first reading

Engagement

18 posts held, back to 9 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.66%
avg views ÷ 1,670 subscribers
Avg views / post
128
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 18 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held18 (9 October 20257 August 2026)
Views total128
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:52 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.

Recent posts

10 Oct 2025, 14:47 UTC≈1,990 viewsread 7 August 2026
Photo

⚽ فید فوتبال – FIFA International Friendly Match 2025 (Tunisia vs Libya) رویداد: دیدار دوستانه ملی فوتبال ۲۰۲۵ – تونس 🇹🇳 در برابر لیبی 🇱🇾 📺 البث المباشر – مباراة ودية دولية لكرة القدم 2025 – تونس ضد ليبيا 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 11079 H 7199 (DVB-S2) 📺 M209-LIB003-M | BISS 🔑 BISS Key: 0F 23 6E A0 42 0B 99 E6 📶 SNR: 11.3 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 14:44 UTC≈1,600 viewsread 7 August 2026
Photo

🏀 فید بسکتبال – FIBA 3x3 World Tour 2025 (Serbia – Čačak) رویداد: تور جهانی بسکتبال سه‌نفره ۲۰۲۵ – صربستان، شهر چاچاک 📺 البث المباشر – الجولة العالمية لكرة السلة 3x3 لعام 2025 – صربيا، تشاتشاك 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 12633 V 4936 (DVB-S2) 📺 YSM-016-1 | BISS 🔑 BISS Key: AB BA 20 85 25 20 26 6B 📶 SNR: 11.3 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 14:29 UTC≈1,120 viewsread 7 August 2026
Photo

⚽ فید فوتبال – AFC Asian Qualifiers (Road to 2026 World Cup) رویداد: مقدماتی جام جهانی ۲۰۲۶ – عراق 🇮🇶 در برابر اندونزی 🇮🇩 📺 البث المباشر – تصفيات كأس العالم 2026 – العراق ضد إندونيسيا 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 11000 V 14396 (DVB-S2) 📺 CYP-005_PATH1 | BISS 🔑 BISS Key: 09 F8 B6 B7 AC 8F 10 4B 📶 SNR: 9.9 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 13:37 UTC879 viewsread 7 August 2026
Photo

⛳ فید گلف – Open de España Madrid 2025 (DP World Tour) رویداد: مسابقات آزاد گلف اسپانیا ۲۰۲۵ – مادرید (مرحله DP World Tour) 📺 البث المباشر – بطولة إسبانيا المفتوحة للجولف 2025 – مدريد 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 12727 V 7198 (DVB-S2) 📺 LAT-002 | BISS 🔑 BISS Key: AA C2 2B 97 52 A5 2B 22 📶 SNR: 10.9 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 13:34 UTC574 viewsread 7 August 2026
Photo

🏸 فید بدمینتون – YONEX SUNRISE BWF World Junior Championships 2025 رویداد: نیمه‌نهایی مسابقات بدمینتون قهرمانی جوانان جهان ۲۰۲۵ – ژاپن 🇯🇵 در برابر چین 🇨🇳 📺 البث المباشر – نصف النهائي من بطولة العالم للشباب للريشة الطائرة 2025 – اليابان ضد الصين 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 12677 H 7199 (DVB-S2) 📺 WF A - C1 BISS 1 | BISS 🔑 BISS Key: 17 1F 8A C0 31 32 5D C0 📶 SNR: 13.0 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 13:31 UTC474 viewsread 7 August 2026
Photo

🐎 فید پرش با اسب – Longines Global Champions Tour 2025 (Rome, Italy) رویداد: مرحله رم از تور جهانی پرش با اسب لونژینز ۲۰۲۵ – ایتالیا 📺 البث المباشر – بطولة لونجين العالمية لقفز الحواجز 2025 – روما (إيطاليا) 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 12641 H 9598 (DVB-S2) 📺 SUI 067 | BISS 🔑 BISS Key: B8 0D 7C 41 8E F9 5E E5 📶 SNR: 11.4 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 13:29 UTC401 viewsread 7 August 2026
Photo

🏁 فید مسابقات اتومبیل‌رانی – FIA Extreme H World Cup 2025 (Round Saudi Arabia) رویداد: مرحله نیمه‌نهایی مسابقات جهانی اتومبیل‌رانی Extreme H – عربستان سعودی ۲۰۲۵ 📺 البث المباشر – كأس العالم للرالي الكهربائي Extreme H في المملكة العربية السعودية 2025 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 12573 H 7199 (DVB-S2) 📺 SAU-033-A | BISS 🔑 BISS Key: 11 ED D7 D5 73 58 41 0C 📶 SNR: 12.3 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 13:24 UTC335 viewsread 7 August 2026
Photo

🏍️ فید مسابقات موتورسواران – World Superbike Championship 2025 (WSBK Estoril) رویداد: مسابقه جهانی سوپربایک در استوریل، پرتغال ۲۰۲۵ 📺 البث المباشر – بطولة العالم للدراجات النارية سوبر بايك 2025 في استوريل (البرتغال) 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 12524 V 9873 (DVB-S2) 📺 WSBK ESTORIL | BISS 🔑 BISS Key: BA 23 AC 89 11 CA 12 ED 📶 SNR: 11.7 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 12:53 UTC315 viewsread 7 August 2026
Photo

🏀 فید بسکتبال – NBA China Games 2025 رویداد: بازی‌های بسکتبال NBA در چین ۲۰۲۵ – بروکلین نتس در برابر فینیکس سانز 📺 البث المباشر – مباريات NBA الصين 2025 (بروكلين نتس ضد فينيكس صنز) 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 11106 H 7199 (DVB-S2) 📺 E-285 via MAI | BISS 🔑 BISS Key: 7E C1 06 45 2A 5B 25 AA 📶 SNR: 10.1 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 12:46 UTC281 viewsread 7 August 2026
Photo

🎉 فید مراسم – افتتاحیه فصل ریاض ۲۰۲۵ (Riyadh Season Opening Ceremony 2025) رویداد: مراسم رسمی افتتاح فصل تفریحی ریاض ۲۰۲۵ 📺 البث المباشر – حفل افتتاح موسم الرياض 2025 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 12564 H 7199 (DVB-S2) 📺 E-296 MAIN | BISS 🔑 BISS Key: 7A 32 BA 66 18 10 10 38 📶 SNR: 13.0 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

10 Oct 2025, 12:41 UTC257 viewsread 7 August 2026
Photo

🥊 فید هنرهای رزمی ترکیبی – ONE Championship 2025 رویداد: ONE Fight Night 2025 📺 البث المباشر – بطولة ون للقتال الليلة 2025 📡 مشخصات فید: 🛰️ Eutelsat 7AB (7°E) 📡 12677 V 7119 (DVB-S2) 📺 EDM HD ENC-1 | BISS 🔑 BISS Key: A1 B4 C2 17 D5 E3 F6 AE 📶 SNR: 11.6 dB ارائه‌شده توسط: @nazz551

Signed میکاییل

Showing the 12 most recent of 18 posts we hold for @satfeed. 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.

Cite this entry

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“SATFEED” (@satfeed), 1,670 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/satfeed.

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.