Channel
@urkysposts
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
71subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002428012696 |
|---|---|
| Type | Channel |
| Username | @urkysposts |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 1 September 2026 |
| On Telegram | t.me/urkysposts |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 17:25 | 71 | -3 |
| 9 Aug 2026, 22:02 | 74 | no change |
| 8 Aug 2026, 16:28 | 74 | +1 |
| 8 Aug 2026, 08:33 | 73 | first reading |
13 posts held, back to 17 January 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 13 posts for this entry, the most recent from 23 May 2026. An engagement rate over an empty window would be a number about nothing.
196 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 46.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5312108610749223697 | 92 | 46.9% | |
| custom 5312137236706253935 | 66 | 33.7% | |
| ❤ | 38 | 19.4% |
Custom emoji. 2 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 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 13 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 196 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 17 January 2026 to 23 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.
Пятая тройка: ой, как я тоже тут переделывал💧 Были и фэнтези, и всё-всё. В итоге я решил, что на фоне будет киберпанк, ахаха. В целом вроде клево? Не? Короче, ждём ваше мнение, реакцию, репосты и всё такое, бла-бла✋ Участвовали: Урки, Мия ииии HLAM😝😝😝 #тройка #рендер
❤10
Ахаха это настолько плохо, что я не хочу кидать это на основу
❤16
Ну лев, ну тигр
❤12
Что вы хотели бы увидеть в основном тгк? Много кто просит делать рендеры с мужиками. А че их рендерить то? Идей ноль
custom 531213723670625393514
Рассказывайте, как ваши дела?
custom 531210861074922369712
Какой же он угашенный
custom 531210861074922369718
Я доволен От этой суммы стоит еще вычесть половину денег, которые я скинул за рефералку, +налог, и получается неплохая сумма для подработки на 4 недели Это очень тяжелая работа, которая востребована только зимой и в непогоду, типо дождя. Чтобы стабильно получать много, надо либо иметь велик, либо машину (хотя с ней лучше уйти в такси) От этой суммы я потратил ±25к на подарки родителям, продукты, такси (в редких сл…
custom 531213723670625393514custom 53121086107492236973
В блендере балуюсь Будто Макима получилась
custom 531213723670625393511custom 53121086107492236973
😭 Мои зимние каникулы подходят к концу Скоро мне выплатят все деньги за доставки, и я сделаю пост о том, сколько по итогу удалось заработать
custom 531210861074922369712custom 53121372367062539352
Ну тут прям пришлось постараться (Забыл траву добавить 😭)
custom 531210861074922369715
Че та еще сделал
custom 531210861074922369716custom 53121372367062539355
Попытка в лоу поли
custom 531213723670625393520
Showing the 12 most recent of 13 posts we hold for @urkysposts. 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.
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.
Named by 1 registered channel — 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.
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.
@urkysposts named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Урки, гадэм!” (@urkysposts), 71 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/urkysposts.
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.