Channel
@sonicgramcom
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
4,029subscribers
-33 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001415223191 |
|---|---|
| Type | Channel |
| Username | @sonicgramcom |
| Created | 17 June 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/sonicgramcom |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 19:43 | 4,029 | -3 |
| 25 Aug 2026, 05:25 | 4,032 | -4 |
| 22 Aug 2026, 02:13 | 4,036 | -6 |
| 18 Aug 2026, 09:56 | 4,042 | -1 |
| 15 Aug 2026, 16:26 | 4,043 | -6 |
| 11 Aug 2026, 17:37 | 4,049 | -5 |
| 8 Aug 2026, 18:04 | 4,054 | -8 |
| 7 Aug 2026, 20:00 | 4,062 | no change |
| 7 Aug 2026, 19:39 | 4,062 | first reading |
5 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 2 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
404 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 48.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5312338400089500532 | 195 | 48.3% | |
| custom 5253769382772890834 | 130 | 32.2% | |
| custom 5220219026696845500 | 55 | 13.6% | |
| custom 5465454877545090785 | 24 | 5.94% |
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 5 of the 5 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 404reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 24 July 2026 to 29 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.
у моих новых друзей вышли новинки, поэтому они решили обновить мне вообще все🤩 обозрим. но не все.
custom 531233840008950053249custom 525376938277289083419custom 546545487754509078518
Signed sophie
в целом все то же, только размер побольше, от того и граммовки х3
custom 531233840008950053232custom 525376938277289083414custom 52202190266968455005
Signed sophie
сопротивляться можно было долго, но я ряльна люблю это занятие, поэтому у нас теперь новая основная рубрика в тиктоке. пока повторю легенд этого чатика, потом перейдем к чему-то более интересному🤩
custom 531233840008950053220custom 52537693827728908348custom 54654548775450907855
Signed sophie
история как мы с родничком первый филиал рэйва в сибири к открытию готовили, чтобы вы в доту и симс рубились congratulations mr president 📍нижегородская 6а
custom 531233840008950053255custom 522021902669684550018custom 525376938277289083418
Signed sophie
pretty girls 2 addicted 2 the pain 👼
custom 525376938277289083471custom 531233840008950053239custom 522021902669684550032custom 54654548775450907851
Signed sophie
Showing the 5 most recent of 5 posts we hold for @sonicgramcom. 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.
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.
“сонечка святая” (@sonicgramcom), 4,029 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/sonicgramcom.
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.