:: обиды запиши в тетрадь) #pvs
custom 60172755742700393169custom 60191510705240864584custom 53323989897382720643
Signed viᴋsᴀ.ssd

Channel
@sofariksbanda
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
989subscribers
-90 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002743249694 |
|---|---|
| Type | Channel |
| Username | @sofariksbanda |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/sofariksbanda |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 04:20 | 989 | -10 |
| 27 Aug 2026, 18:46 | 999 | -13 |
| 24 Aug 2026, 10:06 | 1,012 | -26 |
| 20 Aug 2026, 14:58 | 1,038 | -5 |
| 17 Aug 2026, 11:32 | 1,043 | -16 |
| 14 Aug 2026, 07:06 | 1,059 | -8 |
| 10 Aug 2026, 19:13 | 1,067 | -12 |
| 8 Aug 2026, 00:06 | 1,079 | no change |
| 7 Aug 2026, 18:55 | 1,079 | first reading |
11 posts held, back to 5 August 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 page of 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 11 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 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.
283 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 38.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6019151070524086458 | 109 | 38.5% | |
| custom 6017275574270039316 | 80 | 28.3% | |
| custom 5224707404960127184 | 45 | 15.9% | |
| custom 5332398989738272064 | 31 | 11.0% | |
| custom 5328308308266736927 | 18 | 6.36% |
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 are Telegram’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 11 of the 11 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 283 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 5 August 2026 to 7 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.
:: обиды запиши в тетрадь) #pvs
custom 60172755742700393169custom 60191510705240864584custom 53323989897382720643
Signed viᴋsᴀ.ssd
:: грустенько что влад уже уезжает,будем скучать🫂🤍 #tt
custom 601727557427003931612custom 53323989897382720642custom 60191510705240864581
Signed янчик.🖤
итоги набора! к нам попали: sontoxi @qwxxip @nikamemmm @veronnxeeex @ylua_safarova флора кто не попал , не расстраивайтесь! это не последний наш набор!
custom 601727557427003931612custom 53323989897382720643custom 60191510705240864582
Signed viᴋsᴀ.ssd
::самая лучшая 🥹 #kk #am #bvs
custom 601915107052408645822custom 53323989897382720644custom 60172755742700393164
Signed элсичка сафарова <3
А вот и реакция Сони,честно скажу очень переживал 🥹
custom 522470740496012718424custom 60172755742700393161custom 60191510705240864581
Signed янчик.🖤
:: как же сони идут цветы,она сияет с ними💞👫 #tt
custom 601915107052408645818custom 60172755742700393163custom 53323989897382720642
Signed янчик.🖤
:: как же мы рады видеть их вместе снова🐱🧛 #tt нарезка: «ксюши кузнецовой•»
custom 601915107052408645820custom 60172755742700393163custom 52247074049601271842custom 53323989897382720641
Signed янчик.🖤
Video message, posted without a caption
custom 532830830826673692718custom 52247074049601271844custom 60172755742700393164
Signed янчик.🖤
::соня с черными нарощенными волосами😍😍 #am
custom 601727557427003931624custom 53323989897382720649custom 60191510705240864585custom 52247074049601271843
Signed viᴋsᴀ.ssd
:: скучают друг по другу🫶🤍 #tt
custom 601915107052408645819custom 52247074049601271847custom 53323989897382720645custom 60172755742700393164
Signed янчик.🖤
:: они как инь и янь☯🤍 #tt
custom 601915107052408645817custom 52247074049601271845custom 60172755742700393164custom 53323989897382720642
Signed янчик.🖤
Showing the 11 most recent of 11 posts we hold for @sofariksbanda. 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.
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.
@sofariksbanda 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“шимерс соняши 🤎” (@sofariksbanda), 989 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/sofariksbanda.
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.