Channel
@Atea_28
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
76subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002298471525 |
|---|---|
| Type | Channel |
| Username | @Atea_28 |
| Description | Чиловый челик из Питера, выкладываю что душе угодно. Рад вас видеть здесь |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Atea_28 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 21:00 | 76 | no change |
| 6 Aug 2026, 23:02 | 76 | first reading |
14 posts held, back to 24 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 | 14 (24 July 2026 – 9 August 2026) |
| Views total | 1,953 |
| Reactions total | 199 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 21:00 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 9 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.
Measured directly from 5 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.
199 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 24.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5298620403395074835 | 49 | 24.6% | |
| custom 5273917241862136310 | 42 | 21.1% | |
| custom 5425038191612674011 | 37 | 18.6% | |
| custom 5296636265943295190 | 30 | 15.1% | |
| custom 5276410444607660852 | 27 | 13.6% | |
| custom 5197376410636816971 | 14 | 7.04% |
Custom emoji. Every row above is a 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 areTelegram’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 13 of the 14 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 199reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 24 July 2026 to 9 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.
🔠🔠🔠🔠🔠 🥢🥢🥢🤩🤩🤩 🥢🥢🥢🥢🤍🤍🤍🤍😈😈 🔣Ближе брата и сестры никого нет и как бы вы не ругались, запомните, что роднее этих людей никогда не было и не будет🔣 🌟Robin 💓Sunday #cosplay #hsr #robin
custom 54250381916126740116custom 52739172418621363104custom 52764104446076608524custom 52966362659432951901
〰〰〰💙〰〰〰〰 С братом прибыли к самому началу, когда включали различные опенинги(там была геройка, это самое главное). Дальше были различные квизы, в одном из них я выиграл, во втором давали жетончики, где у меня, брата и учителя был семейный бюджет и мы на получили всего разного. После было уже не так весело, самое грустное что было мало песен, в основном кпоп и то немного. Когда всё закончилось мы пошли покушать, а да…
custom 52966362659432951905custom 52739172418621363104custom 52764104446076608523custom 54250381916126740111
Вот вам смешное фото на ночь, фотки с Юны будут завтра😴
custom 52739172418621363109custom 52986204033950748356custom 52764104446076608524custom 52966362659432951901
💫💫💫💫💫 Буду на Юнапати вместе со своим братиком, в образе Зарянки по этому арту. Буду рад со всеми повидаться🫡
custom 52966362659432951906custom 52986204033950748355custom 52764104446076608523custom 52739172418621363101custom 54250381916126740111
Я его не забросил, оно на этапе гофрации. Долгой и мучительной гофрации😐
custom 51973764106368169716custom 52986204033950748354custom 52764104446076608522custom 54250381916126740111
Будни после шашлыков проходят так Ацуши
custom 52739172418621363104custom 52986204033950748353custom 51973764106368169711custom 52764104446076608521
👿😈😈👿🆎😈 👿😈👿😈👿😈😈👿 Сегодня нашей бсд компанией ездили на шашлыки и купаться. У нас была фем бдсм тусовка, которая была запланирована месяц назад🌟 Все вместе встретились и поехали на точку развлекаться. Время пролетело незаметно, такого опыта у меня ещё не было, чтобы выбраться на тусовку в закосах, было незабываемо💗 ❤️🩹В главных ролях: Акутагава, Ацуши, Элис, Дазай, Чуя, Гоголь
custom 52986204033950748357custom 51973764106368169715custom 54250381916126740114custom 52739172418621363102
Сегодня на таком вайбе. Сходили компашкой на шашлыки. Ждите влог и тиктоки☺️ Мы этот поход ещё месяц назад запланировали
custom 54250381916126740118custom 52966362659432951907custom 52986204033950748355custom 52739172418621363101
Как понял собираем всех Питерских😶
custom 54250381916126740113custom 51973764106368169712custom 52966362659432951902custom 52739172418621363101custom 52764104446076608521
Posted without readable text
💙 🫶🫶🫶 🫶🫶🫶🫶🫶 💙 〰〰〰〰 〰〰〰〰 – захотелось сделать что-то классное, вот и подобрал небольшую видюшку)🌟 🌟 🫶 ps: Дазай Гоголь Акутагава Достоевский Ацуши 👻👻👻👻👻👻👻 #косплей@weixng #фест 👻👻👻
custom 54250381916126740118custom 52739172418621363103custom 52986204033950748353custom 52966362659432951901
🤩🤩 🤩🤩 🤩 🫶🫶🫶🫶🫶🫶🫶🫶🫶 🤩 🫶🫶🫶 🫶🫶🫶🫶🫶🫶🫶 🫶 Если ты снова полезешь вперёд один - я тебя убью. Лично 🫶 💗Ацуши 💗Акутагава 💗Фото #cosplay #bsd #shinsoykoky #Akutagawa
custom 52739172418621363107custom 52764104446076608525custom 52986204033950748354custom 54250381916126740112custom 52966362659432951901
Showing the 12 most recent of 14 posts we hold for @Atea_28. 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 — 70,911 of 1,169,250entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 7 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Бегуночек” (@Atea_28), 76 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Atea_28.
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.