Telegram RegisterThe public register of Telegram

Channel

𝗦𝗡𝗢𝗪𝗬 🕸 𝗢𝗡𝗧𝗢𝗣

@SNOWY_ONTOP

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

90subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003856402057
TypeChannel
Username@SNOWY_ONTOP
Description@PV_SNOWY
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/SNOWY_ONTOP

Growth

907 August 2026 — 90 subscribers9 August 2026 — 90 subscribers7 August 20269 August 2026
2 measurements spanning 2 days. 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 89–91 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 14:3290no change
7 Aug 2026, 18:0390first reading

Engagement

20 posts held, back to 8 August 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
2.44%
avg views ÷ 90 subscribers
Avg views / post
2.2
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 9 August 2026
Posts held20 (8 August 20269 August 2026)
Views total44
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 14:32 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

Photos
309
Videos
185
Links
155

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
3m 24s
Average length
51s

Measured directly from 4 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.

Recent posts

9 Aug 2026, 12:59 UTC2 viewsread 9 August 2026
Forwarded from @HajArcTicFile

File, posted without a caption

Signed -Parsa 16:29

9 Aug 2026, 11:22 UTC3 viewsread 9 August 2026
Forwarded from @digianti0botPhoto

• نام گروه : NIGHTSHADOW • تعداد عضو : 297 • توضیحات : • لینک گروه : ━┅┅ ✦ ┅┅━ 🔗 https://t.me/+5eMcd6-AZ603NjA0

Signed 𝐹𝒶𝒩✞

9 Aug 2026, 09:49 UTC3 viewsread 9 August 2026
Forwarded from @digi1botPhoto

• نام گروه : 𝐎𝐧𝐥𝐲 𝐋𝐨𝐯𝐞 ✨ • تعداد عضو : 205 • توضیحات : 𝗢𝘄𝗻𝗲𝗿 𝗶𝗗 : @ParsaArcTic • لینک گروه : ━┅┅ ✦ ┅┅━ 🔗 https://t.me/+HN1cnMOJyvI1ZmRk

Signed -Parsa 13:19

9 Aug 2026, 07:18 UTC1 viewsread 9 August 2026
Forwarded from @silent_OnTOP

https://t.me/HajArcTic چنل خودمه جوین بدین

Signed -Parsa 10:48

8 Aug 2026, 23:28 UTC2 viewsread 9 August 2026
Forwarded from @LONELYONTT1Video

Video, posted without a caption

Signed 𝗬𝗮𝘀𝗵𝗮𝗿 ✞

8 Aug 2026, 20:37 UTC1 viewsread 9 August 2026
Forwarded from @wilenOnTop1Video

Loz: Samorai ( kos nne)

Signed Meti wilen𓂀

8 Aug 2026, 19:55 UTC2 viewsread 9 August 2026
Forwarded from @REALAMIRANDPAKOONTOP

اخ پسر دیدی بیغریتی

Signed Unloved

8 Aug 2026, 19:55 UTC2 viewsread 9 August 2026
Forwarded from @REALAMIRANDPAKOONTOP

کوه غیرت

Signed Unloved

8 Aug 2026, 17:43 UTC5 viewsread 9 August 2026
Forwarded from @LONELYONTT1Photo

6908490045561700353😂 اد بدید 😊

Signed 𝗬𝗮𝘀𝗵𝗮𝗿 ✞

8 Aug 2026, 17:37 UTC2 viewsread 9 August 2026
Forwarded from @HajArcTic

اسکریم واس امشب @ParsaArcTic

Signed -Parsa 21:07

8 Aug 2026, 17:20 UTC3 viewsread 9 August 2026
Forwarded from @brok_559

2283739357 10 منتظر میمانم امدین امدین نیامدی کصه ننت بقیه هم بیان ننه اینارو بگاییم

Signed 𝘽𝙍𝙊𝙆

Showing the 12 most recent of 20 posts we hold for @SNOWY_ONTOP. 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.

Forward network

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

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.

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

“𝗦𝗡𝗢𝗪𝗬 🕸 𝗢𝗡𝗧𝗢𝗣” (@SNOWY_ONTOP), 90 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/SNOWY_ONTOP.

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.