🦾MADE BY KOGTESERJ🦾
custom 51881876459346013008🐳6custom 54067098352888336074
Signed $анбубля

Channel
@SuCkMyBoNeS
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
360subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001860539001 |
|---|---|
| Type | Channel |
| Username | @SuCkMyBoNeS |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/SuCkMyBoNeS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 08:14 | 360 | +2 |
| 21 Aug 2026, 07:04 | 358 | +3 |
| 14 Aug 2026, 14:37 | 355 | +2 |
| 8 Aug 2026, 06:46 | 353 | no change |
| 7 Aug 2026, 15:31 | 353 | first reading |
17 posts held, back to 28 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 5 August 2026 |
|---|---|
| Posts held | 17 (28 July 2026 – 5 August 2026) |
| Views total | 1,947 |
| Reactions total | 148 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:46 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 1 video 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.
261 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 32.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🐳 | 85 | 32.6% | |
| custom 5406709835288833607 | 35 | 13.4% | |
| 💔 | 34 | 13.0% | |
| custom 5188187645934601300 | 32 | 12.3% | |
| custom 5420491749686537751 | 25 | 9.58% | |
| custom 5406886895315610381 | 21 | 8.05% | |
| custom 5294457016717165159 | 18 | 6.90% | |
| custom 5406893217507473701 | 6 | 2.30% | |
| custom 5472014838794307565 | 5 | 1.92% |
Custom emoji. 7 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 17 of the 17 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 261reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 28 July 2026 to 5 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.
🦾MADE BY KOGTESERJ🦾
custom 51881876459346013008🐳6custom 54067098352888336074
Signed $анбубля
ладно да
🐳10custom 54068868953156103812custom 54204917496865377512
Signed $анбубля
Video message, posted without a caption
custom 540688689531561038113custom 51881876459346013003🐳2
Signed $анбубля
почему то щас убеждена что я ахуительна господи прости ладно нет
🐳8custom 54204917496865377515custom 54068932175074737012
Signed $анбубля
это так странно мы люди самые настоящие паразиты на планете уничтожаем природу уничтожаем друг друга устраиваем геноциды войны ненавидим ближних зато стабильно каждое лето пьем айс латте с сырной пенкой с кавайным сиропом закусывая печенькой и находим что то невероятно глубокое в так называемом явлении «любовь» а потом думаем куда сбросить ядерное оружие ммм
custom 540670983528883360718🐳12💔4
Signed $анбубля
Video message, posted without a caption
🐳3💔2custom 52944570167171651592
Signed $анбубля
тогда вот еще
🐳8custom 51881876459346013001custom 52944570167171651591custom 54067098352888336071custom 54204917496865377511
Signed $анбубля
я случайно
🐳2💔1custom 52944570167171651591
Signed $анбубля
э
🐳2custom 54068868953156103811custom 54720148387943075651
Signed $анбубля
Photo, posted without a caption
🐳5custom 54068932175074737012💔1custom 51881876459346013001custom 54068868953156103811
Signed $анбубля
Photo, posted without a caption
custom 54204917496865377516🐳3custom 54067098352888336073
Signed $анбубля
обалдеть это как
💔8custom 54720148387943075654
Signed $анбубля
Showing the 12 most recent of 17 posts we hold for @SuCkMyBoNeS. 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 — 948,241 of 1,628,524entries 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“солнечное сплетение” (@SuCkMyBoNeS), 360 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/SuCkMyBoNeS.
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.