Еще один урок усвоен Мужик решил поиграть со змейкой и вот что из этого вышло.
👍8🤯2❤1

Channel
@trysqhws
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,275subscribers
-132 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001698736404 |
|---|---|
| Type | Channel |
| Username | @trysqhws |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/trysqhws |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 40% 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 Oct 2026, 13:40 | 3,275 | -12 |
| 4 Oct 2026, 18:17 | 3,287 | -12 |
| 25 Sept 2026, 07:56 | 3,299 | -31 |
| 15 Sept 2026, 05:00 | 3,330 | -6 |
| 11 Sept 2026, 18:00 | 3,336 | -9 |
| 6 Sept 2026, 18:41 | 3,345 | -10 |
| 2 Sept 2026, 17:08 | 3,355 | -6 |
| 30 Aug 2026, 22:05 | 3,361 | -7 |
| 27 Aug 2026, 21:16 | 3,368 | -10 |
| 24 Aug 2026, 10:43 | 3,378 | -9 |
| 20 Aug 2026, 21:02 | 3,387 | -7 |
| 17 Aug 2026, 10:38 | 3,394 | -7 |
| 13 Aug 2026, 11:23 | 3,401 | -4 |
| 10 Aug 2026, 17:27 | 3,405 | -1 |
| 7 Aug 2026, 20:05 | 3,406 | -1 |
| 7 Aug 2026, 11:16 | 3,407 | first reading |
13 posts held, back to 6 November 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages 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 13 posts for this entry, the most recent from 24 December 2023. An engagement rate over an empty window would be a number about nothing.
Measured directly from 11 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.
87 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 32.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 28 | 32.2% | |
| ❤ | 18 | 20.7% | |
| 😢 | 15 | 17.2% | |
| 🔥 | 9 | 10.3% | |
| 😱 | 6 | 6.90% | |
| 😁 | 3 | 3.45% | |
| 👎 | 2 | 2.30% | |
| 🤮 | 2 | 2.30% | |
| 🤯 | 2 | 2.30% | |
| 🥴 | 1 | 1.15% | |
| 🦄 | 1 | 1.15% |
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 12 of the 13 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 87 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 6 November 2023 to 24 December 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Еще один урок усвоен Мужик решил поиграть со змейкой и вот что из этого вышло.
👍8🤯2❤1
Канал продаётся, по всем вопросам @GRAM_SM
Красивы, легко запоминающиеся номера. Бесплатная доставка. Платите только за тариф от 790р в месяц. Активация сим сразу после пополнения. Закать тут : https://vk.cc/csMvhF
👍4
Смешное. Подростки пытались сделать селфи на железнодорожных путях но получили удар 600В. Судя по всему парень не хотел уходить один, поэтому прикоснулся к девушке передав ей заряд. Их дальнейшая судьба неизвестна.
😢7😱4❤1👍1😁1
Ещё одно видео связанное с железной дорогой но уже из России. Из-за того что пиздюку лет 10 от силы, оно всё-таки грустное.
😢8🔥3👍2
Agua video (i want water) Очередной пиздец от картеля. На этот раз убийца из картеля CJNG по кличке "Клоун" похитил человека который, скорее всего, был членом враждебного картеля. На видео видно человека которому полностью сняли лицо как на funkytown video и он находясь в сознании просит у своих мучителей воды.
👍3🤮2❤1🔥1
Лев съел человека в цирке прямо напротив толпы зевак.
🔥2
«Ваш президент убит. Киев окружён. Сложите оружие. Слава России!»: российские хакеры держат в тонусе украинского телезрителя
❤11👎2😁2🦄1
Что б сука не втыкал, чепуха!
👍1🔥1
В Якутии на вахтовиков напал медведь. Другие сотрудники пытались отогнать медведя, но получилось это не сразу.На место вызвали охотника, который убил животное. Пострадавшие были госпитализированы с серьезными ранами головы.
👍2❤1
В Ростове чухан до полусмерти забил администратора компьютерного клуба Конфликт начался 29 октября, когда группа людей пришла в клуб. Они развалились на диванах, по-хамски себя вели, кидая джойстики по комнате. Когда администратор попросил покинуть клуб — его побили Уже 5 ноября конфликт продолжился. Один из мигрантов (что приходил ранее) пришел в клуб, жестоко избив молодого парня, с которым у него был конфликт
👍2
Во Владивостоке двое мужчин зачем-то пытались распилить артиллерийский снаряд. Обоих просто разорвало. Кадры очень жесткие, строго 21+.
👍5❤1🔥1
Showing the 12 most recent of 13 posts we hold for @trysqhws. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“Жесть 18+” (@trysqhws), 3,275 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/trysqhws.
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.