Telegram RegisterThe public register of Telegram
Telegram profile photo for Jonreals Trade

Channel

Jonreals Trade

@jonrealstrade

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

98subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002001124609
TypeChannel
Username@jonrealstrade
DescriptionЛичный торговый дневник по скальпингу и наборам. У телефона @jonreals
CreatedBetween 1 November 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/jonrealstrade

Growth

987 August 2026 — 98 subscribers9 August 2026 — 98 subscribers7 August 20269 August 2026
2 measurements spanning 2 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 97–99 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 11:3198no change
7 Aug 2026, 10:4898first reading

Engagement

8 posts held, back to 31 March 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 8 posts for this entry, the most recent from 13 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
283
Videos
104
Links
8

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

27 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 37.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1037.0%
custom 5278376178124605062933.3%
custom 5395855516628972415518.5%
custom 541794523780693875227.41%
custom 524900960123122469113.70%

Custom emoji. 4 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 areTelegram’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 7 of the 8 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 27reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 31 March 2025 to 13 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

13 Oct 2025, 21:37 UTC397 views10 reactionsread 9 August 2026
Photo

Столкнулся с тем,что заполнение дневника, сбор статы, итоги дня\недели достаточно рутинное занятие, в особенности, если нет определенной эффективной системы. До этого пинал хуи,собирал стату огромный промежуток времени,но делал это максимально неслаженно и в большинстве своем - безрезультативно. Сейчас 2 недели заполнял дневник и сделал более-менее эффективную систему. Нужно это для тех,кто пытается выйти в стабиль

custom 52783761781246050629custom 54179452378069387521

Signed Jonreals

11 Oct 2025, 11:24 UTC364 views6 reactionsread 9 August 2026
Photo

Почти икс Не брал на себя огромные риски,заходил в среднем на 2-3 плечо. После пары лосей решил полностью скальпить пролив. Также чуть нашкрябал на usde. История с Кудо немного потрясла. Все кто остался в нуле, фомит и тд, пролистайте тгшки, посмотрите скольких ребят убило, у которых трейдинг был единственным источником дохода. Еще страшнее, если на тебе лежала ответственность за близких. Один, два, три икса не стоя

custom 53958555166289724155custom 54179452378069387521

Signed Jonreals

8 Apr 2025, 23:33 UTC551 views1 reactionsread 9 August 2026
Photo

Итоги вт: Пробой по эфиру. Исходя из прошлых сделок,цели небольшие,но и уровни там были более глобальные. Нужно собирать стату,не знаю ошибка или нет. Пока не разобрался со своей торговлей, торгую онли классику - пробои заточки плотности. Наборы потрепали меня по деньгам и морали. С другой стороны, этот опыт позволил мне развиваться в плане построения стратегии,рисков и необходимости вести разбор своей торговой и

👍1

Signed Jonreals

5 Apr 2025, 01:03 UTC437 views2 reactionsread 9 August 2026

Итоги пт: Словил небольшой тильт. Надеюсь к следующей неделе вернусь в строй

👍2

Signed Jonreals

3 Apr 2025, 23:03 UTC392 views5 reactionsread 9 August 2026
Photo

Итоги чт: Отскок по hippo Все еще ленюсь разбирать дневник. День получится не очень продуктивным. Нет проблем с сидением за терминалом,но есть проблемы с эффективным разбором торговли(не просто протеганные сделки в тмм). Это нежелания выполнять мелкую рутину выливается в бесмысленную трату времени за терминалом,т.к. нету четкого понимания какие сетапы хорошо работают,в каких я совершаю ошибки,отдаю деньги и т.д.

👍4custom 52490096012312246911

Signed Jonreals

2 Apr 2025, 23:52 UTC327 views1 reactionsread 9 August 2026
Photo

Итоги ср: Trump приподнять: Не хотел 2 раз кликать. Стакан хреново настроил,не чувствовал ленту Alch на копье: Мертвячок В чт нужно будет взяться за разбор дневника,ленюсь жестко. +Добавить систему продуктивного/непродуктивного дня

👍1

Signed Jonreals

31 Mar 2025, 22:45 UTC282 views2 reactionsread 9 August 2026
Photo

Итоги пн: Broccoli: Тейк был перехай выделенного уровня. По итогу часть фиксанул в локалку и дальше стопнулся в слом на 5с Rez: Очень хотелось посидеть,но эфир начали агрессивно сливать,пришлось выйти Gun: Обычный набор Mask: Неудачное разъедание Act: Вышел,как только начали сливать на фоне убравшихся плотностей на маске Дневник и итоги недели не успел сделать и скорее всего завтра тоже не смогу. Немного поднимае

👍2

Signed Jonreals

Showing the 8 most recent of 8 posts we hold for @jonrealstrade. 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

Citation-graph rank — 412,747 of 1,481,217entries 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.

Mentions

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.

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.

Cite this entry

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“Jonreals Trade” (@jonrealstrade), 98 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/jonrealstrade.

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.