слабые отписываются, сильные — идут выполнять первый приказ от синего кита
custom 535305557052385669917custom 53552860243500804314custom 53527657933753622373custom 53525380999791345931

Channel
@yatalant666
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
609subscribers
+235 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002397030934 |
|---|---|
| Type | Channel |
| Username | @yatalant666 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/yatalant666 |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 4 Oct 2026, 10:56 | 609 | +89 |
| 19 Sept 2026, 03:01 | 520 | +25 |
| 10 Sept 2026, 11:41 | 495 | +52 |
| 1 Sept 2026, 09:49 | 443 | +60 |
| 24 Aug 2026, 19:28 | 383 | -10 |
| 16 Aug 2026, 19:23 | 393 | +18 |
| 8 Aug 2026, 13:57 | 375 | +1 |
| 8 Aug 2026, 06:18 | 374 | no change |
| 7 Aug 2026, 19:44 | 374 | first reading |
20 posts held, back to 17 May 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 20 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
330 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 42.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5352538099979134593 | 139 | 42.1% | |
| custom 5352765793375362237 | 48 | 14.5% | |
| custom 5353055570523856699 | 25 | 7.58% | |
| custom 5352657886617018049 | 24 | 7.27% | |
| custom 5352722972551422194 | 23 | 6.97% | |
| custom 5352750735220023963 | 23 | 6.97% | |
| custom 5355286024350080431 | 19 | 5.76% | |
| custom 5352985854614708391 | 18 | 5.45% | |
| custom 5352901995378252828 | 11 | 3.33% |
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 15 of the 20 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 330 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 17 May 2026 to 27 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.
слабые отписываются, сильные — идут выполнять первый приказ от синего кита
custom 535305557052385669917custom 53552860243500804314custom 53527657933753622373custom 53525380999791345931
творог кола зеро помидоры огурцы сметана курица соус
custom 535298585461470839114custom 53525380999791345937custom 53552860243500804312
стримы не смотрите, так хоть посты лайкайте, сучки 😡 сегодня покоряю лоутаб twitch.tv/yatalant666 tiktok.com/@yatalant666_collectors/live
custom 535253809997913459330custom 53530555705238566993custom 53527229725514221942custom 53527507352200239632custom 53527657933753622372
лечу апать 2500 ♿️ twitch.tv/yatalant666 tiktok.com/@yatalant666_collectors/live
custom 53525380999791345939custom 53527507352200239631custom 53529019953782528281custom 53529858546147083911
гайд на прицел кто отпишется у того понос будет, предупреждаю
custom 535276579337536223732custom 535253809997913459320custom 535272297255142219415custom 53552860243500804318custom 53526578866170180496
а хули вы другие посты так не лайкайте
custom 535275073522002396313custom 53526578866170180499custom 53527229725514221946custom 53530555705238566995custom 53529858546147083912
лан, хуй с вами 30 сердец сюда и будет гайд 😇
custom 535253809997913459359custom 53529019953782528286custom 53552860243500804315custom 53527507352200239631
позитивный стрим без мата (до первой смерти) 😁 twitch.tv/yatalant666 tiktok.com/@yatalant666_collectors/live
custom 53527657933753622377custom 53525380999791345934custom 53527507352200239631
летим в корпоративном турике 2-3 чтобы в плей-офф выйти надо сегодня 2 последние выиграть проебали 🌚 30 сек дилэй twitch.tv/yatalant666 tiktok.com/@yatalant666_collectors/live
custom 53526578866170180493custom 53527507352200239631
ку че делаете twitch.tv/yatalant666 tiktok.com/@yatalant666_collectors/live
custom 53527507352200239634
стрим до первого луза (1 игра 😁) twitch.tv/yatalant666 tiktok.com/@yatalant666_collectors/live
custom 53525380999791345934
в конце собака начала скулить, не обессудьте 🌚
custom 53525380999791345935custom 53529019953782528282
Showing the 12 most recent of 20 posts we hold for @yatalant666. 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 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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“yatalant666” (@yatalant666), 609 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/yatalant666.
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.