Telegram RegisterThe public register of Telegram
Telegram profile photo for لـِ ࢪاء ࠝ.

Channel

لـِ ࢪاء ࠝ.

@rama_133

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

1,609subscribers

+61 since we began measuring on 1 September 2026

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

Register entry

Telegram ID-1003072024891
TypeChannel
Username@rama_133
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live2 September 2026
Measurements held2
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/rama_133

Growth

1,5481,6091,578.51 Sept 2026, 12:30 — 1,548 subscribers2 Sept 2026, 12:04 — 1,609 subscribers1 Sept 2026, 12:302 Sept 2026, 12:04
2 measurements taken within a single day, net +61. 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,539–1,618 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 12:041,609+61
1 Sept 2026, 12:301,548first reading

Engagement

20 posts held, back to 14 August 2026the 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.

ERR · 30 days
51.8%
avg views ÷ 1,609 subscribers
Avg views / post
833
20 posts measured
Reaction rate
15.0%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 18 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held20 (14 August 20261 September 2026)
Views total16,669
Reactions total2,506
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Sept 2026, 12:30 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.

Reaction mix

2,506 reactions across 18 posts, in 13 distinct kinds. The most used accounts for 28.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 526742304944714175571928.7%
custom 539541675565491617433013.2%
custom 593805040566456250525810.3%
custom 54408375380486817871877.46%
custom 52692348942858598671756.98%
custom 60015496288251475981756.98%
custom 52675188787574483291736.90%
custom 60484370910108796671736.90%
custom 58369373320993910071626.46%
custom 59923914485850508721435.71%
custom 539805704814542156950.2%
custom 582806511507682835550.2%
custom 601016906125254647110.04%

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 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 18 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 2,506 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 14 August 2026 to 1 September 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.

Telegram Stars

Stars received
330
across the posts below
Posts paid on
13
of 20 we hold a reading for · 65%
Most on one post
44
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @rama_133. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 14 August 2026 to 1 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

1 Sept 2026, 12:24 UTC9 viewsread 1 September 2026

عطيني صلاحيه رفع المشرفين

Signed 𓏺 ࠝ𝑹

1 Sept 2026, 12:24 UTC10 views1 reactionsread 1 September 2026

وينها رمش

custom 60101690612525464711

Signed 𓏺 ࠝ𝑹

1 Sept 2026, 12:23 UTC10 views1 reactionsread 1 September 2026

هااي

custom 58280651150768283551

Signed 𓏺 ࠝ𝑹

31 Aug 2026, 00:33 UTC351 views175 reactions33 Starsread 1 September 2026

•• أنا مش انطوائيه انا مزاجي Vip مش لأي حد 🌟 .

custom 5267423049447141755175

29 Aug 2026, 22:11 UTC493 views175 reactions44 Starsread 1 September 2026
Photo

شاركني الشاي والحكي بدون أهداف دا الحزن ان شاف اتنين قاعدين يضحكوا بخاف🥲.

custom 5269234894285859867175

27 Aug 2026, 17:08 UTC829 views173 reactions33 Starsread 1 September 2026

مو ذنبك :🎀 - إنك نضيفة من جوا .. - إنك عفوية .. - إنك بتحبي كل الناس .. - إنك بتشوفي الكل منيح .. - إنك مابتحبي تشوفي حدا مدايق .. - إنك ع طول إنتي لي بتبادري .. - إنك مرباية وبنت أصل .. - أنك حنونة وكتير .. - أنو طلعوا الي حواليكي ما بيستاهلوكي .. - أنو عطيتي الناس وخذلولك .. - إذا الناس تفكيرها مريض وبشع ..  لاتلومي حالك ، ولاتزعلي إذا هالمنيح اللي قدمتيه ضاع عند البشر ! ضلّي متل ما انتي لانو انتي صح وعم تعملي ب

custom 5267518878757448329173

25 Aug 2026, 23:22 UTC≈1,070 views165 reactions33 Starsread 1 September 2026

•• حتى حُزني ! لم يكن حزناً بالطريقة المُعتادة لم أبحث عن كتفٍ لأبكي عليه ولا أذنٍ لتسمعني كنتُ أتوسّل العالم أن يتركني وشأني فحسب 🌟 .

custom 5267423049447141755165

24 Aug 2026, 22:11 UTC≈1,040 views162 reactions33 Starsread 1 September 2026

•• أَتَبكي على فَقدان شيءٍ وأنتِ الّذي قُلتِ: 🦋 ⏩وأصرِفْ عنّا شرَّ ما قَضَيتَ⏪

custom 5836937332099391007162

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

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

“لـِ ࢪاء ࠝ.” (@rama_133), 1,609 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/rama_133.

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.