Posted without readable text
custom 5469889929494439762114custom 546964189083812798853custom 547011603375276943937custom 54699389093014819029custom 54699471599336591224custom 54698473277138318151

Channel
@char_me_d
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
1,193subscribers
+89 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003741968227 |
|---|---|
| Type | Channel |
| Username | @char_me_d |
| Created | Between 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/char_me_d |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 09:20 | 1,193 | +15 |
| 2 Sept 2026, 11:54 | 1,178 | +6 |
| 30 Aug 2026, 20:28 | 1,172 | +10 |
| 27 Aug 2026, 21:04 | 1,162 | +15 |
| 25 Aug 2026, 00:37 | 1,147 | +13 |
| 21 Aug 2026, 12:23 | 1,134 | +16 |
| 18 Aug 2026, 20:45 | 1,118 | +12 |
| 15 Aug 2026, 20:55 | 1,106 | +2 |
| 15 Aug 2026, 10:02 | 1,104 | first reading |
10 posts held, back to 5 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 1 page of 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 14 August 2026 |
|---|---|
| Posts held | 10 (5 August 2026 – 14 August 2026) |
| Views total | 1,051 |
| Reactions total | 526 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 10:02 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.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
1,828 reactions across 10 posts, in 23 distinct kinds. The most used accounts for 17.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5454025162116605080 | 322 | 17.6% | |
| 💘 | 258 | 14.1% | |
| custom 5271778391098413151 | 200 | 10.9% | |
| custom 5469891544402143425 | 176 | 9.63% | |
| custom 5271882578415082400 | 149 | 8.15% | |
| custom 5469889929494439762 | 122 | 6.67% | |
| custom 5469641890838127988 | 116 | 6.35% | |
| custom 5271805887479043187 | 115 | 6.29% | |
| custom 5453914098557296299 | 90 | 4.92% | |
| custom 5469938909301481902 | 54 | 2.95% | |
| custom 5271539986053749063 | 51 | 2.79% | |
| custom 5454391149164800189 | 40 | 2.19% | |
| custom 5470116033752769439 | 39 | 2.13% | |
| custom 5454082203577266054 | 34 | 1.86% | |
| custom 5469947159933659122 | 14 | 0.766% | |
| custom 5273890552935370731 | 11 | 0.602% | |
| custom 5456556169164269157 | 9 | 0.492% | |
| custom 5271654747579896495 | 7 | 0.383% | |
| custom 5454112779449442438 | 7 | 0.383% | |
| custom 5454186163260663269 | 7 | 0.383% | |
| 3 further kinds | 7 | 0.383% |
Custom emoji. 19 of the rows above are 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 are Telegram’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 10 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 1,828 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 5 August 2026 to 14 August 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @char_me_d. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 10 most recent posts we hold for this entry, published 5 August 2026 to 14 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Posted without readable text
custom 5469889929494439762114custom 546964189083812798853custom 547011603375276943937custom 54699389093014819029custom 54699471599336591224custom 54698473277138318151
Posted without readable text
custom 5469891544402143425176custom 546964189083812798863custom 546993890930148190245custom 546994715993365912210custom 54698899294944397628custom 54698707352855922664custom 54701160337527694392
Posted without readable text
custom 5454025162116605080151custom 545391409855729629945custom 545439114916480018938custom 54541127794494424385custom 54538959952701450952custom 54541861632606632692
Posted without readable text
custom 5454025162116605080170custom 545391409855729629944custom 545408220357726605434custom 54565561691642691575custom 54541861632606632694custom 54541127794494424382custom 54543911491648001892
File, posted without a caption
custom 527177839109841315132custom 527180588747904318715
🌟🌟🌟 🌟🌟🌟#кагеяма #эстетика 🌟🌟 🤩 ᥴhᥲrⲙᥱᦔ | haikyuu • хедканоны
custom 5271778391098413151108💘39custom 527180588747904318730custom 52738905529353707316custom 54565561691642691574custom 54539140985572962991custom 54540251621166050801custom 54541861632606632691
File, posted without a caption
custom 527180588747904318728💘9custom 52717783910984131516custom 52718825784150824001
🌟🌟🌟 🌟🌟🌟#куроо #эстетика 🌟🌟 🤩 ᥴhᥲrⲙᥱᦔ | haikyuu • хедканоны
custom 5271882578415082400148💘40custom 527177839109841315129custom 52715399860537490634custom 52718058874790431873custom 52738905529353707311
File, posted without a caption
custom 527177839109841315121💘7custom 52718058874790431872
🌟🌟🌟 🌟🌟🌟он влюблён. 🌟🌟 #хедканоны #сакуса #онвлюблён 🤩 ᥴhᥲrⲙᥱᦔ | haikyuu • хедканоны
💘163custom 527153998605374906347custom 527180588747904318737custom 52716547475798964957custom 52717783910984131514custom 52738905529353707314
Showing the 10 most recent of 10 posts we hold for @char_me_d. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“ᥴhᥲrⲙᥱᦔ | haikyuu!! • хедканоны” (@char_me_d), 1,193 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/char_me_d.
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.