Telegram RegisterThe public register of Telegram
Telegram profile photo for VAVILON | SABZY

Channel

VAVILON | SABZY

@vavilon_sabzy

On this record: Growth · Engagement · Posts · Citations · Cite this entry

14subscribers

+0 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002842354288
TypeChannel
Username@vavilon_sabzy
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/vavilon_sabzy

Growth

1413 Aug 2026, 03:02 — 14 subscribers13 Aug 2026, 07:53 — 14 subscribers13 Aug 2026, 03:0213 Aug 2026, 07:53
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 13–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:5314no change
13 Aug 2026, 03:0214first reading

Engagement

20 posts held, back to 27 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
55.7%
avg views ÷ 14 subscribers
Avg views / post
7.8
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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 12 August 2026
Posts held20 (27 July 202612 August 2026)
Views total156
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 03:02 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.

Recent posts

12 Aug 2026, 07:13 UTC5 viewsread 13 August 2026

канал: @ASTREVAL_FM след: @skel3tonz пдп 10:10 — папка вз/рп/актив/актив+рп. допы: 2:2 @NNDUII 3:3 @zxcursebq 4:4 @Hikewen 5:5 @ABVMXN 6:6 @RXGHP 7:7 @OTHDN1 8:8 @rtv3n 9:9 @NUARE7 10:10 @xhiroks

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

10 Aug 2026, 10:52 UTC7 viewsread 13 August 2026

канал: @VALENHUBFM след: @G0LDDDY папка: рп/вз пдп: 3:3 допы: 1:1 @G0LDDDY 2:2 @G0LLTH 3:3 @V1LLANT

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

7 Aug 2026, 13:26 UTC9 viewsread 13 August 2026

канал - @BXSTONX папка рп/вз/актив+рп пдп 8:8 след - @V1LLANT допы: 1:1 @V1LLANT (переходник) 2:2 @G0LLTH 3:3 @G0LDDDY 4:4 @meowwterr (переходник) 5:5 @sweet_raf 6:6 @Burnout812 переходник 7:7 @Lunyx143 8:8 @MILLERNEWT 9:9 @OS21TIN 10:10 @wdlucsz

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

7 Aug 2026, 13:25 UTC6 viewsread 13 August 2026

Канал - @tellmeproject След - @wersachh Папка рп 2:2 @liptirs 3:3 @PANAC3333YA (переходник) 4:4 @WWWWWWWWWWWWWWWWWWWWWVV (переходник) 5:5 @VTP1NG 6:6 @BLY4DOTA11 7:7 @lariohaskr (переходник) 8:8 @H4RK00M (переходник) 9:9 @Affectionatehug 10:10 @T8130N 11:11 @ACT1MEL1 12:12 @DeadPooliha (переходник) 13:13 @exmmrs 14:14 @GTMMKANG (переходник)

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

7 Aug 2026, 13:23 UTC5 viewsread 13 August 2026

канал: @SEXSLVR пдп/папка: 7×7 / рп следящий: @aishitk допы: 2:2 @frrrozvwi 3:3 @LORDYUN 4:4 @RIXXMING 5:5 @T3MP7ER 6:6 @E3CUT1ONER 7:7 @ALOAN_69

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

6 Aug 2026, 19:18 UTC6 viewsread 13 August 2026

канал @xxxh4b след @DR1P4RXHUB папка рп Допы: 2:2 @e_wone 3:3 @kkalin 4:4 @Idkkfkk 5:5 @NRS1TC4 6:6 @svfalu 7:7 @xxxh4b1

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

6 Aug 2026, 14:11 UTC7 viewsread 13 August 2026

Канал: @JUDASCHANNEL01 След: @gegehell Папка: рп Пдп: Допы: 2:2 @HiroBL69 3:3 @JK97LE 4:4 @jor_ji 5:5 @nillhse 6:6 @fahenff 7:7 @temoKT

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

6 Aug 2026, 14:09 UTC8 viewsread 13 August 2026

канал: @analystky следящий: @miluiss папка: рп допы: 1:1 – @miluiss (следящий) 2:2 – @Sv0l0th 3:3 – @miluiin 4:4 – @DVmff 5:5 – @WhisperOO 6:6 – @aesoo_gh 7:7 – @Aderllllli

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

6 Aug 2026, 14:07 UTC7 viewsread 13 August 2026

Канал @RCF4M След: @AMER1II Пдп: 7:7 Папка: рп Допы: 1:1 @AMER1II (след) 2:2 @AMER1IO 3:3 @g1tadd 4:4 @affect6 5:5 @swweettnness 6:6 @marc_sman 7:7 @t1vv4ka

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

6 Aug 2026, 14:06 UTC5 viewsread 13 August 2026

тгк: @NRCRSS след: @KSM_Z4 допы: 1. @T1RV1NO 2. @AL1TXJK 3. @Y0URK4RM4 4. @RINJUY7 5. @K0R_sT0n 6. @W_LFRD 7:7/рп

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

6 Aug 2026, 13:43 UTC4 viewsread 13 August 2026

Канал: @HB_KROWFORD След: @SEX_MORT Пдп: 26:26 Папка: вз/рп Допы: 1:1 @SEX_MORT 2:2 @lunaiiiiii 3:3 @w1nt3rbluu 4:4 @xxsm6 5:5 @FUCK_MORT 6:6 @rremann 7:7 @sspplllll 8:8 @LetAskk 9:9 @stnkq 10:10 @Baker_Ester 11:11 @angskai 12:12 @nnxzss 13:13 @amirrkax 14:14 @mosytik 15:15 @man1eee 16:16 @SV1XERR 17:17 @VIOLENSEC 18:18 @corrugated_paper427 19:19 @medd4y (переходник) ВЗ доп 20:20 @perehraf (переходник) 21:21 @W_snk (

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

6 Aug 2026, 13:40 UTC4 viewsread 13 August 2026

канал: @analystky следящий: @miluiss папка: рп/актив/вз/актив + рп пдп: 19:19 допы: 1:1 – @miluiss (следящий) 2:2 – @Sv0l0th 3:3 – @miluiin 4:4 – @LVBEFF 5:5 – @WhisperOO 6:6 – @NOPM228 7:7 – @Aderllllli 8:8 – @Christop1er_ban 9:9 – @Lyyyciiiiifeeerr 10:10 – @min_son_Yoon 11:11 – @nn_abbiee 12:12 – @DARLINGAXXX 13:13 – @DieHaseNastya201 14:14 – @s1mski (перех) 15:15 – @oduvanpastuha 16:16 – @babaika_665 17:17 — @jal

Signed 𝐒͢𝐓̷𝐘𝐋̲𝐄̷̚

Showing the 12 most recent of 20 posts we hold for @vavilon_sabzy. 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 — 1,451,056 of 1,563,849entries 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.

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

“VAVILON | SABZY” (@vavilon_sabzy), 14 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/vavilon_sabzy.

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.