Channel
@evgeniiabrikos
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
22subscribers
-1 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002500527546 |
|---|---|
| Type | Channel |
| Username | @evgeniiabrikos |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/evgeniiabrikos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 15:27 | 22 | -1 |
| 13 Aug 2026, 06:33 | 23 | first reading |
20 posts held, back to 8 May 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 6 August 2026 |
|---|---|
| Posts held | 20 (8 May 2026 – 6 August 2026) |
| Views total | 299 |
| Reactions total | 63 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 06:33 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.
186 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 20.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5303099689212601953 | 38 | 20.4% | |
| custom 5303204293141096364 | 36 | 19.4% | |
| custom 5427290021491151861 | 32 | 17.2% | |
| custom 5301207601499882345 | 19 | 10.2% | |
| custom 5384413375860067680 | 16 | 8.60% | |
| custom 5219791965213714250 | 14 | 7.53% | |
| custom 5380082455392845502 | 10 | 5.38% | |
| ❤ | 6 | 3.23% | |
| custom 5235977124266929651 | 4 | 2.15% | |
| custom 5461010063135088912 | 4 | 2.15% | |
| custom 5467904421948058091 | 4 | 2.15% | |
| custom 5460918966878758055 | 3 | 1.61% |
Custom emoji. 11 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 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 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 186reactions 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 8 May 2026 to 6 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.
меняю название на купля-продажа тефтель ебанных из эйай
custom 52359771242669296514custom 53844133758600676802custom 54272900214911518611custom 54610100631350889121
Signed dance like u in pain
блаблабла пукпукпукпук
custom 54679044219480580914
Signed dance like u in pain
этот пост посвящен всем анимешникам !
custom 53030996892126019534custom 53012076014998823453custom 54610100631350889123custom 54272900214911518611
Signed dance like u in pain
у меня к ним какие то чувства интимные
custom 53030996892126019535custom 52197919652137142502custom 53012076014998823451custom 53844133758600676801
Signed сын крипера2008
ребята я увидел бензин ЗА 83 РУБЛЯ !!!!!!!!!!!! заправляйтесь 92 !!!!!!!!!!!!!!!!!!!
custom 53844133758600676803custom 53012076014998823452custom 53032042931410963642custom 53030996892126019531custom 54272900214911518611
Signed Svishzy!
придумайте в бс такую функцию что бы играть без интернета потому что в дороге его нету суперселл задумайтесь
custom 54272900214911518616custom 52197919652137142502custom 53844133758600676802
Signed Svishzy!
эй анимешники даттебае
❤6custom 53032042931410963644custom 53012076014998823451custom 54272900214911518611
Signed Svishzy!
ребят не пробуйте рецепты с тик тока я вас умоляю потому что это либо съедобно но полная хуебень либо это несъедобная невкусная горькая просроченная хуйня поносная которую максимум можно отдать собакам это пиздец просто нет если есть с закрытым носом то норм
custom 53032042931410963646custom 52197919652137142502
Signed zxc жиргуль 1
как это объединение хуесосов называется
custom 52197919652137142505custom 53030996892126019534custom 54609189668787580552
Signed жиргуль
держите кабачок
custom 54272900214911518613
Signed жирреш
пакет вб даже на рыбалке меня преследует но мне похуй это не отменяет тот факт что озон круче и лучше
custom 53012076014998823454custom 53030996892126019532custom 53800824553928455021custom 53844133758600676801custom 54272900214911518611custom 54609189668787580551
Signed zданя чzв zутенер
я был рад дождю с грозой ровно до того момента пока не отрубили свет
custom 53032042931410963646
Signed свишzи
Showing the 12 most recent of 20 posts we hold for @evgeniiabrikos. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
название вместо евгения абрикоса
Shares as published. 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 8 May 2026 to 6 August 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.
Citation-graph rank — 517,364 of 1,480,944entries 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“купля-продажа электрических латунных чайников из ссср” (@evgeniiabrikos), 22 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/evgeniiabrikos.
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.