Channel
@f1shkwW
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
865subscribers
+4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002460754199 |
|---|---|
| Type | Channel |
| Username | @f1shkwW |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/f1shkwW |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 17:13 | 865 | +4 |
| 8 Aug 2026, 14:46 | 861 | no change |
| 8 Aug 2026, 10:45 | 861 | first reading |
11 posts held, back to 26 July 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.
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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 11 (26 July 2026 – 7 August 2026) |
| Views total | 5,885 |
| Reactions total | 252 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:45 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 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.
252 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 32.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5316638684555001101 | 82 | 32.5% | |
| custom 5312344632087038010 | 65 | 25.8% | |
| custom 5316804702220862879 | 36 | 14.3% | |
| custom 5210846660732678811 | 33 | 13.1% | |
| custom 5449461939753204225 | 19 | 7.54% | |
| custom 5384138721291420149 | 17 | 6.75% |
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 11 of the 11 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 252reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 26 July 2026 to 7 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.
артики как я и обещал, вы набрали 100+ лайков малатцы завтра будет еще парочку, и возможно сделаю мини лоту на артик для вас. ну а я пошел спать!
custom 521084666073267881123custom 54494619397532042258custom 53166386845550011017custom 53123446320870380102custom 53841387212914201492
вы давайте участвуйте, если наберется много участников будет больше розыгрышей
custom 53123446320870380107custom 53168047022208628793
я на лодачк на ангаре крут класс я видел пять беспилотников пролетающих над нами (наших) вв еще видео лайкните если вы крутые: https://l.likee.video/v/tmRHsi а и если 100 лайков на видео наберется, то я вам сегодня артиков напосщу, делаем?
custom 531234463208703801012custom 53166386845550011017custom 53841387212914201494custom 54494619397532042252
каждый кто прокомментирует это видео получит пилигрим 🐦🦆виноград, яблоки зеленые, сливы https://l.likee.video/v/vulDi2 https://l.likee.video/v/vulDi2 https://l.likee.video/v/vulDi2
custom 531680470222086287912custom 53841387212914201491custom 54494619397532042251
привет ребятки!! я пришел вам напомнить, что у меня можно купить всякие приколюхи, которые вы найдете на втором закрепе жду ваши заказики!
custom 531234463208703801021custom 531663868455500110110custom 54494619397532042254custom 52108466607326788111custom 53841387212914201491
🐠🐠🐠🐠 с первым августа кстати! подкачу вам пост пораньше чтоб поздравить(и погрустить вместе) на заброшке снимал вам видео, щас уже пошли видео с моря, одно ждет уже в лайке, смотрите предыдущий пост. я сейчас нахожусь в иркутской области, город черемхово, а завтра поеду в бухту на байкале - купаться и снимать вам видео! ждемс🐠 ➿➿➿➿➿➿➿ •куда вы ездили этим летом? •арбуз или дыня? ➿➿➿➿➿➿➿ подкатил пост пораньше чтоб…
custom 53123446320870380108custom 52108466607326788113custom 53166386845550011012custom 53168047022208628791custom 53841387212914201491custom 54494619397532042251
у меня наконец то купили эту маску, как вернусь домой выложу новую, папьешку щас могу только похвастаться видео с море, смотрим и лайкаем https://l.likee.video/v/FWh1gS https://l.likee.video/v/FWh1gS https://l.likee.video/v/FWh1gS я верю что завтра будет пост
custom 53123446320870380106custom 52108466607326788111custom 53166386845550011011custom 53841387212914201491
🐠🐠🐠🐠🐠 сюда
custom 531680470222086287916
🐠🐠🐠🐠🐠🐠🐠🐠 —от Майки Уэй! 🐠🐠🐠🐠🐠: призы раздаются по месту победителя - кто первее, тот и выбирает приз. • хвост (рыжий/серый/черный) • основа пластик 3 штуки • мини вентилятор • значки любого фандома (заказать или могу сделать сам) 6шт • бандана (любой цвет) • серьги звезды морские • лианы (зеленые/сакура) • оплачиваю прем на месяц • скидка на маску от меня или любой товар 35% • пушистые гетры белого цвета 🐠🐠🐠🐠🐠🐠🐠 : 1…
custom 531663868455500110125custom 53123446320870380106custom 52108466607326788113custom 53841387212914201493custom 54494619397532042252
ребят, вероятнее всего, переделаю фото-батл в розыгрыш. даты и призы будут те же, но без фото и полный рандом. простите, так вот нужно
custom 531663868455500110118custom 53168047022208628794custom 53123446320870380103custom 53841387212914201493custom 52108466607326788111
ждиье, пять сек и все готово
custom 531663868455500110112custom 52108466607326788111custom 53841387212914201491custom 54494619397532042251
Showing the 11 most recent of 11 posts we hold for @f1shkwW. 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 — 543,435 of 1,481,217entries 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.
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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“𓁺₊ ⊹𝐌𝟏𝐊𝐄𝐘.𝐖𝟖 .𖥔 ݁ ˖” (@f1shkwW), 865 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/f1shkwW.
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.