🤏
custom 537056773273762470219

Channel
@huskyyytalks
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
342subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002597649999 |
|---|---|
| Type | Channel |
| Username | @huskyyytalks |
| Description | code:13.37 Founder's Channel Zifretta. @Zifretta_Bot @LokiGateBot to be continued... Soon |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/huskyyytalks |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 07:01 | 342 | no change |
| 7 Aug 2026, 17:38 | 342 | first reading |
19 posts held, back to 6 June 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 pageof 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 19 posts for this entry, the most recent from 14 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 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.
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.
765 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 49.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5370567732737624702 | 382 | 49.9% | |
| custom 5407045748976018145 | 137 | 17.9% | |
| custom 5409168064115665922 | 121 | 15.8% | |
| custom 5408896424614061463 | 80 | 10.5% | |
| custom 5411163183798835202 | 45 | 5.88% |
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 areTelegram’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 19 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 765reactions 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 6 June 2026 to 14 July 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 @huskyyytalks. 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 19 most recent posts we hold for this entry, published 6 June 2026 to 14 July 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 537056773273762470219
📱— 💼
custom 540704574897601814512custom 54088964246140614638custom 53705677327376247024
Всем здравствуйте! 👋 Помимо продуктовых обновлений и активной разработки, хотим поделиться с вами еще одной приятной новостью. 🎤Команда Zifretta становится сильнее! — С радостью представляем нового участника нашей команды, Никиту Барышева. Многие знают Никиту как амбассадора Zifretta и основателя канала «Лысые истории». За его плечами большой опыт в развитии проектов, аналитике, работе с аудиторией и медиа. 📰В Z…
custom 537056773273762470223custom 540704574897601814512custom 540916806411566592212
+🤓☝️
custom 537056773273762470223custom 54088964246140614635custom 54070457489760181454
Something is cooking ⛅️
custom 537056773273762470220
Ну чтожжж... 🔘Общедоступный 1-ый скин зашел,. Еще парочку для "разнообразия" и включим предметы на добычу в систему помимо BattlePass, а дальше и Второй этап "улучшения предметов" Я надеюсь вы помните — NPC делаются не для того, чтоб их за день проходили, как раз вот на Summer Man вам показатель будет😀 🔘Те же Monks, Loodik то есть те же NPC с донатом в заданиях, тоже не проработаны чтоб их проходили в первый день.
custom 537056773273762470211custom 54091680641156659229custom 54070457489760181455
Всем здравствуйте! 👤 🎤Прежде чем, выпускать посты связанные с модулем Neuroport, NPC, предметами, уделите внимание данному посту. 🔘Это важно. Пожалуйста не поленитесь, прочтите, поймите. ‼️Зачем проходить задания? Главная цель заданий не в получении XP, Boosts или других наград, это лишь бонусы не более. Задания являются способом открыть доступ к предметам экипировки для вашего персонажа. 💡Пока задание на предмет …
custom 537056773273762470218custom 54070457489760181458custom 54091680641156659227
— Summer man - запущен — Black Monk - запущен — Корректировка на White Monk — сделано - Push-уведомление в процессе - Посты на канал Zifretta - в процессе
custom 537056773273762470215custom 540889642461406146315custom 541116318379883520215
🔘Ожидаем Push в боте в течении дня, в ночь не стали выпускать. А пока, пора спать😀
custom 537056773273762470221custom 54088964246140614637custom 54111631837988352026
— Мы готовы. А вы? 🔘Если вы готовы, окей, сегодня стартуем значит🍸
custom 537056773273762470233custom 540916806411566592220custom 540889642461406146314custom 54070457489760181455
😀Итоги будут веселые, без этого никак, увы. — Кто понял, тот понял. Акцент сделать на - "любые попытки манипуляции результатами"
custom 537056773273762470218custom 540916806411566592214custom 540704574897601814513custom 54088964246140614634
🤫💸
custom 541116318379883520224custom 540704574897601814520custom 540916806411566592218
Showing the 12 most recent of 19 posts we hold for @huskyyytalks. 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Huskyyy Talks!” (@huskyyytalks), 342 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/huskyyytalks.
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.