This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
2 measurements taken within a single day, net +6. 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 870–878 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Aug 2026, 02:06
877
+6
7 Aug 2026, 06:16
871
first reading
Engagement
19 posts held, back to 12 February 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 · 30 days
54.8%
avg views ÷ 877 subscribers
Avg views / post
480
12 posts measured
Reaction rate
0.625%
reactions ÷ views · ER floor
Posts in window
12
of 19 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. It is computed over the 7 of 12 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
19 (12 February 2026 – 6 August 2026)
Views total
5,764
Reactions total
22
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 06: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.
Reaction mix
38 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 47.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5226980520696513815
18
47.4%
❤
12
31.6%
🔥
4
10.5%
😁
4
10.5%
Custom emoji. One row above is a 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 count beside it isTelegram’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 11 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 38reactions 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 12 February 2026 to 6 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.
$HFT
Завтра в 12 часов по МСК будет делист этого токены с бинанс фьючей. Его качнули уже в 5 иксов (0.007-0.037)
Ситуация довольная частая с делистом с фьючей бинанса: накачка - делиcт - раз до нуля. Позу можно уже частями набирать на Гейте или Байбите
актуальные фреши:
0x9397c7394b4c0ea06f164a97023a61d7f821cfd2 15,000,000 HFT $525,000
0x593c553a69a03032c014023a7ce4373f46d022ff 14,999,997 HFT $525,000
0x1…
UPD по $ESPORTS
Первая четвёрка пуста — всё слили за 9–12 минут:
0x233dcf3636c64d7ede17a1b8aadc4917b912ca3d → $0
0xf457f4cd7ddc41e92dbdd6edb940881e7ebb96e7 → $0
0xa8e0b4a2d32d58b82e729215745cc55bb3b2aca9 → $0
0x94923d59928bb18aebf64f8064f32440cd7252c7 → $0
Хаб 0xcffe4c23… тоже в нуле
Но схема оказалась длиннее. Дробили не для продажи с каждого кошелька - токены снова стянули в одну точку:
0x7a7ad9aa93cd0a…
С Gnosis закидывают на фреш крупную сумму, дальше дробят её на несколько кошельков, параллельно пампя цену. Спустя 20–30 минут бьют по стакану через декс.
Так было уже 2 раза. Сейчас — третий: с Gnosis перевели на фреш.
Транзакция: https://bscscan.com/tx/0xa9a4db03172f5b10501ce1df2f0e5c2a7ef6bb4bd0a0c49ad6d27cb4a9f1948e
0x39cf4a13eddb4328b766d58fd673b147180db8a5 (Gnosis Safe) → 0xcffe4c239373e09815a501d1bb8c1bd1e0…
ДВИЖУХА ПО $LAB
Кошелёк-раздатчик
0xad3ab20ddd675e804a52a642d9d5f8ff1d256879
Создан пустым 28 июля. За полтора суток пропустил через себя $107M - вдвое больше капитализации токена
Полная хронология
28.07 16:59 — первая заливка $715K
28.07 17:34 — приходит $19.6M
28.07 17:49–17:50 — две тестовые ноги по $1 на 0x17C61f4a7f41b96eb9c0D8805255b8411387c63b и Gnosis Safe 0x0D81B1f99d65Ac1d34FFc3BFe0D206a9c7B25778. Прове…
Раскидка $OPEN на фреши
Со вчерашнего вечера идет раскидка токенов в два прохода. Капа 35кк$, топ-10 адресов держат 93% саплая.
Вчера вечером с этого кошелька раскинули 817к$ на два прокладочных:
0x453243D085E73f1Ed4fF1e1Dcf8a0F1f0d2b9780
Прокладочные:
0xB825d654c9A7C97a608907B80D4cD125adbCb38c
0x9D3F41d242C3CbFb3275cc60515B71893e4cde6b
Сегодня ночью пошла перекидка глубже — токены с прокладок и еще с 8 кошельк…
30 лямов баксов получили фреши в $AKE
Газ на транзу на кошелях уже есть за два часа до раздачи закинули с кукоина
Кошели:
0x7986fa5f64a0997f3b50990f2ba64f81d829ff9c
0x30a603dbd14981417b520ce96d2005d96c6fd275
0xcfbbe27f7fb368d15d3a278da85415e62e9706fa
0x998ef0e79a7574952d098d9b4e01f87d3fd864a8
0xa8da77a990638b75963ac923e6cc617dc7e20377
0x86ea348705c21fe04ed58061878b9bb507868dd4
0xc970decb237c291b255b16884b9707c3572…
Showing the 12 most recent of 19 posts we hold for @freakytrady. 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 — 182,967 of 1,160,990entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 4 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.
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.
“Freaky Trader” (@freakytrady), 877 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/freakytrady.
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.
