Telegram RegisterThe public register of Telegram

Channel

RESO.hub

@RESOhub

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

121subscribers

-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-1002152346989
TypeChannel
Username@RESOhub
CreatedBetween 1 June 2024 and 3 August 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/RESOhub

Growth

121122121.57 August 2026 — 122 subscribers9 August 2026 — 122 subscribers15 August 2026 — 121 subscribers7 August 202615 August 2026
3 measurements spanning 8 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 121–122 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 03:14121-1
9 Aug 2026, 03:30122no change
7 Aug 2026, 12:56122first reading

Engagement

16 posts held, back to 3 August 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 16 posts for this entry, the most recent from 11 October 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
9s
Average length
9s

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.

Reaction mix

53 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 41.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2241.5%
👍1018.9%
🔥611.3%
😢611.3%
❤‍🔥59.43%
🍓23.77%
💩11.89%
🥰11.89%

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

Measured over the 16 most recent posts we hold, published 3 August 2024 to 11 October 2024, 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

11 Oct 2024, 14:52 UTC148 viewsread 9 August 2026

Ребята, кто хотел мерч со скидкой, но так и не доехал до хаба, у нас начался месяц тотальной распродажи на сайте!

11 Oct 2024, 14:52 UTC150 views1 reactionsread 9 August 2026
Forwarded from @resonancemoscowPhoto

RESO SALE 30% OFF 09.10-16.10 Объявляем месяц тотальной распродажи прошлых коллекций мерча. Каждую неделю октября скидка будет расти, но количество вещей в наличии — уменьшаться. Число вещей ограничено, рестока не будет. Худи «Музыка дело чести» — 7200 ₽ 5000 ₽ Лонгслив «Музыка дело чести» — 5200 ₽ 3650 ₽ Футболка (белая/серая/черная) — 2000 ₽ 1400 ₽ Шарф RESO24 (белый/черный) — 3200 ₽ 2250 ₽ Шапка RESO24 (черная

1

20 Sept 2024, 15:57 UTC193 views7 reactionsread 9 August 2026
Forwarded from @resonancemoscowPhoto

После полутора лет, проведённых на «Дизайн-заводе», мы закрываем RESO.hub. Проект будет обновляться и возродится в новом месте. Двери Kyomei остаются открытыми, и ресторан продолжит радовать вас изысканными блюдами японской кухни. Следите за обновлениями!

😢6💩1

10 Sept 2024, 18:22 UTC254 views4 reactionsread 9 August 2026
Photo

Rhythm riot x Kyomei В эту пятницу встречаемся на веранде Kyomei вместе с вечеринкой Rhythm riot. Приглашаем насладиться изыскаными японскими закусками и авторскими коктейлями на основе саке. Будем танцевать с друзьями под открытым небом под звуки UK Garage, 2step и breakbeat. 📍RESOhub & Kyomei Japanese bistro (Большая Новодмитровская, 36с2) 📋 Вход свободный

4

6 Sept 2024, 14:57 UTC500 views3 reactionsread 9 August 2026

У нас небольшие изменения в лайнапе. Ловите тайминг на сегодня: 19:00 senyasenya 20:30 promi$e 22:00 seagxll

3

3 Sept 2024, 18:44 UTC≈1,210 views17 reactionsread 9 August 2026
Photo

UK CLUB x Kyomei В эту пятницу на веранде Kyomei встречаем промокоманду UK CLUВ. Проведём тёплый осенний вечер с друзьями, наслаждаясь изыскаными японскими закусками и авторскими коктейлями. Будем общаться и танцевать под сеты молодых и дерзких ребят из UK CLUB, которые подготовили селекты из отборного хауса, бодрого брейкса и брейкбита. 🕖 6 сентября, 19:00 📍RESOhub & Kyomei Japanese bistro (Большая Новодмитровс

8🔥5👍4

31 Aug 2024, 16:52 UTC221 views3 reactionsread 9 August 2026
Photo

Сегодня весь вечер на веранде Kyomei заряжают дарковыми вайбами друзья RESO.hub Tina Gavaldi & Andrè Приходите вкусно есть и танцевать! Начало в 20:30

👍3

30 Aug 2024, 14:27 UTC190 views5 reactionsread 9 August 2026

Вечером встречаемся на веранде! Ловите тайминг на сегодня: 19:00 Kaleria 20:00 Anny Bruk & Chernika 21:30 Mystica 22:30 Erika Eger

❤‍🔥21🔥1🥰1

28 Aug 2024, 09:33 UTC210 views2 reactionsread 9 August 2026
Photo

Rimbu Pro x Kyomei В последнюю пятницу этого лета провожаем закат на веранде Kyomei вместе с шоукейсом Rimbu Pro. Приглашаем насладиться изыскаными японскими закусками и авторскими коктейлями на основе саке, будем танцевать с друзьями под открытым небом и встречать теплую летнюю ночь. Музыкальным наполнением вечера займутся девушки из промо команды Rimbu Pro, под чутким кураторством Наташи Chernika весь вечер буде

👍2

23 Aug 2024, 14:27 UTC188 views1 reactionsread 9 August 2026

Вечером встречаемся на веранде Kyomei, а в случае сильного дождя будем согреваться в нашем уютном хабе. Тайминг на сегодня: 19:00 Brad Pulpitt 20:00 Amora 21:00 Veres 22:00 Mishur 23:00 Andrew

1

21 Aug 2024, 12:42 UTC534 views3 reactionsread 9 August 2026
Photo

Amora x Kyomei В пятницу на веранду Kyomei возвращается московский промоутер и диджей Amora с её фирменной вечеринкой. Приглашаем провести вечер в кругу друзей, наслаждаться японской едой, пить саке и авторские коктейли, и, конечно, танцевать. В этот вечер вас ждут dj-сеты перспективных артистов, с музыкальным наполнением от инди дэнса до техно всех мастей. 🕖 23 августа, 19:00 📍RESOhub & Kyomei Izakaya Bar (Больш

❤‍🔥3

12 Aug 2024, 16:30 UTC239 views2 reactionsread 9 August 2026
Photo

Шахматный клуб // 13.08 Завтра вечером встречаемся в хабе, угощаемся вином, саке и изысканными японскими закусками, играем в шахматы. Уровень участников открытый, каждый найдёт себе соперника по силам. А хостит встречу КМС по шахматам Иван Дрозд. 🕗 13 августа 20:00 📍RESOhub & Kyomei Izakaya Bar (Большая Новодмитровская, 36с2)

2

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

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.

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

“RESO.hub” (@RESOhub), 121 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/RESOhub.

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.