Channel
@FelixLegacy
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
168subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003972532655 |
|---|---|
| Type | Channel |
| Username | @FelixLegacy |
| Created | 26 May 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/FelixLegacy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 05:44 | 168 | no change |
| 12 Aug 2026, 03:31 | 168 | first reading |
16 posts held, back to 26 May 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 16 (26 May 2026 – 8 August 2026) |
| Views total | 3,466 |
| Reactions total | 168 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:31 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.
Measured directly from 6 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.
290 reactions across 15 posts, in 65 distinct kinds. The most used accounts for 5.86% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6336769893542663462 | 17 | 5.86% | |
| custom 6336929077915555871 | 17 | 5.86% | |
| custom 6084590600995214401 | 16 | 5.52% | |
| custom 5172447776205702031 | 15 | 5.17% | |
| custom 6336725990386963799 | 14 | 4.83% | |
| custom 5422369784266257729 | 13 | 4.48% | |
| custom 5893048571560726748 | 13 | 4.48% | |
| custom 5895266423952904371 | 13 | 4.48% | |
| custom 5776428724731781108 | 8 | 2.76% | |
| custom 6336870266928371445 | 8 | 2.76% | |
| custom 5373146297958154452 | 7 | 2.41% | |
| custom 5424671633333845534 | 7 | 2.41% | |
| custom 6262697813814025356 | 7 | 2.41% | |
| custom 5328204155309808263 | 6 | 2.07% | |
| custom 5422739014014764143 | 6 | 2.07% | |
| custom 5422807926765029627 | 6 | 2.07% | |
| custom 5773692770434685497 | 5 | 1.72% | |
| custom 6084916511703569476 | 5 | 1.72% | |
| custom 4958839553424098323 | 4 | 1.38% | |
| custom 5240334914049556477 | 4 | 1.38% | |
| 45 further kinds | 99 | 34.1% |
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 15 of the 16 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 290reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 26 May 2026 to 8 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.
🌟 Nᴏ ᴏɴᴇ ɪꜱ ᴄᴏᴍɪɴɢ ᴛᴏ ꜱᴀᴠᴇ ʏᴏᴜ.
custom 54223697842662577295custom 54228079267650296273custom 53236573783762220672custom 54227382881652867172custom 54227390140147641432custom 62896114833450696812custom 54225592696334217471custom 54225815691036265761
@musi | info
custom 53236573783762220672custom 54113702914168209752custom 54246716333338455342custom 62626978138140253562custom 54223576982282903201custom 54228079267650296271custom 62445410371386822081
💧 "ꜱʜᴇ ᴀᴄᴛꜱ ʟɪᴋᴇ ꜱʜᴇ'ꜱ ᴏᴋ, ʙᴜᴛ ᴅᴇᴇᴘ ᴅᴏᴡɴ ɪɴꜱɪᴅᴇ, ꜱʜᴇ'ꜱ ᴛᴏᴏ ʜᴏʀɴʏʏʏʏʏ ᴀɴᴅ ꜱᴀʏꜱ ʏᴇꜱ ᴅᴀᴅᴅʏʏʏʏʏ"🚫
custom 54223697842662577295custom 54223576982282903202custom 54228021800987855661custom 54228079267650296271custom 54246716333338455341custom 62445410371386822081custom 62626978138140253561custom 62987395429795182711
Sticker, posted without a caption
custom 54227390140147641434custom 54228021800987855662custom 54360317273424914622custom 54113718461949852801custom 54223576982282903201custom 54223697842662577291custom 54228079267650296271custom 54246716333338455341
🌟 Pᴏᴠ: Eᴠᴇʀʏᴏɴᴇ Cᴀʟʟᴇᴅ Iᴛ Sᴛᴀʟᴋɪɴɢ, Bᴜᴛ Iɴ Mʏ Lᴀɴɢᴜᴀɢᴇ. 💋 I Cᴀʟʟᴇᴅ Iᴛ Iɴᴠᴇsᴛɪɢᴀᴛɪᴏɴ.
custom 61139291489320344664custom 53279098297909476591custom 54223697842662577291custom 54360658465626911481custom 54363481977127301131custom 61138830381631463481custom 62489615291488706751custom 62626978138140253561
𝑇𝑖𝑚𝑒 𝑒𝑟𝑎𝑠𝑒𝑑 𝑚𝑦 𝑛𝑎𝑚𝑒, 𝐹𝑎𝑡𝑒 𝑏𝑢𝑟𝑖𝑒𝑑 𝑚𝑦 𝑒𝑥𝑖𝑠𝑡𝑒𝑛𝑐𝑒, 𝑎𝑛𝑑 𝑤ℎ𝑒𝑛 𝑛𝑜𝑡ℎ𝑖𝑛𝑔 𝑟𝑒𝑚𝑎𝑖𝑛𝑒𝑑 𝑜𝑓 𝑚𝑒, 𝐼 𝑟𝑒𝑚𝑎𝑖𝑛𝑒𝑑 𝑎𝑠 𝑡ℎ𝑒 𝐹𝑜𝑜𝑙.
custom 53282041553098082632custom 54360658465626911482custom 62489615291488706752custom 53279098297909476591custom 54362539833101240961custom 61137398740182673501custom 61138830381631463481custom 62626978138140253561
🫤 Nᴏ ꜱᴘᴇᴄɪᴀʟ ʙʟᴏᴏᴅʟɪɴᴇ ʙᴛᴡ.. ᴏɴʟʏ ᴛᴀʟᴇɴᴛ ᴀɴᴅ ʜᴀʀᴅᴡᴏʀᴋ. 🌟 Fᴛ. Jᴀᴍᴇꜱ Lᴇᴇ, Lᴏᴏᴋɪꜱᴍ
custom 52403349140495564774custom 61588204778223090263custom 61613319041140703492custom 52199567244541472261custom 52424893426596746551custom 52447335403812429231custom 52471318286444962961custom 53731462979581544521
@musi | info
custom 49589636479141819132custom 60982778328388812652custom 60983176471857155392custom 53282041553098082631custom 54362539833101240961custom 54719033457382757001custom 60979733282475299021custom 60980676113696113271
Video, posted without a caption
custom 49588395534240983234custom 53731462979581544522custom 49587198483905915401custom 49589636479141819131custom 53282041553098082631custom 60984347752388453141
🤩🤩🤩🤩
custom 63367698935426634626custom 58952664239529043715custom 53731462979581544522custom 53752064391512224542custom 63369290779155558712custom 49585625666882119741custom 51724477762057020311custom 61138830381631463481
Video, posted without a caption
custom 63369290779155558718custom 58952664239529043715custom 51724477762057020314custom 53752064391512224542custom 49587198483905915401custom 53279098297909476591custom 53282041553098082631custom 53731462979581544521
Video, posted without a caption
custom 58930485715607267488custom 51724477762057020315custom 60845906009952144014custom 63367698935426634623custom 63369290779155558713custom 58952664239529043712custom 53282041553098082631custom 54223697842662577291
Showing the 12 most recent of 16 posts we hold for @FelixLegacy. 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.
Citation-graph rank — 831,304 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Ꮋꫀʏㅤ𝐅 ᴇ ʟ ɪ xㅤ ᥫ᭡” (@FelixLegacy), 168 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/FelixLegacy.
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.