Channel
@geblasse
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
3subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003875800307 |
|---|---|
| Type | Channel |
| Username | @geblasse |
| Created | 2 March 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/geblasse |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 10:49 | 3 | no change |
| 10 Aug 2026, 07:31 | 3 | first reading |
6 posts held, back to 2 March 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 14 May 2026. An engagement rate over an empty window would be a number about nothing.
Союз лист Нами Каро 1. @BizOrion — @XCCDFZXC Доп:@arsensult 2. @FerynM — @Wx7DZ 3. @AR1RVNG — @Usedalii 4. @KURA_MA — @gloosan 5. @kanybekovvy — @dxxsye 6. 7. @motimkmg — @mksxsss 8. @teyitknf — @qptrws 9. @evoquefm — @adgress 10. @zhannovvyy — @zhannkvn 11. @hirdfml — @AZHIRD 12. @GiN7Xi — @ishinbolbosunnnn 13. @ZaganFm — @elzk1z 14. @Begierdev — @Deffrra 15. @omarbekovy — @xdarkvex 16. @zhetimskie — @tdrso 17. @Den…
Signed 𝓝𝓪𝓶𝓲 𝓚𝓪𝓻𝓸
союзы: 1. @kanybekovvy - @dxssye: доп: @ser1kovas_088 2. @DIADOR_FM ‐ @dam11r3 3. @FerynM - @Wx7DZ 4. @motimkmg - @mksxsss 5. @atanovy - @poiuytrellm 6. @ZaganFm - @elzk1z 7. @AR1RVNG - @Usedalii 8. @Manapofm - @Xrj6z 9. @omarbekovy - @xdarkvex 10. @musichea1s - @a1tmatovvv доп: @felisdds 11. @mustang_faml - @ssmmiiltt доп: 12. @zhetimskie - @tdrso доп: @a1shol 13. @evoquefm - @adgress 14. @GiN7Xi - @tm1led 15. @zhan…
Sticker, posted without a caption
rules union 1. союзы 0+ пдп. 2. рп держится 1-2 часа. 3. рп проводится в свободное время админа. выходные (сб-вс) 4. подписки 1:1. 5. без поста, сразу в союз лист. 6. в конфликтах мы на нейтральной стороне. 7. в чистках не участвуем. 8. заключаем союзы с кр/кз кф, семьями, студиями. разрыв если: 1. если ваш следящий не подписан на нас. 2. нас нету в союз листе. 3. не будет рп с вашей стороны. 5. не предуп…
Channel name was changed to «Geblass Union»
Channel created
Showing the 6 most recent of 6 posts we hold for @geblasse. 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 — 395,953 of 1,481,346entries 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.
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.
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.
@geblasse named 24 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Geblass Union” (@geblasse), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/geblasse.
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.