Channel
@AndrewCryptoZ
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
98,793subscribers
-1,968 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002104430532 |
|---|---|
| Type | Channel |
| Username | @AndrewCryptoZ |
| Description | Как стабильно получать доход на крипто рынке? Ты узнаешь в этом канале. Админ - @InflCrypto |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/AndrewCryptoZ |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 63% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. They sit inside a group of 8 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @CryptoDiaryX | 12 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @CryptoDiaryX (12–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 13 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 8, the earliest publisher we hold is @HoldBull. That is a statement about our reading window, not a claim of authorship.
82.9 average views per post against 98,931 subscribers — an engagement rate of 0.084%. Across the 8,255 registered channels in the same cohort — 31,626–99,998 subscribers, posting mainly in Russian — the middle half sit between 4.97% and 21.2%, with a median of 10.4%.
| Window | 30 days (21 July 2026 – 20 August 2026) |
|---|---|
| Posts measured | 25 of 25 published in the window (25 exact, 0 rounded by Telegram) |
| Views totalled | 2,073 |
| Mature posts only | 0.086% over 24 posts read at least 24h after publication |
| Subscribers | 98,931 measured 20 August 2026 |
| Cohort | b31623:rus · 8,255 channels · p10 2.39% · p25 4.97% · p50 10.4% · p75 21.2% · p90 36.7% |
| Position in cohort | 0.848th percentile · 1/125 the cohort median |
| Uncertainty | ±0.029% of the figure, from Telegram’s rounding |
| Post language | Russian · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the keys clone_copy · err_low, last confirmed 20 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 7 other registered channels, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 22:18 | 98,793 | -138 |
| 20 Aug 2026, 15:29 | 98,931 | -98 |
| 19 Aug 2026, 18:26 | 99,029 | -187 |
| 18 Aug 2026, 15:17 | 99,216 | -135 |
| 17 Aug 2026, 13:18 | 99,351 | -185 |
| 16 Aug 2026, 05:47 | 99,536 | -236 |
| 14 Aug 2026, 14:17 | 99,772 | -200 |
| 13 Aug 2026, 01:43 | 99,972 | -152 |
| 12 Aug 2026, 02:34 | 100,124 | -125 |
| 11 Aug 2026, 02:38 | 100,249 | -129 |
| 9 Aug 2026, 23:35 | 100,378 | -165 |
| 8 Aug 2026, 23:56 | 100,543 | -121 |
| 8 Aug 2026, 00:23 | 100,664 | -97 |
| 7 Aug 2026, 12:45 | 100,761 | first reading |
39 posts held, back to 13 July 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 36 pagesof 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 1 of 26 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 21 August 2026 |
|---|---|
| Posts held | 39 (13 July 2026 – 21 August 2026) |
| Views total | 2,080 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 12:03 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.
Lifetime counters from Telegram’s own channel header, read 22 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.
Дарим по 0.5 TON каждому… Стейкинг подарков под 358% По многочисленным просьбам, мы снова запускаем акцию по стейкингу подарков Даем ровно 3 дня до 23 августа 22:00. Всем, кто сделает депозит NFT подарком в @pilotka, мы переведем на ваш баланс по 0.5 TON за каждый добавленный подарок. Более того, мы увеличили заработок по стейкингу подарков до 358% ровно на 3 дня. Вывод подарка возможен в любое время. Подробнее п…
Осталось 15 минут И Мишка 🧸 может быть твой
Вам доступна бесплатная ставка в игровом режиме Арена Если вы сегодня еще не делали бесплатную ставку 🤓 Сделать бесплатную ставку
Зайдите в новый режим Арена и получите бесплатно 10 ⭐️ Получить
Для вас новый промо на фрикейс: casefree Доступно 800 активаций кейса Не забываем, что каждая ставка поднимает вас выше в турнирной таблице и вы сможете получить дороже подарок. Активируем промо на фрикейс в Pilot
Вам доступна бесплатная ставка в новом режиме Арена Сделать бесплатную ставку
Запустили розыгрыш на 5 000 ⭐️ и NFT подарки Рассылайте сообщение о розыгрыше в чаты и своим друзьям - за это вы получаете билеты. Так же билеты можно купить Чем больше билетов, тем дороже подарок получите. Принимай участие и забирай подарки 👇
Новый промо на фрибет для игры в Краш Промо: happystar Доступно 700 активаций ‼️Обязательно переключите игру на ⭐️ Stars, чтобы активировать промо, иначе промо будет считаться не верным. Активируем промо в N1 приложении по подаркам Pilot
Сделали уже бесплатную ставку в Арена? Самый легкий шанс, чтобы запутать большие иксы
Только что на моих глазах игрок сделал ставку в размере 50 ⭐️ и выиграл 4000 ⭐️ в Pilot Gift Он сделал 87x всего с 2 ставки в новом режиме Арена Вот это удача! Кто сможет больше?
Раздали новых Мишек 🎂 А еще сегодня кейсы хорошо выдают нфтишки
Турнир #2 в самом разгаре Уже через 9 дней топ-50 игроков получат призы. Первые 10 мест получат: 🎁🎁🎁🎁🎁🎁 Что нужно сделать, чтобы попасть в топ? Все достаточно просто, достаточно играть в любой режим: - Открывать кейсы - Краш - Арена - Ролл - Таймер Подробнее в посте - https://t.me/pilotgift/1293 А на каком вы месте в Турнире? Скидывайте скрины в комментарии
Showing the 12 most recent of 39 posts we hold for @AndrewCryptoZ. 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.
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.
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 20 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Andrew Crypto” (@AndrewCryptoZ), 98,793 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/AndrewCryptoZ.
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.