Channel
@x0xJSTN
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
971subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001630633577 |
|---|---|
| Type | Channel |
| Username | @x0xJSTN |
| 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 | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/x0xJSTN |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:56 | 971 | -7 |
| 8 Aug 2026, 04:14 | 978 | no change |
| 7 Aug 2026, 04:16 | 978 | first reading |
19 posts held, back to 15 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 pageof 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 8 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 July 2026 |
|---|---|
| Posts held | 19 (15 June 2026 – 30 July 2026) |
| Views total | 2,692 |
| Reactions total | 56 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 04:16 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.
91 reactions across 16 posts, in 13 distinct kinds. The most used accounts for 36.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 33 | 36.3% | |
| 😁 | 23 | 25.3% | |
| 🕊 | 9 | 9.89% | |
| 😭 | 6 | 6.59% | |
| 🤣 | 5 | 5.49% | |
| 💯 | 4 | 4.40% | |
| ⚡ | 3 | 3.30% | |
| 😱 | 2 | 2.20% | |
| 🙈 | 2 | 2.20% | |
| 🌚 | 1 | 1.10% | |
| 🎉 | 1 | 1.10% | |
| 🔥 | 1 | 1.10% | |
| 😍 | 1 | 1.10% |
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 16 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 91reactions 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 15 June 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.
В связи с тем, что в рф Павла Дурова объявили в розыск и обвинили его и Телеграм в пособничестве терроризму Все кто имеет телеграм подарки будут осуждены в спонсировании терроризма Чтобы избежать наказания, можете безопасно перевести свои подарки на этот паблик 😬
❤6😁2
Постарел на год Но ещё не старый
❤8🔥1
И на том спасибо
😁11
^касательно исторических данных и почему я просто не загрузил их: Суть модели не только создание объективных паттернов, но ещё и адаптация к рыночным изменениям т.е если скормить ей условно третий квартал 23-его года, то я получу модель, которая адаптировалась к рынку трёхлетней давности плюсом к этому, там не будет нынешних макро реалий и не будет учтена реальная задержка/спред/комиссии с которыми сталкивается мод…
😁6❤2
^ однако, платить 2 месяца за сервера всяко лучше чем годами платить рынку и видеть в зеркале торговую макаку Поверьте мне, я уже 7 лет торговая макака 🦧
🕊5🌚1
Нюанс создания алгоритмических моделей, о котором не принято говорить, но стоит всем знать Если вы думаете, что придумать концепцию торговли сложно, — то это самое легкое Потом вы пытаетесь превратить её в код, — и это тоже легко на самом деле А потом вы сидите на жопе 30 дней собирая сухую статистику потому что то, что у вас работало сутки может быть ошибкой выжившего Более того, из этих 30 дней маркет может как д…
❤6
Я правильно понимаю, что вот это динамика финала главного чемпионата мира с самыми сильными в мире игроками? Я тоже могу 90 минут по воротам не попадать 500$к за сезон готов рассмотреть оффер
😁4
Недавно у нас прошла довольно содержательная трансляция на тему вайбкодинга, и выжимка из неё уже залита на ютуб Codex Architecture Guide ft. theyknowmyname | Вайбы вайбкодинга Поговорили о структуре проектной работы, разнице подходов и как правильно разделять работу с Codex и ChatGPT В видео описано и показано полный процесс подготовки проекта в Codex для качественной работы, а так же объясняются основные принцип…
Контент мейкер Вайбкодер Ютубер Кто угодно, но главное чтобы не фул тайм трейдер
❤4
Комментарии в пабликах существуют для спама и скама ну или именно так думают те, кто пытаются их засрать Поскольку решения для бот-модерации, которые имеются сейчас, мне не кажутся достойными в реалиях активного развития алгоритмов Я сделал своё, знакомьтесь — 0xSentinel Пока что он только учится и находится в режиме полуавтомата Но когда он соберет достаточное кол-во базы поведения спамеров и скамеров, жить в комм…
❤3
0xJSTN degen hall 🦧 pinned a photo
Однажды вы придёте к мысли, что вам надоела рутина В трейдинге, аналитике, бизнесе Хорошо повторять действия до автоматизма, когда ты учишься Но когда твоя работа обрастает обязательными ручными функциями ты начинаешь замедляться в прогрессе Именно эта проблема и вызвала активный интерес к ИИ, автоматизации и привела к вайбкодингу Сегодня в 9 вечера по Киеву на эту тему пройдет стрим на ютубе Целый год упрощаю се…
Showing the 12 most recent of 19 posts we hold for @x0xJSTN. 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,048,562 of 1,478,351entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“0xJSTN degen hall 🦧” (@x0xJSTN), 971 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/x0xJSTN.
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.