букет СЕЙЛОР ВЕНЕРА 🧪 использует силу любви! состав: •гелиантус •амарант •георгин •пионовидная роза Melon •краспедия •диантусы •эустома 4500₽ заказать
custom 52513645661593442536custom 52513242450063722973custom 53235873875891483833

Channel
@hypnoooo
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,092subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001520950759 |
|---|---|
| Type | Channel |
| Username | @hypnoooo |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/hypnoooo |
Ecommerce storefront — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 12 Sept 2026, 18:22 | 1,092 | +6 |
| 9 Sept 2026, 03:20 | 1,086 | +1 |
| 3 Sept 2026, 23:59 | 1,085 | -2 |
| 31 Aug 2026, 07:22 | 1,087 | -1 |
| 24 Aug 2026, 13:37 | 1,088 | +1 |
| 21 Aug 2026, 05:04 | 1,087 | -2 |
| 18 Aug 2026, 03:22 | 1,089 | -1 |
| 11 Aug 2026, 02:26 | 1,090 | -2 |
| 7 Aug 2026, 20:02 | 1,092 | no change |
| 6 Aug 2026, 23:32 | 1,092 | first reading |
4 posts held, back to 28 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 4 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
67 reactions across 4 posts, in 12 distinct kinds. The most used accounts for 14.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5233478668776389596 | 10 | 14.9% | |
| custom 5357096889936269710 | 10 | 14.9% | |
| custom 5267272231670529639 | 8 | 11.9% | |
| custom 5391124786246083532 | 8 | 11.9% | |
| custom 5422606754791847363 | 7 | 10.4% | |
| custom 5251364566159344253 | 6 | 8.96% | |
| custom 5323587387589148383 | 6 | 8.96% | |
| custom 5422448240433851075 | 4 | 5.97% | |
| custom 5251324245006372297 | 3 | 4.48% | |
| custom 5312477552734914786 | 2 | 2.99% | |
| custom 5339096909632000503 | 2 | 2.99% | |
| custom 5246988664499618325 | 1 | 1.49% |
Custom emoji. Every row above is a 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 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 67 reactions 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 28 July 2026 to 30 July 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.
букет СЕЙЛОР ВЕНЕРА 🧪 использует силу любви! состав: •гелиантус •амарант •георгин •пионовидная роза Melon •краспедия •диантусы •эустома 4500₽ заказать
custom 52513645661593442536custom 52513242450063722973custom 53235873875891483833
свадебные букеты 💗 спасибо нашим прекрасным невестам! каждый букет - личная история, образ и стиль! ссылка, чтобы заказать свой букет мечты
custom 535709688993626971010custom 54226067547918473637custom 53235873875891483833custom 54224482404338510753custom 53390969096320005032custom 52469886644996183251
букет ЗЕЛЕНЫЙ ОСТРОВ🍃 отдохнуть и пробежаться глазами по линиям, фактурам и игре оттенков! состав: •гладиолус •гелиантус •краспедия •диантусы •амарант •роза Вегги •никандра 4300₽ заказать
custom 52334786687763895966custom 53911247862460835326custom 52672722316705296392
дуо-букет сезонный СОЛНЕЧНОЕ СПЛЕТЕНИЕ 🔅 георгины сложного оттенка в дуэте с шариками краспедии, которая превратится в сухоцвет и не изменит внешний вид! состав: •георгины •краспедия 3600₽ заказать
custom 52672722316705296396custom 52334786687763895964custom 53124775527349147862custom 53911247862460835322custom 54224482404338510751
Showing the 4 most recent of 4 posts we hold for @hypnoooo. 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 2 registered channels — 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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“ГИПНОЗ - ЦВЕТЫ” (@hypnoooo), 1,092 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/hypnoooo.
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.