Channel
@urusukaaa
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
783subscribers
+4 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004426099990 |
|---|---|
| Type | Channel |
| Username | @urusukaaa |
| Created | Between 1 June 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/urusukaaa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 19:26 | 783 | +4 |
| 25 Aug 2026, 22:15 | 779 | first reading |
19 posts held, back to 30 June 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 August 2026 |
|---|---|
| Posts held | 19 (30 June 2026 – 25 August 2026) |
| Views total | 4,097 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Aug 2026, 22:15 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 2 of the 19 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 30 June 2026 to 25 August 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.
Рынок джунов не умер. Умер старый способ входа в IT. Раньше было достаточно пройти курс, сделать калькулятор, написать Java в CV и отправить 300 откликов. Сейчас этого мало. Если бы я заходил с нуля сегодня, я бы строил путь так: 1. База + практика одновременно Синтаксис Java, ООП, коллекции, SQL, Git, HTTP и понимание того, как вообще работает код, всё ещё нужны. AI фундамент не отменяет. Если вы не понимаете основы…
Что сейчас вообще можно встретить на собеседованиях на рынке? Выше я писал, что хочу сделать небольшое исследование рынка и я его сделал. Сходил на разные интервью, посмотрел, как сейчас нанимают, и постепенно буду делиться результатами. Уже не по чужим тредам, а по своему опыту. Я бы сейчас выделил 3 основных типа собеседований. 1. Старый добрый аутсорс / аутстафф Да, он всё ещё жив и вполне активно нанимает. …
Всем привет! Сегодня хочу запостить небольшой топ чеклист перед каждым собесом. Вроде бы вещь очевидная, но многие это недооценивают и забивают. Я когда-то тоже забивал и думал, что оно само собой всё придёт – не придет, вас встречают по одежке и важно быть к этому готовыми. Первое: представление о себе надо знать почти на зубок и не придумывать его прямо на звонке. Кто ты, сколько опыта, над чем сейчас работаешь, з…
File, posted without a caption
Сегодня на разборе CV моего знакомого разработчика. Которое не так давно было у него единственным акутальным (личные данные изменены). На первый взгляд всё выглядит неплохо: 5+ лет опыта, Java/Spring, React, базы данных, микросервисы. Но есть несколько критических моментов, которые нужно менять. Первое, что бросается в глаза: дизайн. Зелёная колонка, шкалы языков, множество отдельных блоков. Ошибка многих – превращат…
Немного субботнего вайба
Всем привет, на пару недель улетел на Тенерифе 🌴 После работы, собесов и всей этой AI-движухи самое время немного потупить у океана. А потом с новыми силами вернуться сюда, связь 🤙
Почему два разработчика примерно одного уровня могут получать $3k и $10k? Очень долго в IT живёт простая логика: джун получает мало; мидл больше; сеньор ещё больше. Чем сильнее разработчик, тем выше зарплата. Звучит логично. На практике я много раз видел совсем другую картину. Два человека примерно одного уровня. Один сидит на $3k. Второй спокойно уходит на $7–10k. И разница между ними далеко не всегда в техническом …
🎮 На днях ради прикола сделал с Claude Code целую игру. Меня зацепила песня Du Bist Gut Genug из того самого пранка в ТЦ, и я подумал: а что если сделать под неё ритм-игру? Типа Flappy Bird, только прыгать надо в бит. Раньше на этом мысль, скорее всего, и закончилась бы. Потому что дальше надо: сделать саму игру; разобраться с музыкой; нарисовать визуал; протестировать механику; выложить; а потом ещё придумать, где в…
Channel photo updated
Сегодня хочу немного поделиться про сегодняшний хайп с ИИ. Меня в разговорах про AI больше всего раздражают две крайности. Первая: «Всё. Программисты закончились. Ещё год и нас заменят». Вторая: «Да бесполезная игрушка ваш AI. Нормальный разработчик сам код пишет». По-моему, обе стороны немного занимаются самоуспокоением. AI уже очень сильно поменял мою работу. Я пользуюсь им практически каждый день и обратно в 2023-…
Sticker, posted without a caption
Showing the 12 most recent of 19 posts we hold for @urusukaaa. 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.
Citation-graph rank — 1,035,300 of 1,630,085 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 5 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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“Urus” (@urusukaaa), 783 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/urusukaaa.
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.