Telegram RegisterThe public register of Telegram
Telegram profile photo for Fishki.net

Channel

Fishki.net

@fishechki

Verified by Telegram

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

25,904subscribers

-316 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001383956225
TypeChannel
Username@fishechki
Description@fishechki - официальный канал Fishki.net в Telegram. № 4796396466 По вопросам рекламы: [email protected] Наш чат: https://t.me/fishkinetchat Включена РКН в перечень персональных страниц: https://clck.ru/3M5jYg
Created8 November 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/fishechki

Topic

Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 why it has no browse page of its own yet.

Growth

25,90426,22026,0626 August 2026 — 26,220 subscribers6 August 2026 — 26,214 subscribers7 August 2026 — 26,210 subscribers8 August 2026 — 26,200 subscribers9 August 2026 — 26,188 subscribers10 August 2026 — 26,182 subscribers11 August 2026 — 26,170 subscribers12 August 2026 — 26,161 subscribers13 August 2026 — 26,158 subscribers14 August 2026 — 26,150 subscribers16 August 2026 — 26,139 subscribers17 August 2026 — 26,133 subscribers18 August 2026 — 26,131 subscribers19 August 2026 — 26,127 subscribers20 August 2026 — 26,122 subscribers21 August 2026 — 26,114 subscribers22 August 2026 — 26,102 subscribers24 August 2026 — 26,088 subscribers25 August 2026 — 26,075 subscribers26 August 2026 — 26,068 subscribers27 August 2026 — 26,064 subscribers29 August 2026 — 26,060 subscribers30 August 2026 — 26,053 subscribers31 August 2026 — 26,047 subscribers1 September 2026 — 26,042 subscribers2 September 2026 — 26,039 subscribers3 September 2026 — 26,032 subscribers5 September 2026 — 26,018 subscribers9 September 2026 — 25,993 subscribers11 September 2026 — 25,979 subscribers13 September 2026 — 25,965 subscribers14 September 2026 — 25,952 subscribers16 September 2026 — 25,944 subscribers18 September 2026 — 25,939 subscribers25 September 2026 — 25,904 subscribers6 August 202625 September 2026
35 measurements spanning 50 days, net -316. 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 25,857–26,267 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
25 Sept 2026, 06:1825,904-35
18 Sept 2026, 21:5925,939-5
16 Sept 2026, 16:5925,944-8
14 Sept 2026, 23:1625,952-13
13 Sept 2026, 09:1425,965-14
11 Sept 2026, 14:3625,979-14
9 Sept 2026, 00:0025,993-25
5 Sept 2026, 14:1526,018-14
3 Sept 2026, 15:4126,032-7
2 Sept 2026, 07:0826,039-3
1 Sept 2026, 06:1426,042-5
31 Aug 2026, 05:5426,047-6
30 Aug 2026, 07:1326,053-7
29 Aug 2026, 09:2826,060-4
27 Aug 2026, 05:5326,064-4
26 Aug 2026, 04:5426,068-7
25 Aug 2026, 08:2526,075-13
24 Aug 2026, 05:5726,088-14
22 Aug 2026, 14:4726,102-12
21 Aug 2026, 08:3526,114first reading

Engagement

542 posts held, back to 5 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 67 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.78%
avg views ÷ 25,904 subscribers
Avg views / post
2,020
142 posts measured
Reaction rate
1.36%
reactions ÷ views · ER floor
Posts in window
142
of 542 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 141 of 142 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 30 September 2026
Posts held542 (5 August 2026 – 30 September 2026)
Views total286,356
Reactions total3,889
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Sept 2026, 15:38 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

Photos
≈5,000
Videos
≈15,800
Links
≈1,460

Lifetime counters from Telegram’s own channel header, read 30 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
5h 13m
Average length
38s

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

Reaction mix

16,702 reactions across 535 posts, in 46 distinct kinds. The most used accounts for 39.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁6,64639.8%
🔥1,97511.8%
🤣1,5339.18%
👍9455.66%
❤6994.19%
💩5563.33%
🤪4982.98%
🥰4562.73%
💯4002.39%
🤮3872.32%
😱3722.23%
👏2711.62%
👀2491.49%
🤡2471.48%
👎1901.14%
💊1290.772%
🤯1270.76%
🎉1030.617%
😢880.527%
🥴860.515%
26 further kinds7454.46%

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 537 of the 542 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 16,702 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 542 most recent posts we hold, published 5 August 2026 to 30 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.

Recent posts

30 Sept 2026, 15:01 UTC390 views9 reactionsread 30 September 2026
Video

Подборка наказаний рабов их хозяевами

😁5🤬3👎1

30 Sept 2026, 14:01 UTC785 views14 reactionsread 30 September 2026
Video

Кто-то рискует остаться с обссанными тапками

🤪9🤡2👍1😁1😈1

30 Sept 2026, 13:03 UTC≈1,030 views14 reactionsread 30 September 2026
Video

Он теперь на работу пешком приходить будет

👎11🤡2🤮1

30 Sept 2026, 12:01 UTC≈1,220 views33 reactionsread 30 September 2026
Video

У продавьца был один шанс выкрутиться и он им воспользовался

🤣26😁3❤2🥱2

30 Sept 2026, 11:01 UTC≈1,390 views12 reactionsread 30 September 2026
Video

Шизовая реклама кофе из 60-х годов

😁10😎2

30 Sept 2026, 10:01 UTC≈1,410 views17 reactionsread 30 September 2026
Video

Если будет всё время отворачиваться, то он никогда не донесет её

😁14👎3

30 Sept 2026, 09:04 UTC≈1,540 views19 reactionsread 30 September 2026
Video

POV: закончились лимиты на токен и ты перешел на бесплатную версию

😁17👎2

30 Sept 2026, 08:05 UTC≈1,610 views30 reactionsread 30 September 2026
Video

Коллекция винтажных зажигалок

🔥27👍2❤1

30 Sept 2026, 07:02 UTC≈1,730 views36 reactionsread 30 September 2026
Video

Диснейленд в России

😁30🤮5👎1

30 Sept 2026, 05:01 UTC≈2,090 views29 reactionsread 30 September 2026
Video

Доброе утро, страна! Итак, давайте разбираться, кто должен пропустить

😁15💩10❤2👍1👏1

29 Sept 2026, 19:01 UTC≈2,310 views37 reactionsread 30 September 2026
Video

Первая ласточка. Вот они охренеют скоро 😂

😁24👏10❤1💩1🤗1

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

Forward network

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.

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

“Fishki.net” (@fishechki), 25,904 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/fishechki.

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.