Telegram RegisterThe public register of Telegram
Telegram profile photo for Home trade 🐳

Channel

Home trade 🐳

@HomeTtrade

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

1,097subscribers

+53 since we began measuring on 23 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001752524771
TypeChannel
Username@HomeTtrade
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live2 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/HomeTtrade

Growth

1,0441,0971,070.523 August 2026 — 1,044 subscribers24 August 2026 — 1,045 subscribers27 August 2026 — 1,047 subscribers30 August 2026 — 1,094 subscribers2 September 2026 — 1,097 subscribers23 August 20262 September 2026
5 measurements spanning 10 days, net +53. 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 1,036–1,105 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 03:371,097+3
30 Aug 2026, 03:231,094+47
27 Aug 2026, 12:021,047+2
24 Aug 2026, 05:451,045+1
23 Aug 2026, 04:451,044first reading

Engagement

14 posts held, back to 2 July 2026the 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 · 30 days
40.4%
avg views ÷ 1,097 subscribers
Avg views / post
443
7 posts measured
Reaction rate
3.48%
reactions ÷ views · ER floor
Posts in window
7
of 14 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 August 2026
Posts held14 (2 July 202618 August 2026)
Views total3,102
Reactions total108
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Aug 2026, 04:45 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.

Reaction mix

153 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 37.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥5737.3%
👍5032.7%
🐳3019.6%
😁74.58%
😭63.92%
💩21.31%
👌10.654%

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 14 of the 14 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 153 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 2 July 2026 to 18 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.

Recent posts

18 Aug 2026, 07:44 UTC374 views23 reactionsread 23 August 2026
Video message

Video message, posted without a caption

❤‍🔥12👍8🐳3

16 Aug 2026, 08:31 UTC454 views18 reactionsread 23 August 2026
Video message

Video message, posted without a caption

❤‍🔥10👍5🐳3

16 Aug 2026, 08:29 UTC448 views11 reactionsread 23 August 2026
Video message

Video message, posted without a caption

❤‍🔥9👍2

16 Aug 2026, 07:01 UTC426 views16 reactionsread 23 August 2026
Video message

Video message, posted without a caption

👍7❤‍🔥6🐳3

15 Aug 2026, 11:44 UTC460 views3 reactionsread 23 August 2026

Ну а трейдинг будет через пару дней когда все подключу и сделаю нормальный интернет (потерпите)))

👍3

15 Aug 2026, 11:42 UTC456 views15 reactionsread 23 August 2026
Video message

Video message, posted without a caption

🐳10👍5

15 Aug 2026, 05:41 UTC484 views22 reactionsread 23 August 2026
Video message

Video message, posted without a caption

❤‍🔥18🐳4

5 Aug 2026, 18:09 UTC853 views4 reactionsread 23 August 2026
Photo

Так по чуть кликал под стрим по доте. (Отвечаю с кайфом бы стал стримером) Неделя без сделок на сейве перед переездом. Не хочу запилиться в мертвом рынке и уезжать с плохим настроением. Хотя весь месяц будет в таком режиме Пока приеду, пока обустроюсь, привыкну к новому рабочему месту.

🐳4

31 Jul 2026, 11:06 UTC846 views3 reactionsread 23 August 2026
Photo

Думаю по коме может быть такой же выход как на ммт. Вчера пытался набраться перед уровнями, кидал основную пачку в хай, никуда не шло. Ночью смотрел как пробили наклонку и улетели вниз, думал на этой коррекции подобрать и оставить пол пачки на перехай.( все закрыл и пошел спать) Просыпаюсь эта дура + 80 процентов)) Так и живем

😁3

31 Jul 2026, 10:37 UTC621 views3 reactionsread 23 August 2026
Photo

Чуть-чуть не дотянул)) По привычке был сосредоточен на заточке, а надо было просто лонговать с участником...

👍3

29 Jul 2026, 10:20 UTC690 views9 reactionsread 23 August 2026
File

Скоро будут новые видосы на ютубе. Парочку уже записал, осталось смонтировать. Подготовил контент на перед, скоро удаление зубов мудрости🥲 И опять переезд✈️

👍5❤‍🔥2🐳1😁1

15 Jul 2026, 13:42 UTC907 views11 reactionsread 23 August 2026
Photo

Налудил Хотел взять отскок, потом пробить. Винрейт 0 🤷 Заканчиваю по просадке..

😭6👍3👌1💩1

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

RdnScalp
@rdnscalp · 32,194
Telegram ranks this channel #56 of 68 here — alongside 67 others — read 5 September 2026
PussyScalper
@KingofTilt · 57,277
Telegram ranks this channel #68 of 72 here — alongside 71 others — read 23 August 2026
DIGAHKA - СКАЛЬПИНГ
@digahkaaaa · 41,607
Telegram ranks this channel #71 of 73 here — alongside 72 others — read 29 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Home trade 🐳” (@HomeTtrade), 1,097 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/HomeTtrade.

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.