Channel
@farfurish
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
340subscribers
+12 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001975246969 |
|---|---|
| Type | Channel |
| Username | @farfurish |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/farfurish |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 17:15 | 340 | +14 |
| 24 Aug 2026, 18:03 | 326 | -3 |
| 16 Aug 2026, 18:15 | 329 | +1 |
| 9 Aug 2026, 08:41 | 328 | no change |
| 9 Aug 2026, 00:15 | 328 | first reading |
7 posts held, back to 21 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 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 7 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
105 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 37.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 39 | 37.1% | |
| 🔥 | 25 | 23.8% | |
| custom 5271894728877571418 | 23 | 21.9% | |
| ❤🔥 | 10 | 9.52% | |
| 🍓 | 5 | 4.76% | |
| 👾 | 2 | 1.90% | |
| 🐳 | 1 | 0.952% |
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 7 of the 7 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 105 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 21 May 2026 to 1 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.
Скажу честно: я пока восстанавливаюсь от жесткого выгорания, которое на данный момент у меня переступило критичную стадию, а само выгорание начиналось еще в начале прошлого учебного года. У меня накопилось достаточно много артов, которые я могу выложить, но пока что у меня нет сил на это. Канал жив, я (вероятно) тоже, не теряйте, скоро обязательно вернусь!!
❤9❤🔥2🐳1custom 52718947288775714181
🌱ЧАЙДУХ РОДИЛСЯ(๑°ㅁ°๑)‼✧ как неожиданно и приятно Этот год был морально очень тяжелый тем, что подкидывал мне страшные события, еще и под выпускной год, с чем было много дела, выкачивающих силы, но главное здесь то, что руки мои не опустились. Да, хотелось, но как видите, не сдалась же, двигаюсь дальше!! Я бы даже сказала, конкретно сейчас, чувствую себя очень даже хорошо благодаря бестиям, которые были рядом все эт…
🍓5custom 52718947288775714182
Перезалив по некоторым причинам Фем бакуго в #KatsukiZine 🤲🏻🤲🏻🤲🏻
❤21🔥13❤🔥6custom 52718947288775714181
с первомаем 2.0!!!
❤6🔥5custom 52718947288775714184
ᅠ ᅠ ᅠ ᅠ ᅠ 🌟🌟🌟🌟 🌟Наконец... пришло время поднять занавес! Встречайте главную звезду самой захватывающей, невероятной, интригующей, заставляющей трепетать сердца постановки – Шэдоу Милк Куки! Аплодисменты, аплодисменты! Не сводите глаз ни на секунду, не думайте ни о чем другом, кроме как о грандиозном, единственном в своем роде спектакле Театра Лжи! ᅠ ᅠ [ПРЕДЗАКАЗЫ ОТКРЫТЫ + РОЗЫГРЫШ] Вас ожидают: 🌟Зин в твердом переп…
🔥3❤2custom 52718947288775714182
прошу прощения за пропажу, я еще не умер, но пока обнов не будет по причине сессия и экзамены вкидываю работу с сегодняшнего занятия также поздравляю всех выпускников и желаю удачи студентам и школьникам все сдать 🙏🙏🙏
custom 527189472887757141813❤🔥2👾2❤1🔥1
Вот и настал этот день! Журналисты шушукаются у входа, фанаты держат камеры наготове, а полицейские изо всех сил пытаются сдерживать беснующуюся толпу. Ожидание съедает вас, на улице шумно и душно, вы почти сходите с ума, но вот наконец откуда-то сверху слышатся взрывы! — Неужели это?.. Подтверждая ваши догадки, один из журналистов хватает микрофон: — А вот и он! Встречайте одного из самых популярных про-героев —…
🔥3
Showing the 7 most recent of 7 posts we hold for @farfurish. 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 7 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“🪷 trofim ovich 18+ 🪷” (@farfurish), 340 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/farfurish.
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.