Telegram RegisterThe public register of Telegram

Channel

𝙧𝙚𝙫𝙚𝙧𝙞𝙚

@felora_ml

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

3,896subscribers

-14 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002369046495
TypeChannel
Username@felora_ml
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/felora_ml

Growth

3,8963,9103,9037 August 2026 — 3,910 subscribers7 August 2026 — 3,910 subscribers11 August 2026 — 3,896 subscribers7 August 202611 August 2026
3 measurements spanning 4 days, net -14. 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 3,894–3,912 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 20:323,896-14
7 Aug 2026, 17:313,910no change
7 Aug 2026, 17:223,910first reading

Engagement

18 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
4.68%
avg views ÷ 3,896 subscribers
Avg views / post
183
18 posts measured
Reaction rate
19.1%
reactions ÷ views · ER floor
Posts in window
18
of 18 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held18 (29 July 20266 August 2026)
Views total3,285
Reactions total628
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:57 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.

What this channel posts

Video runtime
37s
Average length
19s

Measured directly from 2 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.

Reaction mix

628 reactions across 18 posts, in 20 distinct kinds. The most used accounts for 13.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8413.4%
🦄7912.6%
🐳6510.4%
🔥609.55%
🌚487.64%
👾477.48%
🕊447.01%
💘345.41%
🤣274.30%
💋264.14%
🍓223.50%
🍾213.34%
💔162.55%
142.23%
🆒142.23%
101.59%
💊71.11%
💯50.796%
👻40.637%
👀10.159%

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 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 628reactions 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 29 July 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.

Recent posts

6 Aug 2026, 15:36 UTC125 views10 reactionsread 8 August 2026

کاش برگردیم به زمانی که تنها تلخی زندگیمون خوردن شربت سرما خوردگی بود

👾5🍾2💋1💯1🆒1

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

6 Aug 2026, 15:35 UTC132 views10 reactionsread 8 August 2026
Photo

Photo, posted without a caption

🐳2👾2👀1👻1💊1💋1💘1🆒1

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

6 Aug 2026, 15:34 UTC148 views9 reactionsread 8 August 2026

برای چیزی که میخوای تلاش کن نه ارزو.

2👾2👻1💊1💋1💘1🦄1

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

4 Aug 2026, 17:46 UTC180 views16 reactionsread 8 August 2026

صدات خیلی قشنگه💔🥺

🍓9👾2🍾1🐳1💋1💘1💯1

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

4 Aug 2026, 17:44 UTC235 views16 reactionsread 8 August 2026
Voice message

Voice message, posted without a caption

🆒8👾2💯2💊1💋1💔1🕊1

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

2 Aug 2026, 15:56 UTC232 views42 reactionsread 8 August 2026

آدم درست اونیه که باعث بشه بیشتر از قبل خودتو دوست داشته باشی نه اینکه احساس ناکافی بودن بگیری

🦄24👾4🐳3💔3🍓2💘2🆒2🍾1

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

2 Aug 2026, 15:53 UTC233 views41 reactionsread 8 August 2026

از یه جایی به بعد دیگه تعداد آدمای دور و برت مهم نیست واقعی بودنشونه که مهمه

🌚22🍓3🍾3🦄3🐳2👻2💋2💔2

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

2 Aug 2026, 06:40 UTC195 views38 reactionsread 8 August 2026

۱۰:۱۰

🔥21🐳3💊3🦄3💔2💘2🆒2🌚1

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

1 Aug 2026, 10:26 UTC86 views44 reactionsread 8 August 2026
Forwarded from @OnissmFile

گاهی بعد رفتن یه نفر می‌فهمیم چقدر اشتباه کردیم و اونجاست که تلخ ترین از دست دادن زندگیمون رو تجربه میکنیم، اون آدم تبدیل میشه به آرزوی دست نیافتنی که هیچ وقت قرار نیست دوباره داشته باشیمش. اُنیسم

23💘4🌚3🔥3🕊3🦄3🐳2💋2

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

1 Aug 2026, 10:16 UTC179 views44 reactionsread 8 August 2026
Video

Video, posted without a caption

🐳23🌚53💋3🍾2💔2💘2🔥2

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

1 Aug 2026, 09:20 UTC222 views39 reactionsread 8 August 2026

ـ سر انجام شمع فهمید همان نخی که در سینه پنهان کرده بود نابودش کرد!

🦄21🌚4🍾3🔥32💋2💘2🐳1

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

31 Jul 2026, 09:21 UTC211 views52 reactionsread 8 August 2026

اینقدر بدم میاد دارم پامو تکون میدم میان دستشونو میزارن رو پام که یعنی تکون نده خب اگه اینو تکون ندم که پا میشم میزنم تو گوشتون....

🤣27🦄65🔥42🍾2🐳2💋2

Signed 𝓕𝓮𝓵𝓸𝓻𝓪

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

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

“𝙧𝙚𝙫𝙚𝙧𝙞𝙚” (@felora_ml), 3,896 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/felora_ml.

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.