Telegram RegisterThe public register of Telegram

Channel

Хижина Охотника 🐺

@hunter_spamit

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

3,304subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002424579885
TypeChannel
Username@hunter_spamit
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/hunter_spamit

Growth

3,3043,3063,3057 August 2026 — 3,305 subscribers7 August 2026 — 3,305 subscribers8 August 2026 — 3,306 subscribers11 August 2026 — 3,304 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,304–3,306 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 11:163,304-2
8 Aug 2026, 05:553,306+1
7 Aug 2026, 13:303,305no change
7 Aug 2026, 12:483,305first reading

Engagement

19 posts held, back to 19 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
48.0%
avg views ÷ 3,304 subscribers
Avg views / post
1,590
11 posts measured
Reaction rate
0.93%
reactions ÷ views · ER floor
Posts in window
11
of 19 held

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 11 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held19 (19 June 20266 August 2026)
Views total17,461
Reactions total140
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:29 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.

What this channel posts

Video runtime
18s
Average length
18s

Measured directly from 1 video 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.

Reaction mix

225 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 45.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10345.8%
😁7432.9%
🤬114.89%
🤯114.89%
😱94.00%
🐳73.11%
👍52.22%
🤝31.33%
🔥20.889%

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 225reactions 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 19 June 2026 to 6 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.

Recent posts

6 Aug 2026, 13:18 UTC720 viewsread 7 August 2026

Аа, там ещё делистинг с Банана завтра Останется ББ, который выкрутит почасовку околоЖБ и лоуликвидные помойки по типу Гейта, Кукоина и Битгета Если порвут ещё раз — возьму под флип, держать до миграции (которая непонятно как пройдёт и сколько по времени это займет) выглядит менее вкусно

6 Aug 2026, 13:05 UTC751 views3 reactionsread 7 August 2026

11 Августа в 16:00 по Киеву проведут миграцию токена $VANRY Пока заливаться не буду, сидеть в позе неделю + фандос выкрутят ЖБ, кто на яйцах можете флипать/заходить в 100% уже сейчас https://x.com/Vanarchain/status/2085350480914284673?s=20 https://koshiktools.com/spreads?c=binance~vanryusdt~gate_spot~vanryusdt

3

1 Aug 2026, 13:02 UTC≈1,520 views21 reactionsread 7 August 2026
Photo

Хочу попробовать себя в новой рубрике — обзоры на полезные тулсы, приватки/сайты для криптанов (как от инфлов так и нет) Первым постом решил сделать обзор на сайт моего кореша — koshiktools.com, в двух словах это сайт для слежки за спредами с полезными фишками, есть как бесплатная так и платная версия сайта с расширенными возможностями Плюсы: ⚪️Можно открывать до 3-х вкладок одновременно (в Pro неограниченное кол-

9👍5😁5🔥2

26 Jul 2026, 20:20 UTC≈1,600 views10 reactionsread 7 August 2026

$SIREN — 200, на чем еще можно подзаработать? С последнего поста про $SIREN я забрал ещё +1.5к$ с фандоса, тотал вышел ~2к$ за 1.5месяца — очень вкусный пассив вышел Следующая на очереди отработка по $VANRY — все видели и слышали, через 2 дня пройдёт миграция и спред Гейт/Фьючи должны сравнять, но это всё идеально на бумаге, как оно будет на самом деле никто не знает, я захожу ведь корабль с Ганвестом не тонет Ами

😁82

22 Jul 2026, 09:44 UTC≈2,180 views9 reactionsread 7 August 2026

Кому BingX не вывел — 99% спишут профит 😵

7🤬2

22 Jul 2026, 04:47 UTC≈2,080 views10 reactionsread 7 August 2026
Photo

Ааа, я вас понял Поддержка пишет "аномалий в фандинг не наблюдается", ало клоуны у вас индекс на 15% ниже, а вы ставите -1% и почасовку на АКЦИЮ Отдал весь профит с $BNC, пошли они нахуй

🤬9🤯1

21 Jul 2026, 21:35 UTC≈1,810 views5 reactionsread 7 August 2026

А $FWDI на мексе будет падать или он рот ебал, есть инфа? Конторка сначала режет сайзы, а потом пушит пустые стаканы что бы ликвиднуть нас, честных и простых рабочих

5

20 Jul 2026, 09:33 UTC≈1,700 views43 reactionsread 7 August 2026
Photo

Спустя месяц расскажу вам историю как я оказался заложником 👮 Началось всё 25.06.2026 с рага $M, тогда можно было погонять любой спот на Мекс в 10% профита даже с хеджом на фьючах, очевидно я сидел думал "а надо оно вообще" и решил прогнать с Гейта на Мекс В депозитах на Мекс вижу обработку платежа 8/110 которая перестала двигаться, обновляю страницу а депозиты уже закрыты, быстро пытаюсь отменить депозит и пишу в

24🤯10🐳5😁4

19 Jul 2026, 20:16 UTC≈1,570 views11 reactionsread 7 August 2026
Photo

Разблядовочка по "ЛФЧ" с Allbridge В 17:51 фреш-кош взял флеш-лоан (займ на одну транзу) в рамзере 1.1млн USDC в SOL —> серией свапов в минус он наебал Allbridge каким-то образом (мб обчистил пул, нашел баг в бридже и т.д.) —> и последним свапом получил те самые 3.9к$ -> 948к$ Тем самым тип заработал 1.66млн$ чистыми за одну серию свапов, после этого что бы выровнять пул начали заимствовать ликву с других пулов (эт

11

14 Jul 2026, 15:52 UTC≈1,850 views28 reactionsread 7 August 2026

"У тебя ТВХ в спреде 16%, а у меня 8% — но по факту мы оба раздеты"

😁253

25 Jun 2026, 16:01 UTC≈2,800 views23 reactionsread 7 August 2026

Мекс не рассчитал масштаб заблокированных средств за $ZENT и обнулился 🕯

😁23

Showing the 12 most recent of 19 posts we hold for @hunter_spamit. 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.

Citation-graph rank

Citation-graph rank — 221,296 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

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.

Cite this entry

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 August 2026 — this entry's latest reading, not the date you are reading this.

“Хижина Охотника 🐺” (@hunter_spamit), 3,304 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/hunter_spamit.

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.