Мы с Федром 🌟
custom 53956448055334333513

Channel
@NifiliCos
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
161subscribers
+29 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002098288523 |
|---|---|
| Type | Channel |
| Username | @NifiliCos |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/NifiliCos |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 9 November 2026 and assigned it the closest of 31 fixed categories, at 70% 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 the other topics.
@NifiliCos was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 19:59 | 161 | +3 |
| 9 Nov 2026, 18:22 | 158 | no change |
| 9 Nov 2026, 17:48 | 158 | +23 |
| 30 Aug 2026, 09:15 | 135 | +2 |
| 23 Aug 2026, 06:28 | 133 | -2 |
| 14 Aug 2026, 23:46 | 135 | +3 |
| 9 Aug 2026, 00:31 | 132 | no change |
| 7 Aug 2026, 19:05 | 132 | first reading |
19 posts held, back to 4 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 2 pages of 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. It is computed over the 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 19 (4 August 2026 – 9 November 2026) |
| Views total | 1,156 |
| Reactions total | 116 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 18:22 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 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.
171 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 25.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 44 | 25.7% | |
| custom 5276378391266744683 | 35 | 20.5% | |
| custom 5292105251539669450 | 19 | 11.1% | |
| custom 5307612973991222724 | 11 | 6.43% | |
| custom 5395644805533433351 | 11 | 6.43% | |
| custom 5395683821016349104 | 11 | 6.43% | |
| custom 5213357197966204782 | 8 | 4.68% | |
| custom 5213171333256473311 | 7 | 4.09% | |
| ❤🔥 | 6 | 3.51% | |
| custom 5213161021039997093 | 5 | 2.92% | |
| 💘 | 5 | 2.92% | |
| custom 5289810987384334248 | 4 | 2.34% | |
| 💋 | 3 | 1.75% | |
| custom 5328293409025199982 | 2 | 1.17% |
Custom emoji. 10 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 17 of the 19 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 171 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 4 August 2026 to 9 November 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.
Telegram’s own ‘edited’ marker: 0 of 10 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Мы с Федром 🌟
custom 53956448055334333513
Posted without readable text
custom 53956448055334333518custom 52763783912667446834custom 52921052515396694504custom 52131713332564733111custom 52133571979662047821custom 53956838210163491041
Седня будет постик! А то канал совсем пустует 🌟
custom 52763783912667446837custom 52921052515396694505custom 52898109873843342484custom 53282934090251999822
Я в шоке чуть-чуть
❤14custom 52763783912667446835custom 52921052515396694504custom 53956838210163491042
♣️ Трефы в сборе! ♣️ #косплей Куромаку Клео Зонтик
❤6
К сожалению мы встретились
💘5custom 52133571979662047823custom 52763783912667446833custom 52921052515396694502
🌟🌟🔠🔠🔠🔠🔠🌟🌟 Буду на Хокку 15 ноября вместе с Rose в Гамболе и Дарвине! 🌟🌟
custom 52763783912667446833custom 52921052515396694503❤2custom 52131713332564733112
Отписки прям полетели 🌟 Извиняюсь за неактив в канале, Сейчас куча забот и проблем. Немного расскажу о планах. Мне приехал новый косплей и есть парочка которые я не снимала еще. Также я сейчас потихоньку работаю над Юини. Следующие косплеи которые я закажу будут Митя 🧑 и Рукия в банкае 🌸 Еще сегодня сделаю анонс на мероприятие на которое я тоже пойду в новом косплее 🌟 Я думаю может больше щп и просто повседневных вещ…
❤4custom 52763783912667446833❤🔥2
🌟🌟🌟🌟🌟🌟🌟🌟 🌟Ты был хорошим псом, Дэнджи ▪️𝑷𝒉|𝑹𝒕: @yatsankos ▪️𝑪𝒐𝒔𝒑: @lissocos Рк/рт/мью/вп?🌟
🔵🔵🔵🔵🔵🔵🔵🔵 По характеру он кажется грубоватым и ворчливым, но на деле очень заботлив. Его магия описывается как «тёплая», и он постоянно создаёт полезные артефакты для дома и учеников Он пытается быть для Кифри «тормозом» и опорой, хотя иногда чувствует боль из-за того, что друг не доверяет ему свои тайны Кица 25.10.2026 ms_rose🔵
custom 52763783912667446835custom 52131610210399970934custom 52133571979662047824
✨🪞💭💭💭💭💭💭👓✨ 🍉✨🃏👁️⭐️⭐️🛖🛖🛖🍉 Тринадцать ударов сердца гордо поют в походе за пламенем, ведь это их горячо любимая земля. И снова открывается первая страница, и на ней написано пророчество о жизни.🪞 ρⲧ/ρᥱᥲⲕⲧ? ⲃᥒ/ⲙью? 🌟🌟 Ph🥰
custom 52763783912667446835custom 53076129739912227244custom 53956838210163491044❤2custom 52921052515396694501
Сейчас смотрю доктора стоуна Думаю может сделать на кого-нибудь потом косплей?
❤2
Showing the 12 most recent of 19 posts we hold for @NifiliCos. 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.
Named by 2 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.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“+:。.𝓝𝓲𝓯𝓲𝓵𝓲 𝓒𝓸𝓼。..:*♬” (@NifiliCos), 161 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/NifiliCos.
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.