ребятаа забыла написать можно задавать вопросы отдельным участникам (не обязательно всем сразу, можно отдельно кому-то), главное пишите кому!
Signed ✁ㅤֻ𝒽𝗮rik𝘆𝘂 ׅ𝓈 針急

Channel
@fantikksquad
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
51subscribers
+0 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003947408555 |
|---|---|
| Type | Channel |
| Username | @fantikksquad |
| Description | аватарку рисовала самая крутая художница @krafty17 |
| Created | Between 1 April 2026 and 22 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/fantikksquad |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 14:23 | 51 | no change |
| 11 Sept 2026, 03:47 | 51 | first reading |
18 posts held, back to 22 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.
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 16 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 September 2026 |
|---|---|
| Posts held | 18 (22 August 2026 – 4 September 2026) |
| Views total | 1,721 |
| Reactions total | 166 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Sept 2026, 14:23 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.
Lifetime counters from Telegram’s own channel header, read 11 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
166 reactions across 16 posts, in 13 distinct kinds. The most used accounts for 19.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 32 | 19.3% | |
| custom 5472173464821439380 | 27 | 16.3% | |
| 🍓 | 19 | 11.4% | |
| custom 5202147844424744583 | 16 | 9.64% | |
| 💘 | 13 | 7.83% | |
| custom 5237947539298220860 | 11 | 6.63% | |
| custom 5294152439111388026 | 11 | 6.63% | |
| custom 5314560422894927426 | 10 | 6.02% | |
| custom 5990242839655619399 | 10 | 6.02% | |
| custom 5267262490684711549 | 8 | 4.82% | |
| 😭 | 5 | 3.01% | |
| custom 5460795727087148129 | 3 | 1.81% | |
| 🐳 | 1 | 0.602% |
Custom emoji. 8 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 16 of the 18 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 166 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 22 August 2026 to 4 September 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.
ребятаа забыла написать можно задавать вопросы отдельным участникам (не обязательно всем сразу, можно отдельно кому-то), главное пишите кому!
Signed ✁ㅤֻ𝒽𝗮rik𝘆𝘂 ׅ𝓈 針急
пр ребята!! давайте в ночную анонку? завтра если что тоже будет отвечаем в щп
🍓2
Signed ✁ㅤֻ𝒽𝗮rik𝘆𝘂 ׅ𝓈 針急
поздравляю победителей! с вами свяжутся в ближайшее время🐡
custom 53145604228949274263
Signed дасяя
Выбор дополнительных победителей (в количестве 1): Победитель: 1. Йоу Марго (@AvoDefey) Проверить результаты
custom 53145604228949274264😭1
Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]
4 место идет на перекрут из-за невыполнения условий розыгрыша 🐡
Signed дасяя
Результаты конкурса: 🥳 Победители: 1. ~𝓂𝒾𝓏𝓊𝓀𝒾~ (@Kotleta_mizyki) 2. 𝐾𝐴𝑍𝐴𝑆𝐻𝐾𝐴 #𝐼𝑁𝐹𝑃 (@KAZASHKA25) 3. ⁞❈⁞❃.:▹ⳝⲁⲥя◃:.❃⁞❈⁞ (@Baksik_cisic) 4. Chibzik (@Chibz_hugtime) 5. •|ᏋԲค🌈 (@Efachka0) Проверить результаты ✅
😭4custom 53145604228949274263custom 54721734648214393801
Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]
ещё арт с джухуном клас👍👍👍 получился немного скетч а не арт напоминаю про лоту #скетч #харикью
❤8💘4🍓1
Signed ✁ㅤֻ𝒽𝗮rik𝘆𝘂 ׅ𝓈 針急
Дася тархун пьет #арт #пельмени
❤11💘3custom 59902428396556193992
Signed Pelmeni
Джухунчик для харикью в moe стиле бебебе :Р #арт #скетч #0сом
❤9💘3custom 59902428396556193993custom 52379475392982208601
Signed OC0m
пост для репостов хоши сейчас в ресте, поэтому к сожалению в этот раз без нее
🍓4🐳1
Signed дасяя
❌🍊🤩🤩🤩🤩🤩🤩🤩🤩🍊 ❌на артики от фантик сквада!! что нужно для участия? 🤩подписка на канал 🤩репост в основной канал / если канала нету - 2 друзьям ❌❌ какие будут призы? 🤩 арт в полный рост от сома 🤩арт по пояс от харикью 🤩арт в полный рост от пельмени 🤩арт по пояс от даси 🤩арт в полный рост от бейли итоги будут 3 сентября в 17:00 по мск!
🍓5custom 54721734648214393802💘1
Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]
пр это джухун опять я этот арт вчера заспидранила #арт #харикью
custom 52379475392982208607
Signed ✁ㅤֻ𝒽𝗮rik𝘆𝘂 ׅ𝓈 針急
Showing the 12 most recent of 18 posts we hold for @fantikksquad. 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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“фантиксквад” (@fantikksquad), 51 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/fantikksquad.
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.