Telegram RegisterThe public register of Telegram

Channel

SOUNDSPLETNIK

@soundgossip

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

455subscribers

+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-1002139267439
TypeChannel
Username@soundgossip
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 15 August 2026
On Telegramt.me/soundgossip

Growth

4558 Aug 2026, 06:01 — 455 subscribers8 Aug 2026, 16:17 — 455 subscribers8 Aug 2026, 06:018 Aug 2026, 16:17
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 454–456 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 16:17455no change
8 Aug 2026, 06:01455first reading

Engagement

5 posts held, back to 22 July 2026the 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
78.9%
avg views ÷ 455 subscribers
Avg views / post
359
5 posts measured
Reaction rate
6.35%
reactions ÷ views · ER floor
Posts in window
5
of 5 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 July 2026
Posts held5 (22 July 202628 July 2026)
Views total1,794
Reactions total114
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:01 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

Video runtime
13s
Average length
13s

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.

Reaction mix

114 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 45.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54453255469447651035245.6%
custom 54450806264347102402622.8%
custom 54453155912105724322421.1%
custom 54452389088644699711210.5%

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 114reactions 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 22 July 2026 to 28 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

28 Jul 2026, 13:31 UTC267 views57 reactionsread 8 August 2026

Спасибо, что были с нами💚 Спасибо каждому, кто приехал на «Пустошь» Спасибо за то, что разбили такой красивый палаточный лагерь, танцевали до рассвета, встречали закаты на берегу Ильменя, поддерживали диджеев, общались и создавали ту самую атмосферу, ради которой мы делаем этот фестиваль. Спасибо за ваши эмоции, доверие и поддержку нашего дела. Именно вы превращаете «Пустошь» из просто музыкального события в настоя

custom 544532554694476510339custom 54450806264347102409custom 54453155912105724329

24 Jul 2026, 18:54 UTC351 views8 reactionsread 8 August 2026
Photo

🌅

custom 54453155912105724326custom 54450806264347102401custom 54452389088644699711

24 Jul 2026, 16:13 UTC343 views12 reactionsread 8 August 2026
Video

Неожиданный гость «Пустошь» 🎈🧺

custom 544508062643471024012

23 Jul 2026, 12:51 UTC347 views18 reactionsread 8 August 2026
Photo

Пока мы начинаем подготовку площадки и делаем все возможное, чтобы вы получили максимально крутые впечатления, ознакомьтесь с местом проведения и правилами «Пустоши» перед посещением: ⛺Место под палатку входит в стоимость билета, бери её с собой! 🎫 Стоимость билета финальная, можно забрать их тут👈🏼 или приобрести на месте. 📍Место проведения опенэйра «Коростинофф Берег» (Если не знаешь как добраться, можно поискат

custom 54452389088644699718custom 54453255469447651036custom 54450806264347102404

22 Jul 2026, 14:36 UTC486 views19 reactionsread 8 August 2026
Photo

А вот и расписание «Пустоши» и все активности, которые будут на фестивале уже в эту пятницу и субботу💗 Оставим тут основную инфу, чтобы ничего не потерялось: 🎫 Билеты и информация о локации туть 🎫 Билеты можно купить на месте но предупреждаем: на территории фестиваля интернет работает не всегда стабильно, поэтому, лучше взять их заранее и наличные для комфортной оплаты товаров и услуг🤩 Тайминги: 24.07 начинаем в

custom 54453155912105724329custom 54453255469447651037custom 54452389088644699713

Showing the 5 most recent of 5 posts we hold for @soundgossip. 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 — 262,381 of 1,480,688entries 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.

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.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“SOUNDSPLETNIK” (@soundgossip), 455 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/soundgossip.

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.