Channel
@GLITCH_cov
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
44subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002291264117 |
|---|---|
| Type | Channel |
| Username | @GLITCH_cov |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/GLITCH_cov |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 07:00 | 44 | no change |
| 11 Aug 2026, 06:53 | 44 | first reading |
18 posts held, back to 4 January 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 18 posts for this entry, the most recent from 13 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
149 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 14.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5326054635847308844 | 22 | 14.8% | |
| custom 5283011418499605504 | 21 | 14.1% | |
| custom 5348584118726718040 | 20 | 13.4% | |
| custom 5327921340303299330 | 19 | 12.8% | |
| custom 5289618401050776596 | 18 | 12.1% | |
| custom 5397868344462290339 | 18 | 12.1% | |
| custom 5327818982642701259 | 17 | 11.4% | |
| custom 5328189896018382840 | 14 | 9.40% |
Custom emoji. Every 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 counts beside them areTelegram’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 10 of the 18 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 149reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 4 January 2026 to 13 January 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.
Группа временно закрыта на рест. Обещаем вернуться в ближайшее время. Набор оставляем открытым ❤️
custom 53279213403032993303custom 52896184010507765962custom 52830114184996055041custom 53260546358473088441custom 53278189826427012591custom 53281898960183828401custom 53485841187267180401custom 53978683444622903391
Sticker, posted without a caption
Заявок совсем нет… мы вас ждем!
custom 53278189826427012592custom 52830114184996055041custom 52896184010507765961custom 53260546358473088441custom 53978683444622903391
Sticker, posted without a caption
🤩🤩🤩🤩—° 🤩rᥲᥴᴛiᥴᥱ 🫀 Τι 🤩🤩🤩🤩[두 번] 🔤 Prototype 💙 |«I won’t gi᥎ᥱ ᥙρ ᧐ᥒ ⲙysᥱᥣf, I'ᥣᥣ κᥱᥱρ rᥙᥒᥒiᥒg ᴛ᧐ᥕᥲrɗs ⲙy ɗrᥱᥲⲙs»| 🌸 κοντά 👀👀👀👀 just ♾️♾️♾️♾️♾️♾️ Минутку этого чудесного январского дня стоит уделить практике нашей Мишельки!! 彼女が生きている間 #MICHELLE | ^√ @woodooOI ▫️*: / 🍪 🪦🪦
custom 53260546358473088446custom 53279213403032993305custom 53978683444622903394custom 52830114184996055042custom 52896184010507765961custom 53278189826427012591custom 53281898960183828401custom 53485841187267180401
Sticker, posted without a caption
Закрываем анон!! Всем спасибо 🎁
custom 53281898960183828402custom 52896184010507765961custom 53279213403032993301custom 53978683444622903391
🤩🤩🤩🤩—° 🎀non 🫀 Τι 🤩🤩🤩🤩[두 번] 🔤 Prototype 💙 |«I won’t gi᥎ᥱ ᥙρ ᧐ᥒ ⲙysᥱᥣf, I'ᥣᥣ κᥱᥱρ rᥙᥒᥒiᥒg ᴛ᧐ᥕᥲrɗs ⲙy ɗrᥱᥲⲙs»| 🌸 κοντά 👀👀👀👀 ♾️N0N with 🤩&🎀 🤩 - <tap> 🪦 ང༥ᜎ༏٤ 🪦🎀 - <tap> ^√ @woodooOI ▫️*: / 🍪 🪦🪦 𐍃ᴛᥱρ one, ɗ᧐ ⲙy ɦigɦᥣigɦᴛ, 𐌑ᥲκᥱ ⲙᥱ sɦiᥒᥱ s᧐ δrigɦᴛ iᥒ ᴛɦᥱ ⲙ᧐᧐ᥒᥣigɦᴛ | 🤩🤩
custom 53278189826427012595custom 52896184010507765963custom 53485841187267180403custom 53260546358473088442custom 53279213403032993302custom 53281898960183828402custom 52830114184996055041custom 53978683444622903391
Sticker, posted without a caption
Мы ждём заявки!!
custom 52830114184996055044custom 53279213403032993303custom 53485841187267180402custom 52896184010507765961custom 53260546358473088441custom 53978683444622903391
Sticker, posted without a caption
🤩🤩🤩🤩—° 🎀udition 🫀 Τι 🤩🤩🤩🤩[두 번] 🔤 Prototype 💙 |«I won’t gi᥎ᥱ ᥙρ ᧐ᥒ ⲙysᥱᥣf, I'ᥣᥣ κᥱᥱρ rᥙᥒᥒiᥒg ᴛ᧐ᥕᥲrɗs ⲙy ɗrᥱᥲⲙs»| 🌸 κοντά 👀👀👀👀 / 🌩۲٤٤ — ♾️ᥲyᥱ᧐ᥒ ✨ #오디션 ! 🤩 #woodoo 🌟🌟🌟 🍓 🌟usy — 💄 —° ot 🔡💙💙 ➿➿➿➿➿➿➿➿➿➿➿ (終わり) 𑀝᧐᧐δщᥱнᥙᥱ ᧐ᴛ Э᧘ρᥙн (δыʙɯᥱᥔ учᥲᥴᴛнᥙцы ᥙ ᧘ᥙдᥱρᥲ): Всем привет, это Элрин. Радостных новостей не будет, скажу прямо. Я покидаю ои. Почему? Раньше я видела здесь поддержку, видела здесь своё место. Сейчас это исчезло.…
custom 53281898960183828406custom 52830114184996055045custom 53485841187267180404custom 53260546358473088443custom 53279213403032993303custom 52896184010507765962custom 53278189826427012592custom 53978683444622903392
Showing the 12 most recent of 18 posts we hold for @GLITCH_cov. 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 — 1,110,065 of 1,183,361entries 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 2 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.
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.
@GLITCH_cov named 1 handle 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“.” (@GLITCH_cov), 44 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/GLITCH_cov.
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.