Telegram RegisterThe public register of Telegram
Telegram profile photo for ﮼فطم 🪷

Channel

﮼فطم 🪷

@ri2es

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

219subscribers

-7 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001401710795
TypeChannel
Username@ri2es
CreatedBetween 1 December 2018 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/ri2es

Topic

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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.

Growth

219228223.57 August 2026 — 226 subscribers7 August 2026 — 226 subscribers14 August 2026 — 228 subscribers21 August 2026 — 226 subscribers28 August 2026 — 224 subscribers7 September 2026 — 222 subscribers14 September 2026 — 221 subscribers7 October 2026 — 219 subscribers7 August 20267 October 2026
8 measurements spanning 62 days, net -7. 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 218–229 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 23:20219-2
14 Sept 2026, 11:55221-1
7 Sept 2026, 14:19222-2
28 Aug 2026, 21:58224-2
21 Aug 2026, 17:08226-2
14 Aug 2026, 17:25228+2
7 Aug 2026, 04:32226no change
7 Aug 2026, 04:28226first reading

Engagement

20 posts held, back to 8 April 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 20 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1,142 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 77.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘89077.9%
🍓23420.5%
custom 521793456365688955370.613%
custom 600361830841319780960.525%
custom 527873100684775656730.263%
custom 583021207044384836520.175%

Custom emoji. 4 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 20 of the 20 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 1,142 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 8 April 2026 to 1 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.

Recent posts

1 Aug 2026, 10:31 UTC34 views2 reactionsread 7 August 2026

يتم حذف التلي

custom 52179345636568895531custom 60036183084131978091

Signed ﮼فـاتـي ❣️

27 Jul 2026, 15:23 UTC638 views11 reactionsread 7 August 2026

- المُـغادرة هي عتابي الوحـيـد 🤎.

custom 52179345636568895533custom 60036183084131978093🍓2custom 58302120704438483652custom 52787310068477565671

Signed ﮼فـاتـي ❣️

10 Jul 2026, 23:44 UTC≈1,100 views7 reactionsread 7 August 2026

وشلي بغيرك انتَ ؟ والگة مثلك وين ♥️

💘3🍓2custom 52787310068477565672

Signed ﮼فـاتـي ❣️

10 Jul 2026, 23:44 UTC≈1,100 views6 reactionsread 7 August 2026

الما يشبهونج شگلهم ؟ هيَ حيرة كل بعيد بعيني يصغر وانت بعيوني چبيرة

🍓2💘2custom 60036183084131978092

Signed ﮼فـاتـي ❣️

10 Jul 2026, 23:43 UTC≈1,150 views6 reactionsread 7 August 2026

لا تضّن وانتَ بعيد تنساني وانسِاك تابع خيالك زين ، تلگاني وياك .

🍓2💘2custom 52179345636568895532

Signed ﮼فـاتـي ❣️

3 Jul 2026, 10:30 UTC≈1,230 views128 reactionsread 7 August 2026

واذا نتلاكة صدفة وتبتسم وياي ارد مثل اليزور وحصّل مراده

💘122🍓5custom 52179345636568895531

Signed ﮼فـاتـي ❣️

3 Jun 2026, 20:03 UTC≈1,410 views63 reactionsread 7 August 2026

أشهد أنَ عَلُياًّ وَليُ ألله شَهد بِها دَمي وَعَظمي وقَلبي وعَقلي كَفني ولِحد قَبري وحتى ألقى بِها رَبي .

💘59🍓4

Signed ﮼فـاتـي ❣️

3 Jun 2026, 20:01 UTC≈1,500 views127 reactionsread 7 August 2026
Photo

صـَوتُ السَماء يَعتَلي قد تَوج الله عـَلي 🤍.

💘124🍓3

Signed ﮼فـاتـي ❣️

25 May 2026, 22:14 UTC≈1,530 views89 reactionsread 7 August 2026
File

File, posted without a caption

🍓87💘2

Signed ﮼فـاتـي ❣️

22 May 2026, 20:49 UTC≈1,710 views62 reactionsread 7 August 2026

حُبِ عَلّي يَمحو ألخَطايا 🩶.

💘58🍓4

Signed ﮼فـاتـي ❣️

16 May 2026, 08:06 UTC≈1,970 views63 reactionsread 7 August 2026

سِمسِمَه ياگمره‍ اليرسِم سِما ياغيمَه بَس مو مِن مُطر ذوبيّلي يا لَطخه شَكر يـَ مكيجهه خُدود السّما يانكهه الحُب الصّدگ بوجهِج خَجل غُصن العِثگ مو مِن ثَمر دنگ عشگ يا غاليه وجيتيّ بغَفل غالي الـ يجي بُمو موسِمه بِلا قاضي داخل محكَمة رُوحي بريئَه ومُجرِمه والما يُحط حَد للجَرح بَس موتَه يُصبح بلسَمه .

💘59🍓4

Signed M

14 May 2026, 23:55 UTC≈1,860 views137 reactionsread 7 August 2026

﴿ وٌيَنِصّرکْمً آلَلَهّ فُلَآ غُآلَبً لَکْمً ﴾

💘136🍓1

Showing the 12 most recent of 20 posts we hold for @ri2es. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“﮼فطم 🪷” (@ri2es), 219 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/ri2es.

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.