$GLITCH | Glitch on Sol is being protected by @Safeguard Click below to verify you're human

Channel
$GLITCH Portal
@imglitchonsol
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
321subscribers
+310 since we began measuring on 17 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003918745137 |
|---|---|
| Type | Channel |
| Username | @imglitchonsol |
| Created | 8 October 2026 — measured — dated from the channel’s first post |
| First recorded | 17 October 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/imglitchonsol |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 5 November 2026 and assigned it the closest of 31 fixed categories, at 76% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 07:16 | 321 | +49 |
| 30 Oct 2026, 04:20 | 272 | +67 |
| 23 Oct 2026, 20:37 | 205 | +192 |
| 17 Oct 2026, 15:49 | 13 | +2 |
| 17 Oct 2026, 14:22 | 11 | no change |
| 17 Oct 2026, 13:47 | 11 | first reading |
Engagement
3 posts held, back to 8 October 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 91.9%
- avg views ÷ 321 subscribers
- Avg views / post
- 295
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 3 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 8 October 2026 |
|---|---|
| Posts held | 3 (8 October 2026 – 8 October 2026) |
| Views total | 295 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Oct 2026, 14:22 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
Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Channel name was changed to «$GLITCH Portal»
Channel created
Showing the 3 most recent of 3 posts we hold for @imglitchonsol. 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.
Mentions
Named by 24 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.
@solearlytrending · 104,29713 postsSolana Whale Trending 🐳💵
@solwhaletrending · 36,6967 postsClasier Calls 🇺🇸
@ClasierCalls · 41,8654 postsSolbix Community Calls
@csolbix · 38,0562 posts𝗦𝗢𝗟 𝗧𝗥𝗘𝗡𝗗𝗜𝗡𝗚 | @𝗠𝗮𝗷𝗼𝗿𝗧𝗿𝗲𝗻𝗱𝗶𝗻𝗴
@MajorSOLTrending · 40,7142 postsSOLANA📈DRAGON🐉CALLS☎️
@Solanadragoncalls · 32,8542 postsCall Analyser
@CallAnalyser · 50,4801 postCrypto King Call
@Crypto_KingCall · 130,0201 post𝐂𝐑𝐘𝐏𝐓𝐎 𝐑𝐀𝐕𝐄𝐍 𝐂𝐀𝐋𝐋 🇯🇴
@CRYPTO_RAVEN_CALL · 29,0751 post𝐂𝐑𝐘𝐏𝐓𝐎 𝐒𝐇𝐈𝐋𝐋𝐈𝐍𝐆 𝐆𝐄𝐌𝐒
@crypto_ShillingGems · 29,5831 post𝐂𝐫𝐲𝐩𝐭𝐨 𝐂𝐨𝐢𝐧𝐋𝐚𝐛 𝐂𝐚𝐥𝐥𝐬
@CryptoCoinLabCalls · 13,0811 postCrypto Lord Gems 💎
@CryptoLordGem · 144,0461 post𝗖𝗿𝘆𝗽𝘁𝗼 𝗦𝗰𝗼𝗿𝗽𝗶𝗼𝗻𝘀 𝗖𝗮𝗹𝗹'𝘀 🦂
@CryptoScorpioncalls · 19,9121 post𝐂𝐫𝐲𝐩𝐭𝐨 𝐖𝐨𝐫𝐥𝐝 𝐒𝐢𝐠𝐧𝐚𝐥𝐬 📈🚀
@Cryptoworldsignlas · 14,6511 post𝗖𝗿𝘆𝗽𝘁𝗼 𝗫 𝗛𝗶𝗴𝗵 𝗚𝗲𝗺𝘀 💎
@CryptoXhighGems · 18,9131 post𝐃𝐚𝐫𝐤 𝐇𝐨𝐫𝐬𝐞 𝐆𝐞𝐦𝐬 🐎
@DarkHorseGems · 15,7861 postDeFi Million 💎
@DeFeMillion · 44,2171 post𝐊𝟐 𝐂𝐫𝐲𝐩𝐭𝐨 𝐜𝐚𝐥𝐥'𝐬 🏔️
@K2Cryptocall · 20,6641 postLizard Calls ⛳️💎
@LizardCall · 29,5471 post𝗟𝘂𝗰𝗶𝗳𝗲𝗿 𝗖𝗮𝗹𝗹𝘀
@LucifersCalls · 38,1781 post𝚃𝙷𝚄𝙽𝙳𝙴𝚁 𝚂𝚃𝙰𝙻𝙻𝙸𝙾𝙽 𝙺𝙾𝙻𝚂 | 中国鲸鱼热点
@STALLION_KOLS · 29,8181 post💎𝑻𝑯𝑬 𝑪𝑹𝒀𝑷𝑻𝑶 𝑮𝑬𝑴𝑺💎
@TheCryptogems1 · 18,1831 post𝐖𝐡𝐚𝐥𝐞'𝐬 𝐂𝐫𝐲𝐩𝐭𝐨 𝐂𝐚𝐥𝐥𝐬
@Whales_CryptoCalls · 24,3521 post华人社区 Whales China 🚀 🇨🇳
@WhalesChinaNews · 18,4751 post
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.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“$GLITCH Portal” (@imglitchonsol), 321 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/imglitchonsol.
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.