Варим кофе, создаем атмосферу, поднимаем настроение и заряжаем энергией. Делимся историями из жизни Робуст, рассказываем про нашу команду, раскрываем секреты и отвечаем на каверзные вопросы гостей
Created
Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
2 measurements taken within a single day. 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 364–366 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Aug 2026, 06:31
365
no change
7 Aug 2026, 23:16
365
first reading
Engagement
4 posts held, back to 8 March 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 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 4 posts for this entry, the most recent from 14 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
953
Videos
464
Links
88
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
1m 53s
Average length
57s
Measured directly from 2 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
73 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 65.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
48
65.8%
custom 5404835520150773707
14
19.2%
custom 5357166391097043194
5
6.85%
custom 5389107822359231369
3
4.11%
custom 5424603794325399808
3
4.11%
Custom emoji. 4 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 areTelegram’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 4 of the 4 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 73reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 8 March 2026 to 14 May 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.
⚡️Кофейня Робуст, которая оказалась вообще не про робусту!
Сегодня с утра случился очень хороший пример того, почему иногда нельзя судить кофейню по названию💡
Когда я перед поездкой в Пятигорск открывал карты и смотрел, куда зайти, увидел кофейню «Робуст».
💭Подумал: «Наверное, там всё на робусте, фильтра нет, эспрессо в итальянском стиле, сахар на стойке, крепко, горько и бодро»
Короче, я почему-то сразу решил, ч…
Представьте мир, где нет женщин. Как изменилась бы культура потребления кофе и облик современных кофеен?
Отвечает нейросеть. Насчет лавандового рафа есть сомнения 😆
С праздником, дамы 🌷
custom 540483552015077370714
Showing the 4 most recent of 4 posts we hold for @roboost. 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.
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 8 August 2026 — this
entry's latest reading, not the date you are reading this.
“Команда РОБУСТ” (@roboost), 365 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/roboost.
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.
