💦 #edit #as #fav association for @tannwerx scp: fs scenes @vervedits

Channel
ineffae
@ineffma
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
129subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003616285069 |
|---|---|
| Type | Channel |
| Username | @ineffma |
| Description | fs editor ae 2020 margo dinabot, shaidobot |
| Created | Between 1 December 2025 and 28 March 2026— 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/ineffma |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 01:31 | 129 | no change |
| 8 Aug 2026, 20:00 | 129 | first reading |
Engagement
18 posts held, back to 28 March 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 · 30 days
- 52.7%
- avg views ÷ 129 subscribers
- Avg views / post
- 68.0
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 18 held
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 14 July 2026 |
|---|---|
| Posts held | 18 (28 March 2026 – 14 July 2026) |
| Views total | 68 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 01: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.
What this channel posts
- Photos
- 51
- Videos
- 51
- Links
- 24
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.
- Video runtime
- 2m 07s
- Average length
- 18s
Measured directly from 7 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.
Reaction mix
71 reactions across 4 posts, in 7 distinct kinds. The most used accounts for 47.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5395482030567893318 | 34 | 47.9% | |
| custom 5235589164166032324 | 12 | 16.9% | |
| custom 5283105267829997242 | 10 | 14.1% | |
| custom 5386709796088985875 | 8 | 11.3% | |
| custom 5220153683064404942 | 3 | 4.23% | |
| custom 5406639797257122995 | 3 | 4.23% | |
| custom 5386854858609409107 | 1 | 1.41% |
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 4 of the 18 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 71reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 28 March 2026 to 14 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.
Recent posts
💜 #edit #kn #fav association for @mirevaa @vervedits
💦 #edit #as #fav scp @vervedits
🤍 #edit #ak scp, ib @vervedits
с новыми силами и новым ноутом
заходите, эта я
🖤🖤 #edit #kv scp: fs_scenes; cc and sound @vervedits
💙 i’m in love with a fairytale… #edit id: @yuzu_9407 sdt: всем подписчикам этого канала
всем приветик у меня новая эра, кому интересно следить дальше, переходите @ineffa_new ❤️
Video message, posted without a caption
говорят, когда то тут были эдиты…
😁😆😁 бываю редко, но метко (нет) #edit | scp: fs_scenes sdt: @sskatrexp
custom 52355891641660323249custom 53954820305678933187custom 52831052678299972423custom 54066397972571229953custom 53868548586094091071
Showing the 12 most recent of 18 posts we hold for @ineffma. 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
Citation-graph rank — 438,150 of 1,160,990entries 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.
Forward network
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.
Mentions
Named by 2 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.
@vervedits · 1515 postslolatrusova fs scp | ae
@lolatrusov · 2,9832 postsвсе таки ника♥️
@sskatrexp · 4612 postsi
@ineffa_new · 421 postпотерянная.
@mirevaa · 1941 postsamx𐌕ru
@samxtru · 1971 postt’аннверкс || t’annwerx
@tannwerx · 1361 posttwiliice💋
@twiliice · 6411 post𝙫𝙖𝙡𝙞𝙚𝙨𝙝𝙠𝙖
@valieshka · 6401 post
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.
Cite this entry
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.
“ineffae” (@ineffma), 129 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ineffma.
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.