#потомпост
custom 54070834544939239289custom 54156679903120329578custom 54159812995863420064custom 54070728201549005093custom 54136737253273574971custom 54159530730612760861

Channel
@filyat0ly_luv
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
2,028subscribers
-71 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002747982517 |
|---|---|
| Type | Channel |
| Username | @filyat0ly_luv |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/filyat0ly_luv |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 69% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 17:56 | 2,028 | -9 |
| 12 Sept 2026, 01:21 | 2,037 | -3 |
| 7 Sept 2026, 18:01 | 2,040 | +4 |
| 3 Sept 2026, 00:04 | 2,036 | +7 |
| 30 Aug 2026, 14:18 | 2,029 | -8 |
| 27 Aug 2026, 08:46 | 2,037 | -2 |
| 24 Aug 2026, 04:15 | 2,039 | -21 |
| 20 Aug 2026, 05:14 | 2,060 | -9 |
| 17 Aug 2026, 09:45 | 2,069 | -11 |
| 13 Aug 2026, 13:47 | 2,080 | -18 |
| 10 Aug 2026, 22:41 | 2,098 | -1 |
| 8 Aug 2026, 08:18 | 2,099 | no change |
| 8 Aug 2026, 04:16 | 2,099 | first reading |
16 posts held, back to 2 August 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 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 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
401 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 37.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5407083454493923928 | 152 | 37.9% | |
| custom 5415667990312032957 | 86 | 21.4% | |
| custom 5413673725327357497 | 33 | 8.23% | |
| custom 5404772109253648671 | 29 | 7.23% | |
| custom 5407072820154900509 | 26 | 6.48% | |
| custom 5406905402329704121 | 25 | 6.23% | |
| custom 5415981299586342006 | 21 | 5.24% | |
| custom 5406662380195192687 | 15 | 3.74% | |
| custom 5415953073061276086 | 14 | 3.49% |
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 16 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 401 reactions 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 2 August 2026 to 7 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @filyat0ly_luv. 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 16 most recent posts we hold for this entry, published 2 August 2026 to 7 August 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.
#потомпост
custom 54070834544939239289custom 54156679903120329578custom 54159812995863420064custom 54070728201549005093custom 54136737253273574971custom 54159530730612760861
ㅤтапаем тапаем реактов много 🤍
custom 54070834544939239285custom 54156679903120329573custom 54069054023297041211
Posted without readable text
custom 540708345449392392826custom 541566799031203295712custom 54070728201549005099custom 54047721092536486716custom 54069054023297041215custom 54159812995863420064custom 54136737253273574973custom 54159530730612760863
Posted without readable text
custom 540708345449392392819custom 541566799031203295712custom 540477210925364867110custom 54069054023297041215custom 54066623801951926873custom 54070728201549005093custom 54136737253273574972custom 54159530730612760862
привеt реакций
custom 54070834544939239287custom 54156679903120329575
︎︎ ︎︎♡⃘ 🌟🌟い𓂃 🌟🌟 !! будь у меня выбор: счастье или ты . . . я бы без раздумий выбрала счастье. 🥹🥹🤩 ㅤㅤ ведь мое счастье - это и есть ты ! #346
custom 540708345449392392824custom 541566799031203295717custom 541367372532735749713custom 54069054023297041217custom 54159812995863420064custom 54159530730612760863custom 54047721092536486712custom 54066623801951926872
Posted without readable text
custom 540708345449392392827custom 541566799031203295715custom 541367372532735749710custom 54047721092536486713custom 54069054023297041213custom 54070728201549005093custom 54159530730612760863custom 54066623801951926872
ㅤㅤㅤㅤ🎼 🤍🤩🤍💕 ╵ 1:13 🪽 :ㅤ﹫ ⲕᥲⲧᥲᥴⲧρ𐔖ⲫυɥᥱᥴⲕυ ⲧᥱⳝя ㅤㅤㅤㅤㅤㅤне хватает ⲙⲏᥱ、 ⲿ𐔏𐔤 электричество、 ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤно не попадаю я、 ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤвоздух ⲧ𐔖᥈ɥⲕᥲⲙυ、 и ᥒ𐔤᥈ьᥴ на три счета-та . . . ㅤбьёт в ᥒᥱρᥱⲏ𐔖ᥴυц𐔤、 ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤя знаю、 ㅤㅤㅤㅤㅤㅤвсе знаю я、 ㅤㅤㅤно ⲕᥲⲧᥲᥴⲧρ𐔖ⲫυɥᥱᥴⲕυ ⲧᥱⳝя ㅤㅤㅤㅤㅤㅤне хватает ⲙⲏᥱ、 ㅤⲕᥲⲧᥲᥴⲧρ𐔖ⲫυɥᥱᥴⲕυ ⲧᥱⳝя не хватает 🤩 🎶 : ﹫ ночные снайперы — катастрофически # 𝟒𝟐.
custom 540708345449392392816custom 541566799031203295711custom 54066623801951926877custom 54069054023297041213custom 54136737253273574973custom 54159812995863420063custom 54070728201549005092custom 54159530730612760862
Signed ㅤанатоля хрюковична
ㅤ на сегодня тейки - В С Е спасибо всем, кто их писал, простите если кого не выложили ㅤ продолжим в следующие выходные !
custom 54070834544939239282
Ч очень люблю Сашеньку. Он мое солнце, он мое счастье, он мой котёнок и самое дорогое что есть в моей жизни. Я очень часто думаю о нем и каждый день мечтаб о том, чтобы он когда нибуть приехал ко мне. Мы далеко друг от друга. Между нами - сотни километров, разные города, чужие улицв, которые я никогда не видела, но уже люблю их, потому что по ним ходит он. Мой Сашенька(Деш) неанон Майлети, ловер Деш(Сашеньки) и мам…
custom 54070834544939239281
Signed ﹫ ʟ𝓸ᵥ𝓮𝒍𝒚 𝐛𝓸𝔱 ♡゙ | филятолики канон
лбблб пересматриватьь ишру кальмара неанон лемон @dailyl0vely_bot ⠆ take bot ! #тейк ┊ @filyat0ly_luv . . ♡᷒ᰰ
custom 54070834544939239282custom 54156679903120329572
Signed ﹫ ʟ𝓸ᵥ𝓮𝒍𝒚 𝐛𝓸𝔱 ♡゙ | филятолики канон
всем привет я очень люблю своего любимого мальчика Яна я знаю что он это увидит поэтому януш, я хоть и редко говорю, как ценю тебя, но знай, что каждый раз, когда я вижу тебя или ты пишешь мне сообщения, моё сердце замирает я очень дорожу тобой и нашими отношениями. я очень рад, что скоро нам будет уже 5 лет. 5 лет, которые мы провели рука об руку и целых 13? лет дружбы, ахвхахв надеюсь мы будем вместе всегда, до сам…
custom 54070834544939239286custom 54047721092536486714custom 54070728201549005093
Signed ﹫ ʟ𝓸ᵥ𝓮𝒍𝒚 𝐛𝓸𝔱 ♡゙ | филятолики канон
Showing the 12 most recent of 16 posts we hold for @filyat0ly_luv. 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.
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.
Named by 4 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“ㅤ филятоли хрюшки 𝄄𝄄 love cf / daily ׅ𓈒 𔘓” (@filyat0ly_luv), 2,028 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/filyat0ly_luv.
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.