#WIRE +60%

Channel
Герман на блокчейне 🇪🇹
@blockchaingerman
On this record: Previous handles · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
33,449subscribers
-118 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001293287526 |
|---|---|
| Type | Channel |
| Username | @blockchaingerman |
| Created | 12 February 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/blockchaingerman |
Previous handles
Recorded in 2019 as “Герман на блокчейне” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:17 | 33,449 | -18 |
| 12 Aug 2026, 02:46 | 33,467 | -10 |
| 11 Aug 2026, 01:42 | 33,477 | -12 |
| 10 Aug 2026, 00:42 | 33,489 | -21 |
| 8 Aug 2026, 21:07 | 33,510 | -17 |
| 7 Aug 2026, 23:05 | 33,527 | -21 |
| 6 Aug 2026, 19:20 | 33,548 | -19 |
| 6 Aug 2026, 01:50 | 33,567 | no change |
| 6 Aug 2026, 00:25 | 33,567 | first reading |
Engagement
45 posts held, back to 2 August 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 17 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 7.48%
- avg views ÷ 33,449 subscribers
- Avg views / post
- 2,500
- 45 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 45
- of 45 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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 45 (2 August 2026 – 12 August 2026) |
| Views total | 112,571 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 21:09 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.
Recent posts
#WIRE есть контакт
#bStocks Binance пушит токен стокс https://x.com/motier_crypto/status/2087466693039960562 0x244B112Cf746e62A5DF723cbDe9906a6dEfd7777
#HMM x10 монета запущена через Wire (bankrbot для Robinhood). Мкап WIRE в 16 раз меньше HMM 🤔 0x8ECEA3d0E648DB646d824AA51EedeB16aC3d6878
#BOT новый продукт от Grok/SpaceX/Маска. Grok companion Ani в своё время раскачали до $80М. В pvp пока побеждает токен с пампфана: HukaK2eHhbTyiuUwuKMntjPJP4aGdD4VwiExsNmyT8WJ
https://x.com/avgjoescrypto/status/2086889992035717166
#STONK есть контакт
#JUGGERNAUT любимый мем Влада Тенева. Cashcat на хаях, тут график смотрит наверх 0xD7321801CAae694090694Ff55A9323139F043B88
С понедельника повышаем стоимость доступа: $90 за 60 дней вместо трёх месяцев. Если присматривались к группе, до конца воскресенья ещё можно оформить 90 дней за $90. Вступить 👉 @german_intraday_bot
#TOAD кабал коин пампфана https://x.com/kanzox0/status/2086321243012141565 A13oRB9FFaiUjfi6LdCg6p9ka1u8SfGkUFs4SKvPpump
#STONK лаунчпад на солане, где можно запустить токен в паре со всем, что торгуется на солане, было бы желание. Шанс Соланы и Raydium забрать себе часть рынка stock tokens AbNNre5ac5QbKDeNgSArBEdATgCZz6pu17jiRSxrxDDU
С понедельника повышаем стоимость доступа: $90 за 60 дней вместо трёх месяцев. Если присматривались к группе, до конца воскресенья ещё можно оформить 90 дней за $90. Вступить 👉 @german_intraday_bot
Showing the 12 most recent of 45 posts we hold for @blockchaingerman. 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 — 129,487 of 1,151,006entries 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.
@mahfavaboyz · 2,0882 postsBTC Intraday
@BTCIntraday · 2,6921 postГлебчик aka Fucckt 🥩
@fuckkt_web30 · 3,1671 postКриптология
@kripto_mozg · 141 postNZT-RESEARCH🧑💻
@NZT_RESEARCH · 2431 postРедакция
@redaktionen · 261 postVendettA
@vendettanews · 551 postYour AirDrop 🚀
@x100airdropp · 411 postY thoughts
@ymarketthoughts · 81 post
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.
Mentions
Named by 6 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.
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.
@ondreigoichev · 162,334
Telegram ranks this channel #62 of 72 here — alongside 71 others — read 12 August 2026
@drops_analytics · 683,618
Telegram ranks this channel #66 of 95 here — alongside 94 others — read 10 August 2026
@markettwits · 334,480
Telegram ranks this channel #77 of 95 here — alongside 94 others — read 10 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Герман на блокчейне 🇪🇹” (@blockchaingerman), 33,449 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/blockchaingerman.
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.