Telegram RegisterThe public register of Telegram
Telegram profile photo for Рыбалка с РЫБКОМ. Рыболовный компас

Channel

Рыбалка с РЫБКОМ. Рыболовный компас

@fishcomonline

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

24subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001409230287
TypeChannel
Username@fishcomonline
CreatedBetween 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live2 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 2 October 2026
On Telegramt.me/fishcomonline

Topic

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 1 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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

242524.57 August 2026 — 25 subscribers11 August 2026 — 25 subscribers16 September 2026 — 24 subscribers7 August 202616 September 2026
3 measurements spanning 39 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 24–25 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 07:1824-1
11 Aug 2026, 10:0425no change
7 Aug 2026, 21:0825first reading

Engagement

20 posts held, back to 29 January 2023 — 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 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 18 July 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

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

Measured over the 20 most recent posts we hold, published 29 January 2023 to 18 July 2023, 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

18 Jul 2023, 09:40 UTCviews —

The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

7 Jul 2023, 08:36 UTCviews —

The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

3 Feb 2023, 16:56 UTC278 views1 reactionsread 11 August 2026

Итоги работы рыбоохраны в 2022 году Рубрика: #рыбком_закон Инспекторы рыбоохраны во внутренних водоемах Российской Федерации в 2022 году выявили более 86,66 тыс. нарушений С учётом поступлений за прошлые периоды, общая сумма взысканных штрафов составила 137 млн 557 тыс. рублей — показатель взыскания вырос с 78% до 82% по сравнению с 2021 годом. Общая сумма взысканных штрафов (без учёта сумм поступлений за прошлые п…

❤1

2 Feb 2023, 17:18 UTC219 viewsread 11 August 2026

Кубок Кузбасса по ловле на мормышку со льда пройдет 4-5 февраля 2023 года Рубрика: #рыбком_спорт Федерация рыболовного спорта Кузбасса объявила о проведении Кубка Кузбасса по спортивной ловле рыбы на мормышку со льда, который пройдет 4-5 февраля 2023 года, на Беловском водохранилище. Соревнование проводится в соответствии с Правилами вида спорта «рыболовный спорт», утверждённый приказом Министерства по физической …

1 Feb 2023, 17:14 UTC115 viewsread 11 August 2026

Выезжающих на морской лед рыбаков будут крупно штрафовать за нарушение режима водоохранной зоны Рубрика: #рыбком_закон Многие рыбаки, пересекая морскую рыбоохранную зону, выезжают на лёд, за что им грозит крупный штраф В Приморском крае с продолжением крепких морозов и устойчивым ледовым покрытием прибрежных морских акваторий активно продолжается сезон зимней рыбалки. Сотни рыбаков-любителей ежедневно выходят на л…

1 Feb 2023, 17:02 UTC77 viewsread 11 August 2026

На Камском водохранилище поймали браконьеров Рубрика: #рыбалка_происшествия Нарушители возместят ущерб рыбным запасам почти в 328 тысяч рублей Сотрудники рыбоохраны по Пермскому краю Волго-Камского территориального управления Росрыболовства во время патрулирования Камского водохранилища обнаружили двух рыбаков, которые нелегально ловили рыбу сетями. У браконьеров изъяли две сети, два снегохода, 237 кг рыбы: 212 э…

31 Jan 2023, 17:49 UTC74 viewsread 11 August 2026

С 1 февраля в заказнике «Устье реки Мёши» вводится запрет на рыбалку рубрика: #рыбком_водоемы С 1 февраля по 15 апреля на территории «Устье реки Меши» вводится запрет на промысловую и любительскую рыбалку Госкомитет Республики Татарстан по биоресурсам сообщает, ограничения вводятся с целью создания устойчивой популяции рыбы и благоприятных условий для ее воспроизводства. В целях профилактики и недопущения правонар…

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

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

“Рыбалка с РЫБКОМ. Рыболовный компас” (@fishcomonline), 24 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/fishcomonline.

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.