Telegram RegisterThe public register of Telegram

Channel

Trading Out Loud

@loudtrading

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

356subscribers

+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-1001811451612
TypeChannel
Username@loudtrading
Description@newdward
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/loudtrading

Growth

3567 Aug 2026, 10:46 — 356 subscribers8 Aug 2026, 06:45 — 356 subscribers7 Aug 2026, 10:468 Aug 2026, 06:45
2 measurements taken within a single day. 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 355–357 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 06:45356no change
7 Aug 2026, 10:46356first reading

Engagement

20 posts held, back to 22 May 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 20 posts for this entry, the most recent from 31 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
91
Videos
1
Links
30

Lifetime counters from Telegram’s own channel header, read 8 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

321 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 18.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🐳5818.1%
custom 54538846479665249535717.8%
👍5316.5%
4614.3%
custom 53146283993422990064012.5%
custom 5388977792224342481257.79%
🍾226.85%
175.30%
👎30.935%

Custom emoji. 3 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 20 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 321reactions 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 22 May 2025 to 31 January 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.

Recent posts

31 Jan 2026, 15:44 UTC141 views7 reactionsread 8 August 2026

Так себе альтсезон, мягко говоря. Думаю, нужно признать неудачу и сократить все позиции в альткоинах до нуля. Оставлю HYPE, потому что еще держится, и BTC, возможно немного SOL/ETH Результат по всему портфелю: -30% от вложенных. Не -99% как у практически всех плечевиков, но и не +320% как у тех, кто просто купил слиток серебра в Апреле 2025 Пора искать новый способ вытягивать с рынка

custom 54538846479665249534custom 53146283993422990063

21 Nov 2025, 22:15 UTC413 views8 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 531462839934229900662

13 Oct 2025, 07:25 UTC384 views5 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 53889777922243424815

10 Oct 2025, 21:24 UTC384 views8 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 53146283993422990068

6 Oct 2025, 15:20 UTC425 views15 reactionsread 8 August 2026
Photo

+9.5% с начала октября, как по часам. Биткоин открыл Q4 свечой на +3.94% и продолжал расти всю неделю Начало квартала многообещающее. К тому же, в мире всё больше печатают деньги, хотя корреляция уже не такая однозначная, сказывается то, что мы на финальных стадиях цикла роста На мой взгляд, времени на рост остается не так много. Может быть я ошибаюсь, но увеличивать риски сейчас нет никакого желания @loudtrading

👍11🐳2custom 53889777922243424812

26 Sept 2025, 17:04 UTC380 views30 reactionsread 8 August 2026
Photo

2 основных состояния крипторынка @loudtrading

custom 531462839934229900612custom 545388464796652495386custom 53889777922243424814

25 Sept 2025, 16:33 UTC316 views23 reactionsread 8 August 2026

Ваши ответы вселяют надежду в мой портфель 🥹

custom 538897779222434248110🍾8🐳4custom 54538846479665249531

25 Sept 2025, 14:02 UTC318 views10 reactionsread 8 August 2026
Poll

Ваши планы по крипте до конца года

  1. Докупаю и держу до 202624%
  2. Докупаю, но продам до 20265%
  3. Держу, продам до 202613%
  4. Держу, не продам до 202615%
  5. Продаю сейчас8%
  6. Уже все продал / без крипты35%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

4👍4👎2

25 Sept 2025, 14:02 UTC243 views9 reactionsread 8 August 2026
Poll

Альтсезон

  1. Будет33%
  2. Не будет28%
  3. Уже был39%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

3👍3🐳21

24 Sept 2025, 11:39 UTC279 views25 reactionsread 8 August 2026
Photo

CZ в кои то веки решил заняться продвижением своих проектов. Пожелаем ему попутного ветра Писал про Aster меньше недели назад, уже +400% от точки входа, едем дальше. Про TWT писал в начале 2024, с таймингом не попал, но, надеюсь, попал с направлением графика. Для TWT партнерство означает существенный рост комиссий с торговли. Связка кошелек+DEX вполне заменяет CEX, удобнее и не требует верификации. @loudtrading

9custom 54538846479665249538🐳62

23 Sept 2025, 18:44 UTC276 views34 reactionsread 8 August 2026
Photo

"Да, денег становится больше, это хорошо" Вспоминаем пост про М2 и немного успокаиваем шортовые настроения. У биткоина довольно скудная техническая картина. Cильный шортовый моментум, -13% за 13 дней, кровавые свечи пугают любителей смотреть на график слишком часто. Если оценивать движение цены отдельно от фундаментала, можно увидеть разворот вниз и замашки на медвежий рынок. Однако, вместе с этим падением было лик

16👍13🐳5

Showing the 12 most recent of 20 posts we hold for @loudtrading. 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.

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

25 Sept 2025, 14:02 UTCAnonymous Poll62 voters

Ваши планы по крипте до конца года

  1. Докупаю и держу до 202624%
  2. Докупаю, но продам до 20265%
  3. Держу, продам до 202613%
  4. Держу, не продам до 202615%
  5. Продаю сейчас8%
  6. Уже все продал / без крипты35%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

25 Sept 2025, 14:02 UTCAnonymous Poll54 voters

Альтсезон

  1. Будет33%
  2. Не будет28%
  3. Уже был39%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 22 May 2025 to 31 January 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 1,064,557 of 1,169,250entries 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Trading Out Loud” (@loudtrading), 356 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/loudtrading.

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.