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 94% 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
14 measurements spanning 50 days, net +193. 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 8,661–8,912 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
25 Sept 2026, 23:35
8,883
+95
15 Sept 2026, 06:21
8,788
+6
11 Sept 2026, 15:16
8,782
+14
7 Sept 2026, 02:21
8,768
+11
2 Sept 2026, 06:42
8,757
-7
29 Aug 2026, 20:25
8,764
+11
27 Aug 2026, 00:04
8,753
-7
24 Aug 2026, 09:26
8,760
+19
21 Aug 2026, 02:13
8,741
+14
17 Aug 2026, 15:55
8,727
+7
14 Aug 2026, 15:06
8,720
+1
10 Aug 2026, 22:53
8,719
+21
8 Aug 2026, 08:05
8,698
+8
7 Aug 2026, 11:17
8,690
first reading
Engagement
107 posts held, back to 6 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 28 pages 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 107 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
47s
Average length
16s
Measured directly from 3 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
679 reactions across 95 posts, in 16 distinct kinds. The most used accounts for 34.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
232
34.2%
👍
210
30.9%
🔥
183
27.0%
👏
12
1.77%
🥴
12
1.77%
🏆
11
1.62%
😢
4
0.589%
😁
3
0.442%
🤝
3
0.442%
🙈
2
0.295%
🥰
2
0.295%
🐳
1
0.147%
👌
1
0.147%
🤔
1
0.147%
🤪
1
0.147%
🤯
1
0.147%
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 95 of the 107 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 679 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 107 most recent posts we hold, published 6 August 2026 to 28 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.
Advertising
Ad load
1.87%
2 of 107 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
698
over 2 measured posts
Median views · rest
674
over 105 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2W5zFGzEnth
1
11 August 2026
11 August 2026
2W5zFJdDhxm
1
9 August 2026
9 August 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 107 most recent posts we hold, published 6 August 2026 to 28 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
🗓 25.08.26
🌊 р. Ока
🎣 Спиннинг
➖
В очередной раз выбрались на Оку половить окуня с дочкой🎣!
Точки домашние, поэтому хорошо знакомые, правда ветер был не совсем подходящий для ловли с нашего берега.
Перебор приманок дал свои плоды🐟, на этот раз окунь клевал исключительно на креатуру личинки стрекозы, причём, у дочки клевал даже на приманку без головы, которую разбили меленькие полосатики🤭.
Все окуньки благополучно упл…
🗓 23.08.26
🌊 р. Ока
🎣 Фидер
➖
Наконец-то долгожданная рыбалка, после длительного перерыва, на реке Ока. Место очень востребовательное, поэтому выезд планирую с вечера. Собираю вещи и в дорогу. Пока ехал, перебрал все другие варианты с другими локациями на случай, если будет занято запланированное место. Приехав на место, вижу, что весь берег занят, но прокатившись между машинами и палатками других рыбаков, нахожу оче…
🗓️ 25.08.26
🌊 Москва река
🎣 Спиннинг
➖
📱 Автор: Константин Кузьмин
➖
Лет десять-пятнадцать назад крэнки были на Москве-реке самым эффективным типом окуневых приманок с июля по сентябрь. Теперь они лишь на третьих ролях после тейл-спиннеров и джиг-рига.
🐟 Отчёты МСК / 💬 Форум
➖
#спиннинг #москварека
источник
🗓 27.08.26
🌊 Джамгаровский пруд
🎣 Спиннинг
➖
👨💼 Отчёт от подписчика
➖
Тейл спинер от кдф 5грамм
Пришли в 9, первая поклевка в 9.40
Щука взяла в 10 под берегом после паузы и ушла в кусты где на себя намотала килограмма полтора водорослей
55см 1,1 кг
🐟 Отчёты МСК / 💬 Форум
➖
#спиннинг #джамгаровскийпруд
🗓 23.08.26
📍 Московская область
🎣 Спиннинг
➖
В этот выезд был в другом конце вдхр. Гонялся за сомами, но усатый был таков. С судаком в этой части посложнее, и размер поменьше. Самый большой был 3950гр.
🐟 Отчёты МСК / 💬 Форум
➖
#спиннинг #московскаяобласть
источник
🗓 23.08.26
🌊 р. Ока
📍 Таруса
🎣 Спиннинг
➖
Хотел поймать жереха, попались щуки. Щука на 2.3кг, шнурка просто сфоткал и скинул обратно)
➖
📍 На карте 👈 Таруса
🐟 Отчёты МСК / 💬 Форум
➖
#спиннинг #ока #таруса #яндекслокация
источник
🗓 23.08.26
📍 Москва (в черте города)
🎣 Спиннинг
➖
Интересный опыт ловли прудового жереха.
Побывав на шабаше Константина Евгеньевича Кузьмина в начале августа познакомился ближе с интересной акваторией, а именно городским прудом, где достаточно жереха, но он не так прост. Желающих его поймать там хоть отбавляй, но далеко не всем удаётся сразу найти подход к осторожной рыбе, так случилось и у меня. На самом шабаше - …
🗓 Август 2026
🌊 р. Ока
🎣 Спиннинг
➖
Всем привет!
На прошлой неделе я ловил рыбку не только на Москве реке, но и посетил свою любимую Оку.
В последнее время я, как то не спешу к рассвету и возможно зря,) активность в течении светового дня, честно говоря была так себе)!
Прокатился по двум с половиной участкам и на каждом из них, примерно одна и та же картина - рыбка не в количестве есть, но активность так себе…
Примерн…
👍3🔥2❤1
Showing the 12 most recent of 107 posts we hold for @rubalkamoskva. 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.
Mentions
Named by 1 registered channel — 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.
Appears in Telegram’s recommendations for other channels
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.
Рыбацкий канал | Рыбалка @rybalka_kanal_fishing · 107,788 Telegram ranks this channel #3 of 65 here — alongside 64 others — read 14 August 2026
Рыболовная сводка Спб @rybalka_spb_lenoblasti · 38,101 Telegram ranks this channel #6 of 70 here — alongside 69 others — read 1 September 2026
Рыбанутый | Рыбалка @fishercl · 22,168 Telegram ranks this channel #13 of 67 here — alongside 66 others — read 21 September 2026
Простая Рыбалка🐟 @ribalka_prostaya · 151,993 Telegram ranks this channel #26 of 81 here — alongside 80 others — read 12 August 2026
Рыбалка с Петром Миненко @fishing_MINENKO · 28,885 Telegram ranks this channel #29 of 61 here — alongside 60 others — read 9 September 2026
Снасти Здрасьте! @snasti_zdraste · 43,549 Telegram ranks this channel #67 of 76 here — alongside 75 others — read 9 September 2026
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.
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.
“РЫБАЛКА В МОСКВЕ И ПОДМОСКОВЬЕ” (@rubalkamoskva), 8,883 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/rubalkamoskva.
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.