Channel
@Filatovaofficiall
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
39subscribers
-1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002373412124 |
|---|---|
| Type | Channel |
| Username | @Filatovaofficiall |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 18 September 2026 |
| On Telegram | t.me/Filatovaofficiall |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 21:17 | 39 | -1 |
| 10 Aug 2026, 18:32 | 40 | no change |
| 10 Aug 2026, 00:46 | 40 | first reading |
14 posts held, back to 7 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 14 posts for this entry, the most recent from 9 May 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
137 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 59.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 81 | 59.1% | |
| custom 5235713357440373968 | 26 | 19.0% | |
| custom 5197216624968494051 | 16 | 11.7% | |
| custom 5195301335842450221 | 14 | 10.2% |
Custom emoji. 3 of the rows above are 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 13 of the 14 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 137 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 7 November 2025 to 9 May 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.
«С праздником днем Победы! 🪖 Пусть этот день напоминает о том, что добро и правда всегда побеждают. Желаю крепкого здоровья нашим ветеранам, а всем нам — мудрости, единства и мирного неба. Вечная память героям и бесконечная благодарность за жизнь!»🎖️
❤9
Дорогие девочки !💐 Хочу поздравить вас с этим замечательным праздником . Я вам желаю крепкого здоровья , счастья ,любви и исполнения всех заветных мечтаний .Пусть каждый день приносит радость,улыбки и новые достижения ! Всех люблю ❤️
❤13
Знакомьтесь! Участник проекта продюсерское продвижение - Любовь Филатова🎤 В скором времени вы сможете услышать в исполнении Любы её первый авторский трек - мы расскажем как будем писать его и о чем! Наш план, добиться максимальных результатов за пол года, собрать портфолио для участия в музыкальных проектах и подготовиться к успешному участию в них🙌🏻 Чтобы поддержать Любу в начале творческого пути - можно подписат…
❤17
С дебютом чтоль 💕 27.12.25🎙️
❤11
Сегодня 1-ое место ,всем спасибо кто поддерживал меня ) Сегодня меня перепутали и хотели дать 2-ое место 🤣 Кстати завтра у меня первое выступление по вокалу 💕 Пожелайте мне удачи 🍀
❤8
Сегодня фотографировалась на рекламу платья 🩷 Скоро буду выставлять фотографии с сестрой и еще ,с рекламы тоже выставлю фото )
custom 51953013358424502215custom 52357133574403739681
Я не знаю для чего это видео ,но пусть будет просто так красиво получилось снять 🥹❄️
custom 51953013358424502217❤4
Я не верю своим глазам 🥹
custom 52357133574403739686❤3custom 51953013358424502212
Кое -что готовлю для вас 🤫
custom 51972166249684940518❤4custom 52357133574403739683
L. Filatova pinned a photo
Верните меня обратно 🥹 Как же я хочу ,туда вернуться и продолжить жизнь именно там ,в Москве 🇷🇺
custom 51972166249684940517custom 52357133574403739683
Video message, posted without a caption
❤6
Showing the 12 most recent of 14 posts we hold for @Filatovaofficiall. 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.
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.
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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“L. Filatova” (@Filatovaofficiall), 39 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Filatovaofficiall.
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.