Channel
@litrasimay
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
20subscribers
+1 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002019161017 |
|---|---|
| Type | Channel |
| Username | @litrasimay |
| Created | 20 March 2024 — measured — dated from the channel’s first post |
| First recorded | 24 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/litrasimay |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 04:14 | 20 | +1 |
| 25 Aug 2026, 05:04 | 19 | no change |
| 24 Aug 2026, 10:46 | 19 | first reading |
13 posts held, back to 20 March 2024 — 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 15 August 2026 |
|---|---|
| Posts held | 13 (20 March 2024 – 15 August 2026) |
| Views total | 9 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Aug 2026, 10:46 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.
43 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 60.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤔 | 26 | 60.5% | |
| ❤ | 8 | 18.6% | |
| 🍌 | 6 | 14.0% | |
| 👍 | 3 | 6.98% |
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 6 of the 13 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 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 20 March 2024 to 15 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.
࿀ ׁ 🀦 pembayaran hanya di lakukan dengan nomor di bawah ini 🤩 e-wallets Dana : 085710200172 An i Shopeepay : 085710200172 an I Gopay : 085710200172 an I Ovo : 085710200172 an I 🤩 bank account BCA : 6755381369 an I JAGO : 106332167757 an I 💸 Coin nitrosen : 5156093601 jangan lupa setelah melakukan pembayaran, untuk mengirim bukti pembayaran tanpa edit dan crop ke room chat pemilik channel payment ini 시칸틱!
Qris polosan, admin 1k untuk semua EWALET
💆♀️
🥳
https://t.me/jual_beli_chanel_dan_grup store ku pindah kesini ya, soal ya ch yang lama ke ban 🙏😭
🤔2
Mimin rekomendasikan rekber aman dan terpercaya, tp selalu juga cek admin nya biar engak kena clone, rekber nya udah masuk sini atau belum, rekber aman hanya di : ✅@jelas_aman ✅@arearekber ✅@rekberml ✅@availrekber ✅@Rekberfamousss ✅@rekberfamouss ✅@rekberfamaous ✅@rekberfamousba ✅@rgekberfamous ✅@infoorekberf…
❤1
🎁
Tidak ada admin lain temen kerabat dan yang lain nya, jadi lebih extra baca dan bertanya, jangan gelap mata atau yang lain nya, 😎
🤔24
😊
👍3
渴望 “.. 📎 ── • morning comes and sets aside night, all life wakes up from its sleep and night comes / . . sets aside morning, the moon and shining stars cover sleeping life. ── 1987 : 🖨 "Working hours". ( 2ND • “MOONLIGHT”─) ☾- ’ › Senin - minggu : 09.00 - selesai Note :: The hours listed are uncertain, sometimes online/offline outside the hours listed 𓇼𓂂ⓘ ─── ·
🍌6
😊
📖 BUDIDAYAKAN MEMBACA 📖📖 𐚈..) “雜誌” writing a masterpiece with an occasional sip of tea to give warmth to the fall 📽️ . . in the company of a loved one is an interesting fantasy. • firstly account • ㅤㅤ 𖤝 .. | @ueesaerom 5156093601 • aktif account • ㅤㅤ 𖤝 .. | @Sherinkuq 1893193290 • userbot • 𖤝 .. | @Mayasistenbot ㅤ…
❤7
Showing the 12 most recent of 13 posts we hold for @litrasimay. 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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“Literasi tempat may” (@litrasimay), 20 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/litrasimay.
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.