Channel
@Fileeex
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
120subscribers
-2 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002145687086 |
|---|---|
| Type | Channel |
| Username | @Fileeex |
| Created | Between 1 December 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 31 August 2026 |
| On Telegram | t.me/Fileeex |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 10:24 | 120 | -1 |
| 18 Aug 2026, 06:42 | 121 | -1 |
| 10 Aug 2026, 13:45 | 122 | no change |
| 10 Aug 2026, 13:34 | 122 | first reading |
15 posts held, back to 18 November 2025 — 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 15 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
250 reactions across 15 posts, in 15 distinct kinds. The most used accounts for 32.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 81 | 32.4% | |
| 😭 | 39 | 15.6% | |
| ❤🔥 | 32 | 12.8% | |
| 💔 | 21 | 8.40% | |
| ⚡ | 18 | 7.20% | |
| 😨 | 15 | 6.00% | |
| 🔥 | 11 | 4.40% | |
| 💋 | 9 | 3.60% | |
| 🥰 | 8 | 3.20% | |
| 🫡 | 5 | 2.00% | |
| 👍 | 3 | 1.20% | |
| 🥴 | 3 | 1.20% | |
| custom 6037243474229595786 | 2 | 0.8% | |
| 🤯 | 2 | 0.8% | |
| 🤩 | 1 | 0.4% |
Custom emoji. One 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 count beside it is 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 15 of the 15 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 250 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 18 November 2025 to 10 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.
Сегодня день рождения у одного прекрасного человечка, который был рядом, поддерживал и оставался хорошим человеком на протяжении нашего общения! Поздравьте Дашу DK с днем рождения под этим постом 🙏 🥳 А еще я довел её до слез поздравлением 😂😭😭😭🥺🥺🥺🥺🥺🥺🥺🥺 P.s не всегда получается постить что-то именно в этот канал, поэтому не теряйте, выйду на дембель и будет контент
❤6
Posted without readable text
🔥1
💜💜💜 💜💜💜 Сегодня нашей команде AVES исполнилось 2 годика👼 На этом пути было много классных проектов, фестов и самое главное - людей⭐️ Большое спасибо всем, кто разделяет наш путь и особенно тем, кто с нами с самых истоков! Хотим поделиться с вами нашими достижениями за последний год⭐ 👼 Гран-при и специальный приз от жюри на Kingdom 👼 3 место Kingdom 👼 2 место K-DOM 👼 7 проектов 👼 Суммарно 3к подписчиков и окол…
❤🔥3⚡2
У нашей прекрасной Лил розыгрыш!!! Всем советую поучаствовать, когда у вас еще будет бесплатная съемка от такого крутого челикса?)
❤5
💜💜💜💜💜💜💜💜💜💜 я бы хотела провести небольшой розыгрыш, и порадовать вас альбомом 💜💜💜💜💜 💜💜💜💜 - 💜💜💜, а также 1 бесплатной съемкой! на съемке я вручу альбомчик💜 💜Чтобы принять участие, необходимо сделать репост данного поста себе в канал, подписаться и оставить любой комментарий под этим постом💜 📌победитель будет выбран случайным образом, через рандомайзер!📌 итоги будут подведены через месяц, 7 июля, удачи 💜
❤🔥1
Товарищи, я продолжаю свою срочную службу в дагестане. Не теряем меня, будет лютая туса 24/25 ноября этого года, освобождаем этот день для встречи меня 😂
❤14🔥10⚡5🥰3
«не переживай, все переживем» доброе обновление, судя по всему, любимого ролика феликса 🎬 ждем возвращения (надеемся, что скорейшего, лисенок) ❤️
❤10😭5⚡1
Скорее бы вернуться во все это
❤15🥰5🥴3
Первые кто мне написал-мои стажеры с работы, я воспитал хороших детей 😭😭😭😭😭😭😭😭
❤🔥15⚡4👍2
Товарищи, я пока на связи и могу немного пообщаться с вами, так что если что можно писать в личку 😁
❤13⚡2👍1
Вот когда вернусь, вы будите в шоке с разрыва индустрии.
❤🔥13💋9❤5⚡1
Товарищи, я в армии, не теряем
😭34💔21😨15🫡5⚡1
Showing the 12 most recent of 15 posts we hold for @Fileeex. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“Что-то на непонятном от FILEX” (@Fileeex), 120 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/Fileeex.
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.