Channel
@infoneff
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
38subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004453019571 |
|---|---|
| Type | Channel |
| Username | @infoneff |
| Description | почему макс нефор красит губы он што педик |
| Created | 30 June 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/infoneff |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:30 | 38 | no change |
| 12 Aug 2026, 06:16 | 38 | first reading |
10 posts held, back to 30 June 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 11 August 2026 |
|---|---|
| Posts held | 10 (30 June 2026 – 11 August 2026) |
| Views total | 26 |
| Reactions total | 12 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 06:30 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 12 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.
465 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 37.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422610087686470814 | 173 | 37.2% | |
| custom 5425102916769843688 | 71 | 15.3% | |
| custom 5447450709647722072 | 64 | 13.8% | |
| custom 5415963084630031263 | 53 | 11.4% | |
| custom 5397886769872016181 | 43 | 9.25% | |
| custom 5397971904713760610 | 24 | 5.16% | |
| custom 5427227950623783022 | 21 | 4.52% | |
| custom 5398009511447402048 | 16 | 3.44% |
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 9 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 465reactions 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 30 June 2026 to 11 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.
💬 У тебя новое анонимное сообщение! 💩💩💩💩обмажься 💩💩💩 💩💩💩💩💩💩 💩💩💩 @anonaskbot
custom 54474507096477220725custom 53978867698720161814custom 53980095114474020481custom 54251029167698436881custom 54272279506237830221
ㅤㅤㅤ➿➿➿ ➿ ࣲ 神᎓ ᱺ who are u to me ？🌟 ㅤ ㅤ ㅤ 𝃡 ׅ𝇂𝇄☀️ ࣪тапайте реакции🤩👍 ㅤㅤ🕯 𝄒𝄒 ֪𝟣. проходили мимо 𑈺 🤩 ㅤㅤㅤㅤ ֪𝟤. друг 𝇂𝇄 подруга 𑈺 🤩 ㅤㅤㅤㅤㅤㅤ 🤩🤩 ㅤㅤㅤㅤ ֪𝟥. подписчик 𑈺 🫦 ㅤ ㅤ ㅤㅤㅤ ㅤㅤ🤩🤩 ㅤㅤㅤㅤ ֪𝟦. бывший друг 𝇂𝇄 подруга 𑈺 🥀 ㅤㅤㅤㅤ ֪𝟧. влюблены в меня 𑈺 😄 ㅤㅤㅤㅤ ֪𝟨. хотите познакомиться 𑈺 🌟 ㅤㅤㅤㅤ ֪𝟩. ненавидите меня! 𑈺 🤬 ㅤㅤㅤㅤ ֪𝟪. видели в пт 𑈺 🤩
custom 5422610087686470814113custom 542510291676984368845custom 541596308463003126323custom 544745070964772207220custom 539788676987201618113custom 542722795062378302210custom 53979719047137606109custom 53980095114474020483
ㅤ ㅤ ؛ ׅ𝇂𝇄🤩🤩ܸ ͏ֺ me and my 𝘀𝘄𝗲𝗲𝘁 𝗯𝗼𝘆 💤
custom 542261008768647081414custom 54474507096477220729custom 54159630846300312637custom 54251029167698436885custom 53978867698720161812custom 53979719047137606102custom 53980095114474020482
🌟
custom 53978867698720161816custom 54226100876864708143custom 54251029167698436883custom 53979719047137606101custom 53980095114474020481
ㅤㅤㅤ ➿➿➿ ➿ 𝂅ׅׄ ̣̣妄᎓ ᱺ love list 🤩 ㅤㅤㅤㅤׄ݁🤩ܸ ”⢾ Here's my beloved ones ִ ִ ִ 🤩🤩 ㅤㅤ𓏼࣪. ׄ ֵ 𝗺𝘆 𝗳𝗿𝗶𝗲𝗻𝗱𝘀! ❤️ ㅤㅤ﹫݃.𝘁error 🪽﹫݃.𝗻elya 🪽﹫݃.𝗿ose ㅤㅤ﹫݃.𝘆uchi 🪽﹫݃.𝗸aizen 🪽﹫݃.𝗺eowrice ㅤㅤ﹫݃.𝗽siopa 🪽﹫݃.𝘇ahar 🪽﹫݃.𝗱ashicats ㅤㅤ﹫݃.𝗮lbertyerg 🪽﹫݃.𝗱ima 🪽﹫݃.𝗿onin ecüs ㅤㅤ ﹫݃.𝗱ashaKFS 🪽﹫݃.𝗸agae GOD ㅤㅤ ﹫݃.𝗱ed eblan 🪽﹫݃.𝗿ina 🪽﹫݃.𝗮nya pro ㅤㅤ ﹫݃.𝗺iko chan 🪽﹫݃.𝗸irill sun 🪽﹫݃.𝗲lazzxlis ㅤㅤ ﹫݃.блоха🪽 ㅤㅤ🎀🤩🤩🤩ࣰ 𝇄ܸ and others, ㅤㅤ ㅤ 🤩🤩🤩 btw idm makin' ne
custom 544745070964772207213custom 54159630846300312637custom 53978867698720161815custom 54251029167698436883custom 53979719047137606102custom 53980095114474020482custom 54226100876864708142custom 54272279506237830222
ㅤㅤㅤㅤ ׁ 𝃣🤩 my shitpost heattsi.t.me ㅤ ㅤ ㅤ
custom 54226100876864708149custom 54251029167698436884custom 54272279506237830224custom 54474507096477220723custom 53978867698720161812custom 53979719047137606102
ㅤ ㅤㅤㅤ ݃ ۣꠂ🤩 ࣪ Opinion post 🤬 ㅤㅤㅤ ㅤㅤㅤㅤ݃ 𝇂𝇄 ⁝⁝ your opinion of me 🐙 ㅤㅤ ㅤ ㅤ ➿➿➿ ➿ ㅤ݃ ױ🕸 здесь вы можете написать ЛЮБОЕ своё мнение обо мне! как о скиноделе, человеке, друге и т.д 👍 ㅤㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤㅤ🚫 ЩП УДАЛЯЮТСЯ ㅤ ㅤ ㅤㅤ 𝅥𝄀 ˚̣̣̣ 🥀 ۪ прошлые отзывы можете ㅤ ㅤ ㅤ ㅤ ㅤ ㅤㅤ ㅤ ㅤ ㅤㅤпочитать вот здесь...
custom 541596308463003126312custom 54226100876864708147custom 54251029167698436886custom 54474507096477220724custom 53978867698720161812custom 53979719047137606102custom 54272279506237830221
🌟
custom 54474507096477220728custom 54226100876864708147custom 54251029167698436884custom 54272279506237830223custom 53979719047137606102custom 53980095114474020482custom 53978867698720161811
ㅤㅤ ㅤ ㅤ➿➿➿ ➿ 늘᎓ ᱺ info about me ..🤩ㅤ ㅤㅤ 😻🖤 my n – @wqsteed🦷🪽ㅤ🌟🌟 🤩 ㅤ ㅤ ㅤ ㅤ name 𑈺 ﹫Neff٫ макс нефор 🫦 ㅤㅤㅤㅤㅤ+6ㅤ㈷𝇂ؗ pronouns 𑈺 any٫ 🤩🤩🤩 🐈⬛ ㅤ ㅤ ㅤ 🀍 ࣰ ⭐ ▎ b – day 𑈺 𝟢𝟩.𝟢𝟣.𝟤𝟢𝟢𝟫 🍼 🗒ㅤㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ📰 MBTI – ISFP ㅤㅤ𝗺𝘆 𝘀𝘄𝗲𝗲𝘁 𝗯𝗳𝗳 🤩 ㅤ ㅤ ㅤ✍️𔖳 стесняешься написать? ㅤ ㅤㅤ ㅤ ㅤ держи анон٫ мб в себя поверишь👍
custom 542261008768647081418custom 53978867698720161818custom 53980095114474020485custom 53979719047137606104custom 54159630846300312634custom 54474507096477220722
Channel created
Showing the 10 most recent of 10 posts we hold for @infoneff. 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 — 808,575 of 1,481,217entries 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 3 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.
@infoneff named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“ㅤㅤ ㅤ info 𝘯𝘦𝘧𝘧” (@infoneff), 38 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/infoneff.
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.