Telegram RegisterThe public register of Telegram
Telegram profile photo for Мойше

Channel

Мойше

@moyshebar

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

264subscribers

-5 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-1001459151774
TypeChannel
Username@moyshebar
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/moyshebar

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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

264271267.57 August 2026 — 269 subscribers8 August 2026 — 269 subscribers22 August 2026 — 271 subscribers29 August 2026 — 266 subscribers8 September 2026 — 265 subscribers15 September 2026 — 264 subscribers7 August 202615 September 2026
6 measurements spanning 39 days, net -5. 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 263–272 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:59264-1
8 Sept 2026, 08:15265-1
29 Aug 2026, 23:14266-5
22 Aug 2026, 21:44271+2
8 Aug 2026, 08:50269no change
7 Aug 2026, 15:48269first reading

Engagement

10 posts held, back to 18 June 2026the 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 10 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
5m 01s
Average length
1m 15s

Measured directly from 4 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

77 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3342.9%
🔥1722.1%
💘1519.5%
😢1215.6%

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

Measured over the 10 most recent posts we hold, published 18 June 2026 to 3 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.

Recent posts

3 Aug 2026, 11:24 UTC91 views12 reactionsread 8 August 2026

Дорогие мои! С сегодняшнего дня я закрыт. Всех обнял и поцеловал. P.S. мы готовим новый коктейльный бар. Он будет в тех же соцсетях. Поэтому не теряемся. Будем делиться процессом!

😢12

30 Jul 2026, 13:34 UTC150 views2 reactionsread 8 August 2026
Photo

Финальная вечеринка, мои хорошие! Любовь живёт три года, мы чуть-чуть не дотянули до пяти. Но, конечно, лучше уходить по любви, а не затягивать до последнего. На этой недели работаю последние дни. А в пятницу и субботу – делаю вечеринку в своих лучших традициях: ▪️ за пультом Алина Пономарёва и dj Shalom Cake ▪️ мы пританцовываем под афро-хаус ▪️ маэстро угощает настойками ▪️ и в пятницу и в субботу разыграем набо

2

17 Jul 2026, 13:19 UTC172 views8 reactionsread 8 August 2026
Photo

Дорогие, мы определились с финальным днём работы. Это будет 2 августа. Шутки на этот счёт, в целом, принимаются. А пока мне ностальгия попала в глаз. Делюсь ей с вами. Сегодня пересматриваю архивные фотокарточки с презентаций коктейльных карт 2022-2025 годов.

💘5🔥3

3 Jul 2026, 10:35 UTC187 views6 reactionsread 8 August 2026
Video

Дарлинги, планы пришлось немного пересмотреть. Помните, я собирался съехать в отель, пока ищу новый дом? Так вот, свободного номера для такого обаятельного жильца пока не нашлось. Поэтому ещё дней десять я буду жить по прежнему адресу и встречать вас за первым баром со всеми оставшимися коктейлями, вермутами и, смею надеяться, отличным настроением. А вот второй бар уже закрылся и вовсю готовится к ремонту. Григори

4💘2

28 Jun 2026, 10:14 UTC188 views7 reactionsread 8 August 2026
Photo

Дарлинги, есть у меня подозрение, что пита с креветкой незаслуженно получает меньше внимания, чем заслуживает! Предлагаю исправить это недоразумение. #вашМойше

💘52

27 Jun 2026, 17:35 UTC168 views12 reactionsread 8 August 2026
Video

Крошки мои, не люблю лезть с расспросами, но ради вас иногда приходится! Получилось, стоит отметить, весьма занятно! P.S. сколько рюмочек насчитали? #вашМойше

7💘3🔥2

21 Jun 2026, 11:11 UTC193 views8 reactionsread 8 August 2026
Photo

Яхонтовые мои, последний вермутовый мастер-класс Мойше случился. Григорио и Макс постарались, все унесли домой по вермуту и по воспоминанию. В общем, я доволен! #вашМойше

5🔥3

19 Jun 2026, 17:53 UTC170 views10 reactionsread 8 August 2026
Video

Мои дорогие, познакомьтесь с людьми, которые терпели меня 5 лет. Эти четверо знали про Мойше всё, (ну почти всё). Остальное я сегодня из них вытащил. Но это, как вы понимаете, только начало! #вашМойше

6🔥4

18 Jun 2026, 14:36 UTC160 views6 reactionsread 8 August 2026
Photo

Сегодня у меня небольшое возвращение. С 20:00 за баром вы сможете лицезреть Алексея Чернышева. Кто знает Лёшу, и так всё понял, а кто не знает, сегодня хороший повод познакомиться! #вашМойше

3🔥3

18 Jun 2026, 13:14 UTC140 views6 reactionsread 8 August 2026
Video

Дарлинги, некоторые вечера хочется растянуть подольше. Поэтому 28 июня я решил устроить прощальный кино-вечер. Будем смотреть «1+1». Фильм, который за столько лет уже стал чем-то вроде старого доброго знакомого. Смешного, трогательного и очень вовремя напоминающего, что хорошие истории всегда про людей. К кино, разумеется, полагается ужин. В меню вечера: ▫️ Фрэнч-дог и картофель фри. ◽️ Паштет с колерованным масло

4🔥2

Showing the 10 most recent of 10 posts we hold for @moyshebar. 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.

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

“Мойше” (@moyshebar), 264 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/moyshebar.

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.