WANT THIS PFP ๐ RECAT HERE ๐
โค3
Signed โโ๐๐๐๐

Channel
@hawkkeyyfx
On this record: Topic ยท Previous handles ยท Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Polls ยท Citations ยท Handles named that no longer answer ยท Cite this entry
734subscribers
+547 since we began measuring on 9 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1003755260992 |
|---|---|
| Type | Channel |
| Username | @hawkkeyyfx |
| Created | Between 1 February 2026 and 31 July 2026 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/hawkkeyyfx |
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 61% 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.
@hawkkeyyfx 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 |
|---|---|---|
| 9 Nov 2026, 12:49 | 734 | +5 |
| 9 Nov 2026, 01:22 | 729 | no change |
| 9 Nov 2026, 00:47 | 729 | +486 |
| 17 Aug 2026, 19:38 | 243 | +55 |
| 10 Aug 2026, 00:01 | 188 | +1 |
| 9 Aug 2026, 20:17 | 187 | first reading |
40 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 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days ยท latest post in window 8 November 2026 |
|---|---|
| Posts held | 40 (4 August 2026 โ 8 November 2026) |
| Views total | 1,447 |
| Reactions total | 28 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 9 Nov 2026, 01: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 6 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.
56 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 69.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 39 | 69.6% | |
| ๐ฅ | 11 | 19.6% | |
| ๐ | 3 | 5.36% | |
| โก | 2 | 3.57% | |
| ๐ฅฐ | 1 | 1.79% |
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 15 of the 40 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 56 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 40 most recent posts we hold, published 4 August 2026 to 8 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: 1 of 20 posts held from the last 30 days (5.00%) 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).
WANT THIS PFP ๐ RECAT HERE ๐
โค3
Signed โโ๐๐๐๐
On this post?
Signed FOXY CC
Reacts?
โค1
Signed FOXY CC
Want this basic spiderman outroโจ? Qr after 6 reactsโค๏ธโฃ๏ธ Made In :- AMZ ๐ฅ Made By :- @FOXYBROSUNO๐ NOTE :- GIVE CREDIT TO ME { @FOXYBROSUNO } IF YOUR NOT USING THIS JUST FOR YOUR PERSONAL USE ๐ ( I DON'T KNOW IF YOU WILL USE IT REALLY OR NOT)
โค1
Signed FOXY CC
DIWALI SPECIAL MALHARI MEP ๐ฅ[AMV/EDIT] 4K ?. See here
Signed ๐ชโโฏ๐๐ถโโฏ ๐ซ๐โฏ๐โฏ๐๐
๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐๐ ๐๐ ๐๐๐๐ ๐๐๐๐๐๐๐ โ๏ธ ๐ ๐๐๐๐๐๐๐ ๐ ๐๐๐ ๐๐๐๐ ๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐ ๐๐๐๐... โก
Admins required for this channel Any interested dm @edittuber_201
Signed Ed. brand ONLY โค๏ธ๐
๐๐๐๐๐๐ ๐๐๐๐๐๐๐ ๐๐ ๐๐๐๐๐๐๐ ๐๐๐ฏ ๐๐๐๐ ๐๐๐๐ ๐๐ ๐๐๐๐ ๐๐ ๐ ๐๐๐๐ ๐๐ ๐๐๐๐๐๐ ๐ ๐๐ ๐๐๐ โก ๐๐๐๐๐๐ ๐๐๐๐ ๐๐๐๐ ๐๐ ๐๐๐๐ ๐๐๐๐ ๐๐ : ๐๐
โค10๐ฅ3๐ฅฐ1
๐ชโจ Happy Diwali! Wishing you happiness, success, and blessings. ๐ Thank you for your continued support. โค๏ธ Keep thriving and stay positive. ๐
๐ช๐๐ก๐ง ๐ง๐๐๐ฆ ๐๐ข๐๐จ ๐ฃ๐๐ฃ ๐ ๐๐ข๐ ๐ฃ๐๐๐ง๐ ๐ด ๐ฅ๐๐๐๐ง๐ฆโก ๐ง๐๐๐ฅ๐ ๐ช๐๐๐ ๐๐ ๐ข๐ก๐ ๐๐จ๐๐๐ฌ ๐ช๐๐ก๐ก๐๐ฅ ๐ค ๐ฅ๐๐๐๐ง - ๐๐๐ฅ๐
โค3๐1
May this Diwali bring you the warmth of glowing diyas, the sweetness of festive mithai, and the joy of being surrounded by family and friends. May Goddess Lakshmi bless your home with prosperity, peace, and endless happiness, and may every lamp you light bring new hope, success, and beautiful beginnings. Wishing you laughter brighter than fireworks, a heart full of gratitude, a table full of love, and a year ahead fiโฆ
Signed ๐ชโโฏ๐๐ถโโฏ ๐ซ๐โฏ๐โฏ๐๐
Am** (New One)
Signed SAMHX
Showing the 12 most recent of 40 posts we hold for @hawkkeyyfx. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A pollโs figures keep moving after that, so each one is dated.
๐๐๐๐ ๐๐๐๐ ๐๐ ๐๐๐๐ ๐๐๐ ๐๐๐๐๐
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only โ there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each optionโs share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each optionโs own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 40 most recent posts we hold, published 4 August 2026 to 8 November 2026. Telegram labels each poll by kind โ an anonymous poll, a quiz, a closed set of final results โ and that label is reproduced rather than paraphrased.
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.
@hawkkeyyfx named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant โ a genuine, evidenced change, not an inference from absence.
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 9 November 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐ผ๐๐ ๐๐โ (@hawkkeyyfx), 734 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/hawkkeyyfx.
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.