Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝓥𝔞𝔩𝔢𝔫𝔱𝔦𝔫𝔬'𝔰 𝔤𝔩𝔬𝔯𝔦𝔬𝔲𝔰 𝔒𝔯𝔤𝛾

Channel

𝓥𝔞𝔩𝔢𝔫𝔱𝔦𝔫𝔬'𝔰 𝔤𝔩𝔬𝔯𝔦𝔬𝔲𝔰 𝔒𝔯𝔤𝛾

@vals_orgy

On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

66subscribers

+18 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003843219466
TypeChannel
Username@vals_orgy
DescriptionCredits : @vals_orgy_cr ; Влд : @myasnik616.
CreatedBetween 1 February 2026 and 3 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live14 October 2026
Measurements held4
On Telegramt.me/vals_orgy

Previous handles

@vals_orgy was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@pony_net
held 11 August 2026 – 11 August 2026

Growth

48665711 August 2026 — 48 subscribers12 August 2026 — 48 subscribers14 October 2026 — 66 subscribers14 October 2026 — 66 subscribers11 August 202614 October 2026
4 measurements spanning 64 days, net +18. 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 45–69 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Oct 2026, 08:2266no change
14 Oct 2026, 07:4766+18
12 Aug 2026, 15:1448no change
11 Aug 2026, 17:3148first reading

Engagement

39 posts held, back to 3 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 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
87.2%
avg views ÷ 66 subscribers
Avg views / post
57.5
19 posts measured
Reaction rate
22.2%
reactions ÷ views · ER floor
Posts in window
19
of 39 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. It is computed over the 2 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 October 2026
Posts held39 (3 July 2026 – 14 October 2026)
Views total1,093
Reactions total32
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Oct 2026, 08:22 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
34
Links
25

Lifetime counters from Telegram’s own channel header, read 14 October 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.

Reaction mix

32 reactions across 2 posts, in 7 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54295856256762913851134.4%
custom 5219787713196080426515.6%
custom 5289677731729024803515.6%
custom 5197643664976814376412.5%
custom 543183093579439135339.38%
custom 539574051458466083026.25%
custom 539578488589179638826.25%

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 2 of the 39 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 39 most recent posts we hold, published 3 July 2026 to 14 October 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

14 Oct 2026, 05:17 UTC13 viewsread 14 October 2026
Photo

💘 :: ¡☺️ᥱ᧘ьʙᥱᴛ ᥰρᥙᥴ᧐ᥱдᥙняᥱᴛᥴя κ ᥴ᧘ᥲʙн᧐ᥔ ᧐ρᴦᥙᥙ ✍️! 💕ᥱ᧘ᥲᥱⲙ ᥱᥔ ᥴᥲⲙы᥊ ⲙ᧐κρы᥊ 🥹 ᧐ρᴦᥲᤋⲙ᧐ʙ. #приход ; #вельвет.

12 Oct 2026, 14:42 UTC27 viewsread 14 October 2026
Photo

💘 :: ¡☺️᧘ᥲᥴᴛ᧐ρ ᥰρᥙᥴ᧐ᥱдᥙняᥱᴛᥴя κ ᥴ᧘ᥲʙн᧐ᥔ ᧐ρᴦᥙᥙ ✍️! 💕ᥱ᧘ᥲᥱⲙ ᥱⲙу ᥴᥲⲙы᥊ ⲙ᧐κρы᥊ 🥹 ᧐ρᴦᥲᤋⲙ᧐ʙ. #приход ; #аластор.

12 Oct 2026, 14:42 UTC27 viewsread 14 October 2026
Photo

💔 :: ☺️юцᥙɸᥱρ κ᧐нчᥙ᧘ ☺️. ☺️ ᥰ᧐κᥙдᥲᥱᴛ ᥴ᧘ᥲʙную ᧐ρᴦᥙю. 💕 #уход ; #люцифер.

4 Oct 2026, 15:12 UTC75 viewsread 14 October 2026
Photo

💔 :: ☺️нджᥱ᧘᧐ κ᧐нчᥙ᧘ ☺️. ☺️ ᥰ᧐κᥙдᥲᥱᴛ ᥴ᧘ᥲʙную ᧐ρᴦᥙю. 💕 #уход ; #анджело.

4 Oct 2026, 15:12 UTC72 viewsread 14 October 2026
Photo

💔 :: ☺️ᥲρ᧘ᥙ κ᧐нчᥙ᧘ᥲ ☺️. ☺️ ᥰ᧐κᥙдᥲᥱᴛ ᥴ᧘ᥲʙную ᧐ρᴦᥙю. 💕 #уход ; #чарли.

4 Oct 2026, 12:24 UTC64 viewsread 14 October 2026
Photo

💔 :: ☺️юцᥙɸᥱρ κ᧐нчᥙ᧘ ☺️. ☺️ ᥰ᧐κᥙдᥲᥱᴛ ᥴ᧘ᥲʙную ᧐ρᴦᥙю. 💕 #уход ; #люцифер.

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

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 1 registered channel — 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.

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

“𝓥𝔞𝔩𝔢𝔫𝔱𝔦𝔫𝔬'𝔰 𝔤𝔩𝔬𝔯𝔦𝔬𝔲𝔰 𝔒𝔯𝔤𝛾” (@vals_orgy), 66 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/vals_orgy.

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.