Channel
@WishExes
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
8subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003894425116 |
|---|---|
| Type | Channel |
| Username | @WishExes |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/WishExes |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:32 | 8 | no change |
| 6 Aug 2026, 09:38 | 8 | first reading |
20 posts held, back to 31 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 1 pageof 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.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 20 (31 July 2026 – 9 August 2026) |
| Views total | 103 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 13:32 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 12 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.
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ Salute to your inner fire, champions! (+08) @carmodice, @CIPHERLEO, @hooniversea, @kyatales, @pillowpuffs, @alphadive, @AHNORB &. @euvorian. ㅤㅤ / More brilliant still, with steadier grace and turn each match to triumph’s face. May conquest relentlessly queue in your favor, < sincerely, @WishExe > 📲🌀🎮 ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ Salute to your inner fire, champions! (+07) @whimsyian, @yuhagloss, @SeanLeague, @Hyeonxile, @enchoire, @seveessence, @cloevian, @Naderria, @leeanother, @hyunellas, @Wonchestra, @vickysoiree, @loleeans. / More brilliant still, with steadier grace and turn each match to triumph’s face. May conquest relentlessly queue in your favor, …
Hallo champions! Apakah boleh bantu kami untuk forward pesan ini? Jika ada yang mau diforward juga bisa disampaikan ke @WishDocsbot ya 👍
Selamat pagi 👍🏻
𝚞𝚗𝚍𝚎𝚛 𝚓𝚞𝚕𝚢'𝚜 30𝚝𝚑 𝚍𝚊𝚠𝚗 time has drifted ever so gently, scattering cherished moments like petals upon the breeze ˚₊‧♡ ੈ * as another mensiversary quietly unfolds, we honor @ianlune, @WishExe, and @Thecoleony a haven where silent dreams awaken beneath tranquil skies. may every heart forever flourish, carried by gentler winds toward endless horizons! ✨🤍
ㅤㅤㅤ✚ SYSTEM LOG : MILESTONE ㅤㅤ “ANOTHER CYCLE DETECTED.” RADAR STATUS ® :: Time passed through static noise and corrupted frequencies, yet your signal remained clear; @TheColeony @WishExe @Markscapee @ianlune Despite every interference, the connection persists. [ MONTH ] OF SYNCHRONIZED SIGNALS.
ㅤ “CADENCE.” / ELD─ICH (‘INVOCATION): Whispered beneath withering incense, the dormant gate of perception was unwittingly sundered open ´ཀ Permitting the spirit to trespass upon realms veiled from mortal / (DISCERNMENT.) @Thecoleony @WishExe @MARKSCAPEE @ianlune. Each slumber became a pilgrimage across the astral abyss, “where entities drifted amidst ruined sanctuaries.” …
ㅤ .• 🪶 Behold, another leaf hath quietly turned within the little tale ye weave together, leaving behind more laughter, more memories, and those moments which grow precious simply because they were shared. “Every season hath its own flower, and every passing day its own story” So too doth this little garden grow in its own time. May your circle continue to find new ways to bloom, with every passing month adding anoth…
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ ( ±± 30 ✷ ) ─── Happy mensive to our dearest @Thecoleony @STROKKIS and @WishExe. Thank you for staying through quiet days and midnight hush, may our bond remain soft yet unbroken, like starlight bleeding through nocturnal void. 🀦 ۫ ׅ ㅤㅤㅤㅤ 𝘞𝘢𝘳𝘮𝘦𝘴𝘵 𝘳𝘦𝘨𝘢𝘳𝘥𝘴, ﹫ 𝘑𝘦𝘦𝘳𝘪𝘰𝘶𝘴. ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ
ㅤ Through The Forbidding Bestowment / Wuthering tides meandered throughout fathomless pavement. Unravel the chronicles amongst befogged journey: @WishExe @TheColeony @BOYNEXTAGE @ianlune. May your path be filled with perpetual jubilation. Inked within sincerity, @HYEVION. ㅤ
ㅤ 𓂃 ☁️ 𝘤𝘭𝘰𝘶𝘥𝘮𝘢𝘪𝘭 𝘥𝘦𝘭𝘪𝘷𝘦𝘳𝘦𝘥 📮 to : @MARKSCAPEE @WishExe @Thecoleony 🎀 the residents of our little pastel house have gathered to celebrate your special milestone today! seeing your circle bloom with beautiful friendships and cherished memories feels like watching strawberry blossoms sway beneath a baby-blue sky. 🌷☁️ 🐈 may your days be filled with comfort, happiness, and people who genuinely care for you. 🩷 sendin…
ㅤ #MIDNIGHTGARAGE ★ MONTHLY SIGNAL, (30—∞) STILL LOUD. Another month passed and somehow we’re still here. Thanks for staying through the noise, chaos, and random frequencies together. 🤘🔇 @ianlune, @TheColeony, @WishExe, @MARKSCAPEE / Static stays alive. —) ㅤ
Showing the 12 most recent of 20 posts we hold for @WishExes. 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,105,495 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.
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.
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.
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.
“W!SH.EXE 📁 D0C$.” (@WishExes), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/WishExes.
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.