Channel
@jsjsjsjaqie
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
29subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002572884999 |
|---|---|
| Type | Channel |
| Username | @jsjsjsjaqie |
| Created | Between 1 March 2025 and 31 July 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/jsjsjsjaqie |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 05:31 | 29 | no change |
| 8 Aug 2026, 06:47 | 29 | first reading |
20 posts held, back to 31 August 2025 — 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 24 July 2026 |
|---|---|
| Posts held | 20 (31 August 2025 – 24 July 2026) |
| Views total | 57 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 05:31 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 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.
104 reactions across 20 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💘 | 104 | 100.0% |
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 20 of the 20 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 104reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 August 2025 to 24 July 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.
всем привет подписчики!!! извините что прерываю вашу любимую радугу дугу, но хотела сказать что у этого хелпа появился собственный тт, кому не лень подпишитесь пожалуйста 🤩 user9384319557692 или же можете найти по нику • хелп дорамной •
💘3
взял пиар у @Rita_tg, приход был, все оч быстро прошло и четко
💘3
оцените канал 🥹
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
💘6
Купил пиар у @Rita_tg, актив хороший, очень рекомендую, а также все честно и быстро
💘3
НАБОР АДМИНОВ!!! ❗ что от вас требуется? 🤍 активность, 🤍 умение, 🤍 свободное время 🤩🤩🤩🤩🤩🤩 ❗анкета: 🤍 имя/псевдоним 🤍 возраст 🤍 ваш канал с нарезками/где вы были админом 🤍 ваши работы 🤍 сколько времени можете уделять каналу (по десятибалльной шкале) 🤍 умеете ли оформлять посты 🤍 насколько вы конфликтный человек 🤍 юзер 🤩🤩🤩🤩🤩🤩 ❗ ИЩЕМ АДМИНОВ ПО... 🤍 по связкам 🤍 по нарезкам 🤍 по фоткам 🤍 по стикерам 🤍 по базам 🤍 по авам…
💘4
Прекрасный пиар от @Rita_tg 🤍
💘2
дрешки админов и влд 23.03 — рита (влд) 23.05 — анастезия 24.08 — ару 22.08 — сае 14.10 — мухамэд 10.12 — сароус 19.12 — летуэль 15.10 — айзо 24.06 — лими дни рождения админов часто напоминаются в канале, когда их нужно поздравлять, но иногда мы забываем поэтому поздравляете ваших любимых админов (и влд сами ❤️
💘4
родная ава вернулась 😎
💘4
я так подумала в инфо нужна моя анонка 🤩 анон - http://t.me/voprosy?start=53rep
💘2
💬 У тебя новое сообщение! Спасибо за лучший тгк! Всё шикарно, админы лучшие. Колоры, нарезки, базы — просто шик. Очень надеюсь, что скоро вы станете популярными, всегда использую только ваши нарезки, спасибо вам большое❤️ ↩️ Свайпни для ответа.
💘3
💬 У тебя новое сообщение! Рита замечательная и админы тоже!♡ ↩️ Свайпни для ответа.
💘8
💬 У тебя новое сообщение! Люблю ритусю. От Х. ↩️ Свайпни для ответа.
💘7
Showing the 12 most recent of 20 posts we hold for @jsjsjsjaqie. 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
оцените канал 🥹
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
на удачу пока рита щедрая 🫢
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 31 August 2025 to 24 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“инфо канал” (@jsjsjsjaqie), 29 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/jsjsjsjaqie.
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.