Channel
@RC_JMTC
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
810subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001240731111 |
|---|---|
| Type | Channel |
| Username | @RC_JMTC |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/RC_JMTC |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 |
|---|---|---|
| 10 Sept 2026, 15:55 | 810 | +3 |
| 31 Aug 2026, 18:48 | 807 | +6 |
| 24 Aug 2026, 13:15 | 801 | -1 |
| 16 Aug 2026, 08:15 | 802 | +2 |
| 8 Aug 2026, 01:35 | 800 | no change |
| 7 Aug 2026, 22:16 | 800 | first reading |
7 posts held, back to 27 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 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 7 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
189 reactions across 7 posts, in 14 distinct kinds. The most used accounts for 32.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 61 | 32.3% | |
| ❤🔥 | 27 | 14.3% | |
| custom 5251369136004539468 | 23 | 12.2% | |
| custom 5235728802142759605 | 22 | 11.6% | |
| custom 5388861626243890161 | 13 | 6.88% | |
| 💔 | 9 | 4.76% | |
| 🦄 | 9 | 4.76% | |
| custom 5235624876819098821 | 5 | 2.65% | |
| custom 5235807206770750407 | 5 | 2.65% | |
| ✍ | 5 | 2.65% | |
| 🐳 | 4 | 2.12% | |
| 🥰 | 3 | 1.59% | |
| 🤓 | 2 | 1.06% | |
| 👍 | 1 | 0.529% |
Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 7 of the 7 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 7 most recent posts we hold, published 27 July 2026 to 7 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.
7 августа — день памяти Михаила Анатольевича Членова (1940–2024), крупного этнографа, востоковеда, создателя Еврейской историко-этнографической комиссии. Сфера его интересов была обширной и включала в себя не только евреев, но главным образом Индонезию и коренные народы севера России. 22 сентября в 19:00 в Кинозале Нового пространства Еврейского музея и центра толерантности мы соберемся на вечер памяти Михаила Члено…
❤12💔9
Одно из наших исследовательских направлений — изучение истории и культуры горских евреев. Уже в четвертый раз мы провели конференцию «На перекрестке культур: евреи Центральной Азии и Кавказа» и наконец-то собрали целый номер журнала🐱 Теперь мы хотим выйти в мир международной науки! Мы ищем переводчика статей с русского на английский. Объем перевода: 13 а.л., сроки работ: сентябрь – октябрь. Стоимость работы: 20 тыс.…
❤6✍4custom 53888616262438901614🤓2🦄2
Закончился июль, а значит, подошла к концу наша активная работа со практикантами этого учебного года 🥸В этом сезоне мы принимали востоковедов ИСАА МГУ, религиоведов РГГУ, историков и искусствоведов из Вышки, а также дистанционно с нами поработала студентка-филолог из Вышки в Санкт-Петербурге. Уф! Вспомним, как это было: по традиции, для всех практикантов мы проводим экскурсии по экспозиции музея и рассказываем о хра…
❤6custom 53888616262438901615🐳4custom 52513691360045394684custom 52358072067707504072
Лето продолжается, а мы напоминаем нашим потенциальным авторам, что до сентября идет прием статей в 5-й номер журнала Newish 👀 Третий номер журнала уже можно найти в РИНЦ и на нашем сайте, а бумажную версию ищите в библиотеке ИЦ и лавке Музея!
❤16custom 52357288021427596055custom 52513691360045394683✍1👍1custom 53888616262438901611
Если вам было интересно узнать, что такое лето в музейных фондах, мы ответим: «Лето — это время ротаций» 😎Каждый год в тёплый летний сезон мы стараемся проводить замену экспонатов в витринах основной экспозиции. Этим летом мы провели ротацию в нескольких залах экспозиции: 💚заменили уставшие экспонаты на экспозиционные копии в витринах «Осенние праздники» и «Синагога» 💚 добавили тематическую подборку предметов, посвя…
❤🔥14🦄7custom 52513691360045394687❤4🥰1custom 52358072067707504071
😎Сотрудники Исследовательского центра продолжают не только исследовать, но и учиться новому! В начале лета Ася Дека (менеджер по работе с основной экспозицией) и Катерина Палепина (менеджер по работе с вузами и студентами) прошли курс повышения квалификации от музея Москвы «Локальная история в музее: от концепции к экспозиционному решению» и разработали идею собственного проекта👋 Мы хотим посвятить его еврейской ис…
❤🔥13custom 523572880214275960512custom 52513691360045394689❤4custom 52356248768190988214🥰2
🚗Сразу после завершения экспедиции в Ярославле, одна из исследовательских групп – Анна Патрушева и Сергей Шастин – отправились под Зеленогорск, чтобы представить первые полевые результаты на междисциплинарном семинаре «Когнитивное. Социальное. Этничность». 🌟В этом сезоне команда опробовала рисуночный метод в исследовании образов, ассоциаций и «еврейского взгляда на мир». Предварительным результатам и рефлексии над с…
❤13custom 52357288021427596055custom 53888616262438901613custom 52358072067707504072custom 52356248768190988211
Showing the 7 most recent of 7 posts we hold for @RC_JMTC. 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.
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 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Исследовательский центр ЕМЦТ” (@RC_JMTC), 810 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/RC_JMTC.
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.