Дорогие Бхакты, доброе утро. Скоро эфир ВОПРОСЫ-ОТВЕТЫ ( ссылка вопросы-ответы, обратите внимание) Присоединяйтесь🙏🐝
🙏2❤1

Channel
@hrishikeshmaharaj
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
293subscribers
+7 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001171107656 |
|---|---|
| Type | Channel |
| Username | @hrishikeshmaharaj |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 October 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 6 |
| On Telegram | t.me/hrishikeshmaharaj |
Religion — 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 8 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 8 Oct 2026, 06:22 | 293 | no change |
| 6 Oct 2026, 10:35 | 293 | +1 |
| 1 Sept 2026, 13:52 | 292 | +2 |
| 24 Aug 2026, 20:05 | 290 | +1 |
| 16 Aug 2026, 17:27 | 289 | +3 |
| 8 Aug 2026, 02:36 | 286 | first reading |
20 posts held, back to 28 September 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 page 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 8 October 2026 |
|---|---|
| Posts held | 20 (28 September 2026 – 8 October 2026) |
| Views total | 1,529 |
| Reactions total | 189 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Oct 2026, 06:22 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.
Lifetime counters from Telegram’s own channel header, read 8 October 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.
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.
189 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 105 | 55.6% | |
| 🙏 | 68 | 36.0% | |
| 💘 | 11 | 5.82% | |
| 🤗 | 3 | 1.59% | |
| ✍ | 2 | 1.06% |
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 20 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 189 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 28 September 2026 to 8 October 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.
Дорогие Бхакты, доброе утро. Скоро эфир ВОПРОСЫ-ОТВЕТЫ ( ссылка вопросы-ответы, обратите внимание) Присоединяйтесь🙏🐝
🙏2❤1
Дорогие преданные, Сегодня, 8-го октября, приглашаем вас на еженедельное общение в ZOOM с Шрилой Бхакти Севан Хришикешем Махараджем. "ОТВЕТЫ НА ВОПРОСЫ" 7:30 Москва/Киев/Рига 10:00 Навадвип/Вриндаван 11:30 Чианг Май Чтобы подключиться к конференции пишите @jivana_dd и @NatashaShtol ▶️ при входе в ZOOM, пожалуйста, указывайте свои духовные имена. Ждем вас и ваши искренние вопросы!🙏
❤4
💬 Когда мы повторяем Святое Имя, мы на самом деле общаемся непосредственно с Господом. Единственное, почему мы не видим этого, — у нас разные степени загрязнения, разные степени невежества. И вот, скажем, мы говорили о бесах — это самые грубые такие штуки: мы хотим смотреть в одну сторону, а нам говорят: «Нет, не смотри туда, смотри вот сюда», — и они постоянно нас отвлекают. Бесы прежде всего рождаются, входят в на…
🙏7💘4❤3
💬 В конечном итоге мы иногда говорим, что у нас в принципе последняя инстанция. К нам люди приходят, которым уже некуда совсем идти, которые готовы на самом деле посвятить свою жизнь Господу. Пока у человека есть надежда на таблетки, на мясо, на дыхание, на мистическую йогу, неважно на что, пока есть надежда, —зачем приходить к преданным? Если приходить со своими идеями, то это все равно не поможет. А наша идея очен…
🙏12❤5
6 октября (вторник) Индира экадаши. Пост. 7 октября (среда) Паран 06:43 — 10:25 (мск) / 06:19 — 10:08 (Сухум) / 07:18 — 10:56 (Санкт-Петербург). 📖 Шри Индира Экадаши 📆 Вайшнавский календарь #вайшнавскийкалендарь #экадаши
❤7🤗3💘1
Зум 13-го августа 2026
❤5✍1
На духовном уровне, всегда в центре стоит то, что от меня хотят, что на самом деле от меня ждут мои старшие, мои Покровители. Если мы пытаемся увидеть эту связь с Высшим миром, то мы рано или поздно увидим это. Мы увидим, как всё это взаимосвязано, и единственное, что мешает, это наша собственная, скажем, духовная неквалификация. Вопросы и ответы 17.09.26 #духовность #связь #старшие
🙏10✍1❤1
Шримад-Бхагаватам Песнь Первая. Глава 9 "Уход Бхишмадевы в присутствии Господа Кришны" 00:02:03 О важности 8 главы для понимания вайшнавской традиции 00:03:58 Об уходе Бхишмадевы 00:07:02 Глава 9 тексты 1-8 с комментариями А.Ч. Бхактиведанты Свами и пояснениями Махараджа. 00:46:56 Вопрос: ощущение ананды (блаженства) в сердце — свойство души или милость Господа? ❗Все эфиры по Шримад-Бхагаватам теперь можно послуша…
❤4
Дорогие бхакты! Сегодня, 4 октября в 8:00 (мск) приглашаем вас присоединиться к циклу лекций Шрилы Бхакти Севан Хришикеша Махараджа по «Шримад-Бхагаватам». Чтобы подключиться к конференции Zoom пишите: @jivana_dd ▶️ при входе в ZOOM, пожалуйста, указывайте свои духовные имена. Ждем вас!🙏
❤6
Духовность — это исключительно, когда мы идём против своей материальной природы, в том смысле, что мы не наслаждаемся этим материальным телом, а пытаемся тело задействовать в служении. Если тело для нас как инструмент для нашего собственного обустройства в этом материальном мире в попытках наслаждаться, тогда это все —иллюзии. Вопросы и ответы 17.09.26 #духовность #тело #инструмент #служение
🙏18
Изучение "Шримад-Бхагаватам", 30 августа 2026.
🙏8
00:04:08 Перевод «Бхулийа томаре» из Шаранагати Бхактивинода Тхакура 00:05:58 Шаранагати — основа нашего духовного продвижения ❓ 00:17:18 Что такое хорошо и что такое плохо с точки зрения Сознания Кришны? Мирская забота родителей — это иллюзия? ❓ 01:00:24 Если сам заболел, что делать? Пытаться продлить жизнь или принять волю Всевышнего? ❓ 01:07:41 Вопрос о страдании святых людей. Как привести в гармонию, что самы…
❤7
Showing the 12 most recent of 20 posts we hold for @hrishikeshmaharaj. 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.
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.
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.
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“Шрила Б. С. Хришикеш Махарадж” (@hrishikeshmaharaj), 293 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/hrishikeshmaharaj.
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.