Telegram RegisterThe public register of Telegram
Telegram profile photo for رقــــ 𝑨𝑳𝑯𝒂𝒚𝒂𝒉ــــآئق

Channel

رقــــ 𝑨𝑳𝑯𝒂𝒚𝒂𝒉ــــآئق

@tttffoooo

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

121subscribers

-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-1002645874045
TypeChannel
Username@tttffoooo
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/tttffoooo

Growth

121128124.57 August 2026 — 128 subscribers9 August 2026 — 128 subscribers15 August 2026 — 125 subscribers22 August 2026 — 121 subscribers7 August 202622 August 2026
4 measurements spanning 15 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 120–129 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 14:04121-4
15 Aug 2026, 17:57125-3
9 Aug 2026, 01:46128no change
7 Aug 2026, 16:56128first reading

Engagement

20 posts held, back to 28 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 22 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

36 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5262671999573977569925.0%
custom 5280569974404966639925.0%
custom 5289850733011693663719.4%
custom 5262922516426420894411.1%
custom 5958292058249631640411.1%
custom 528082686498887339425.56%
custom 594271221041227980412.78%

Custom emoji. Every 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 counts beside them areTelegram’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 9 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 36reactions 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 28 December 2025 to 22 February 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

22 Feb 2026, 12:56 UTC62 views5 reactionsread 9 August 2026

القناة ليست معي نقلت ملكيتها اذكروني بدعوة ياغالين في امان الله

custom 52898507330116936634custom 59427122104122798041

29 Dec 2025, 16:18 UTC481 views5 reactionsread 9 August 2026
Sticker

Sticker, posted without a caption

custom 52898507330116936633custom 52805699744049666392

29 Dec 2025, 16:18 UTC398 views11 reactionsread 9 August 2026

‏التغيير صعب في البداية فوضوي في الوسط ورائع في النهاية !

custom 52629225164264208944custom 59582920582496316404custom 52626719995739775693

28 Dec 2025, 23:55 UTC391 views2 reactionsread 9 August 2026

إلى اعدائي أتمنى لكم ألعز أما الذل فأنتم فيه.💋

custom 52805699744049666392

28 Dec 2025, 23:52 UTC343 views2 reactionsread 9 August 2026

*‏"يكفيك من الدنيا شخص ينتبه لصمتك أكثر من كلامك🖤."*

custom 52805699744049666392

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

“رقــــ 𝑨𝑳𝑯𝒂𝒚𝒂𝒉ــــآئق” (@tttffoooo), 121 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/tttffoooo.

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.