Channel
@fadieseed
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
43,936subscribers
-1,919 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001533112562 |
|---|---|
| Type | Channel |
| Username | @fadieseed |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/fadieseed |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 01:37 | 43,936 | -300 |
| 17 Sept 2026, 05:20 | 44,236 | -103 |
| 15 Sept 2026, 04:00 | 44,339 | -82 |
| 13 Sept 2026, 12:19 | 44,421 | -105 |
| 11 Sept 2026, 14:00 | 44,526 | -102 |
| 8 Sept 2026, 22:18 | 44,628 | -182 |
| 5 Sept 2026, 18:37 | 44,810 | -76 |
| 3 Sept 2026, 20:20 | 44,886 | -79 |
| 2 Sept 2026, 12:48 | 44,965 | -39 |
| 1 Sept 2026, 10:05 | 45,004 | -54 |
| 31 Aug 2026, 09:53 | 45,058 | -52 |
| 30 Aug 2026, 09:03 | 45,110 | -68 |
| 29 Aug 2026, 06:35 | 45,178 | -43 |
| 28 Aug 2026, 09:03 | 45,221 | -36 |
| 27 Aug 2026, 06:13 | 45,257 | -53 |
| 26 Aug 2026, 02:58 | 45,310 | -51 |
| 25 Aug 2026, 00:44 | 45,361 | -76 |
| 23 Aug 2026, 14:47 | 45,437 | -99 |
| 22 Aug 2026, 00:57 | 45,536 | -46 |
| 20 Aug 2026, 18:44 | 45,582 | first reading |
2 posts held, back to 12 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 85 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 30 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
14 reactions across 1 post, in 7 distinct kinds. The most used accounts for 21.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 21.4% | |
| ❤🔥 | 2 | 14.3% | |
| 👍 | 2 | 14.3% | |
| 👏 | 2 | 14.3% | |
| 🔥 | 2 | 14.3% | |
| 🥰 | 2 | 14.3% | |
| 💯 | 1 | 7.14% |
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 of the 2 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 2 most recent posts we hold, published 12 August 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.
💎يعطيكم الف عافية جميعا ، هذه القناة عم أواجه فيها بعض المشاكل لذلك مختصر الحديث رح نرجع لقناتنا الأولى ، الي حابب يبقى معنا حياه الله ، جميع شغلي رح يكون على القناة الأولى 📢احتمال جداً كبير يتم بيع هذه القناة القناة المعتمدة ⬇️ https://t.me/Faditraderr
❤3❤🔥2👍2👏2🔥2🥰2💯1
Channel photo removed
Showing the 2 most recent of 2 posts we hold for @fadieseed. 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.
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.
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 27 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 16 seed channels' Telegram-generated recommendation lists in total. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Faditrader” (@fadieseed), 43,936 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/fadieseed.
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.