Channel
@rafidit_313
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
385subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001551838545 |
|---|---|
| Type | Channel |
| Username | @rafidit_313 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/rafidit_313 |
Religion — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 13 Sept 2026, 09:16 | 385 | +1 |
| 5 Sept 2026, 11:59 | 384 | +1 |
| 21 Aug 2026, 20:34 | 383 | -3 |
| 15 Aug 2026, 16:57 | 386 | -3 |
| 8 Aug 2026, 06:02 | 389 | no change |
| 7 Aug 2026, 09:27 | 389 | first reading |
18 posts held, back to 4 August 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 1 page 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 18 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 12 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.
57 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 29.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17 | 29.8% | |
| ❤ | 15 | 26.3% | |
| 😢 | 10 | 17.5% | |
| 💯 | 5 | 8.77% | |
| custom 5456183868514129854 | 3 | 5.26% | |
| 💔 | 3 | 5.26% | |
| 🙏 | 2 | 3.51% | |
| 🤯 | 2 | 3.51% |
Custom emoji. One row above is a 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 count beside it is 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 13 of the 18 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 57 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 4 August 2026 to 6 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.
Имам Садик ع сказал: «Провести одну ночь возле (могилы) Али ع— равноценно поклонению в течение 700 лет. А провести одну ночь возле (могилы) Хусейна ع— равноценно поклонению в течение 70 лет. Молитва возле (могилы) Али ع равна по награде 200 000 молитв». Аш-Ша‘аир аль-Хусейнийя, т. 3, стр. 62 Рафидит
❤8
روى الشيخ أبو محمد الحسن بن محمد بن نصر يرفع الحديث برجاله إلى محمد بن جعفر البرسي، عن إبراهيم بن محمد الموصلي، عن جابر الجعفي. قال الأمام الباقر صلوات الله عليه: يا جابر، إنا أهل البيت لا يقاس بنا أحد، من قاس بنا أحدا من البشر فقد كفر. يا جابر، بنا الله أنقذكم، وبنا هداكم، ونحن والله دللناكم على ربكم Шейх Абу Мухаммад Хасан бин Мухаммад бин Наср передал от Мухаммада бин Джафара Аль-Барси, от Ибрахима бин Мухаммада …
👍8
Кафир, Еврейская потаскуха!
🤯2
Что за ящер в белой шляпе)
Проклятая секта рахбаритов!
❤2
Это история о противостоянии абсолютного добра и абсолютного зла. Когда Имам Хусейн (мир ему) отказался присягнуть на верность Язиду, Язид отправил против него своё войско. Имам Хусейн (мир ему) не стремился к войне. Его лагерь был окружён, а доступ к воде для его семьи и сподвижников был перекрыт. Все страдали от мучительной жажды, особенно дети. Хазрат Аббас (мир ему) направился к вражеским рядам, чтобы принести …
😢3
Photo, posted without a caption
Мое сердце ♥️
💔3
«Приемлемо ли такое поведение перед Имамом Хусейном (а)?! Эта музыка не соответствует атмосфере скорби и траура в дни Арбаина, не говоря уже о том, что она является запретной (харам).» Вот такие вот песеньки от Иранцев)
custom 54561838685141298543
Наверное, сам актёр даже не знает, что он, оказывается, на стороне Трампа. 😁
))
Вчера произошел очередной позорный инцидент между рахбаритами, широзитами и сторонниками Муктады Садра. Мукаллиды начали пожирать друг друга, защищая своих лидеров, своих идолов и свои политические культы. Каждый готов оправдать любую ложь, любую агрессию и любое унижение ради своего шейха или вождя)) Разве этому учили Имамы Ахль аль-Бейт (а)? Разве они призывали к тому, чтобы мусульмане превращали религию в арену ф…
👍5❤2
Showing the 12 most recent of 18 posts we hold for @rafidit_313. 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.
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 1 seed channel's Telegram-generated recommendation list 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Рафидит” (@rafidit_313), 385 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/rafidit_313.
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.