10 дней тренировок, а запас еды на все 50 😁
🔥50👍19😁4❤1🆒1

Channel
@elfishing
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry
10,507subscribers
+59 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001774346530 |
|---|---|
| Type | Channel |
| Username | @elfishing |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/elfishing |
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 04:39 | 10,507 | +9 |
| 11 Sept 2026, 08:40 | 10,498 | +25 |
| 8 Sept 2026, 11:57 | 10,473 | -1 |
| 5 Sept 2026, 06:40 | 10,474 | -3 |
| 3 Sept 2026, 13:16 | 10,477 | +5 |
| 2 Sept 2026, 06:55 | 10,472 | +2 |
| 31 Aug 2026, 04:06 | 10,470 | +2 |
| 30 Aug 2026, 02:55 | 10,468 | -1 |
| 29 Aug 2026, 00:43 | 10,469 | +8 |
| 28 Aug 2026, 00:08 | 10,461 | +1 |
| 26 Aug 2026, 02:17 | 10,460 | -3 |
| 25 Aug 2026, 02:38 | 10,463 | -2 |
| 23 Aug 2026, 16:56 | 10,465 | -1 |
| 22 Aug 2026, 03:07 | 10,466 | -2 |
| 20 Aug 2026, 17:37 | 10,468 | -1 |
| 19 Aug 2026, 15:05 | 10,469 | -1 |
| 17 Aug 2026, 10:15 | 10,470 | +2 |
| 15 Aug 2026, 17:51 | 10,468 | +3 |
| 14 Aug 2026, 07:17 | 10,465 | +7 |
| 12 Aug 2026, 21:38 | 10,458 | first reading |
22 posts held, back to 20 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 37 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.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 22 (20 July 2026 – 29 August 2026) |
| Views total | 21,720 |
| Reactions total | 627 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 14: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 11 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.
2,739 reactions across 22 posts, in 26 distinct kinds. The most used accounts for 40.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,099 | 40.1% | |
| 🔥 | 859 | 31.4% | |
| 😁 | 252 | 9.20% | |
| ❤ | 191 | 6.97% | |
| 👏 | 164 | 5.99% | |
| 🏆 | 95 | 3.47% | |
| ⚡ | 11 | 0.402% | |
| 🤝 | 11 | 0.402% | |
| 💯 | 9 | 0.329% | |
| 👀 | 7 | 0.256% | |
| 🫡 | 7 | 0.256% | |
| 😱 | 6 | 0.219% | |
| ✍ | 4 | 0.146% | |
| ❤🔥 | 4 | 0.146% | |
| 🎉 | 4 | 0.146% | |
| 🤣 | 4 | 0.146% | |
| 🍾 | 2 | 0.073% | |
| 👌 | 2 | 0.073% | |
| 🆒 | 1 | 0.037% | |
| 💘 | 1 | 0.037% | |
| 6 further kinds | 6 | 0.219% |
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 22 of the 22 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 2,739 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 20 July 2026 to 29 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.
10 дней тренировок, а запас еды на все 50 😁
🔥50👍19😁4❤1🆒1
А вот уже и второй этап 😎 Начинаем подготовку! ✊️ #PAL #teammida #harlovs
👍87❤25🔥24👀1😁1
Полезно сделать забросик перед сном)
👍75🔥26❤7👏3😁1
5) Есть места, где рыбу не увидишь ни в один прибор. Это густые коряжники, изрезанный рельеф, перепады глубин и пересечения данных факторов. Значит мы должны найти активную рыбу приманкой. Для этого брали 110 поролонку APS с прижатыми крючками и проходящим коряги грузиком. Если соберетесь в те края летом, берите на вооружение! 😉🤝 #teammida #harlovs #DAIWA #PAL #Чебоксарка
🔥46👍29🤝4❤2
Пару слов о прошедшем турнире BetBoom PAL 2026. Ограниченная зона ловли в разрезе соревнований и катострофическая нехватка времени заставляют быстро принимать решения и избирательно подходить к поиску хищника, постоянно делая корректировки с поправкой на новые вводные. День сурка. В 21ч заканчиваем тренировку и причаливаем, оперативно засыпаем, а в 6ч мы уже в лодке на ходу чистим зубы, умываемся и готовимся к завт…
🔥32❤18👍13🏆5✍3👏1
СТУКАНУЛ ДВИЖОК. Щука-попрыгунья и КУЛЬБИТ ЕЛИСЕЕВА | Первый этап BETBOOM PAL 2026 Выступление экипажа Андрея Питерцова и Дмитрия Елисеева на Первом этапе BETBOOM PAL 2026. 🎥 В этом фильме вы узнаете о подготовке к турниру, проблемах с мотором, интересных подробностях туров, том самом эпизоде с вылетевшей из подсака щукой и, конечно же, акробатических навыках Димы. 📺 Смотреть на VKВидео 📺 Смотреть на YouTube 📺 Смо…
👍44❤5🔥5🏆3😢1
Пришло время намотать свежачка. Пару слов о выборе шнура.
🔥55👍27⚡4❤2🏆2👏1
Если давно присматривались к NorthSilver, сейчас хороший момент вернуться к этому вопросу. Ребята из Рыбанутые.РФ продлили скидку 20% на ВСЕ лодки NorthSilver из наличия до 30 августа 2026 года. Производители лодок такого уровня нечасто дают подобные скидки, тем более сразу на весь модельный ряд из наличия - успевайте. Сейчас доступно более 15 корпусов! Есть разные модели и варианты под разные задачи: от рыбалки д…
👍11🔥10❤7
Frapp Rowdy Head — птица или все-таки мышь? 🧐 "Как-то в лодке с Андрюхой мы размышляли о данной приманке, и напарник выдал очень интересную мысль — при рывковой анимации под водой лохматый ведет себя как мелкая птица, которая отталкивается лапками. Согласитесь, похоже на правду? Хотя щука не прочь полакомиться и грызунами, но тут все же про отталкивания и гидроудар. Плюс перфорированная голова у Rowdy Head дает боль…
👍62🔥29❤11🏆4👏1💯1🤗1
👀Самая эпичная досрочка Третьего тура Первого этапа BETBOOM PAL 2026😱 📣 Чат для болельщиков #АльфаБанк #BETBOOM #Ситидрайв #KGM #Битрикс24 #ВКСпорт #ФабрикаЛодок #Harlovs #ПроЛодки #MFBoats #ПрактикПро #DapDrift #Рыбомания #ArdorFishing #ROIX #FRAPP #KEITECH #Decoy #Ares #MIDAGroup #PAL2026
🔥170😁39👏10👍8❤6💘1💯1
Нужно уметь держать удар. Все спортсмены рано или поздно сталкиваются со сложностями. Естественно, подавляющее число проблем происходит именно в туре, когда никто не жалеет ни себя, ни технику и нацелен на максимальный результат. Если произошел форс-мажор, то следует сохранять хладнокровие и решать ситуацию быстро и максимально эффективно. Чебоксарка вновь не дала нам спокойной жизни.. Поломка мотора в туре, невозм…
👍268❤50🏆38🔥29👏20😁15🤝3😱3
Дорогие зрители турнира BetBoom PAL 2026, спасибо за то, что выступили за запрет лайвсонаров! Благодаря этому у нас хоть и на один денек, но появилась возможность спокойно насладиться природой, не нагружать голову количеством информации и уберечь от избыточного потребления и без того загруженный катер. А завтра вновь напрягаемся, ищем и ловим вприглядку. Хоть это и очень сложный процесс, но интересный и крайне инфо…
👏86😁36👍32🏆10❤8🔥5❤🔥4⚡1
Showing the 12 most recent of 22 posts we hold for @elfishing. 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.
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 3 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“EliseevFishing” (@elfishing), 10,507 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/elfishing.
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.