Telegram RegisterThe public register of Telegram

Channel

ꫝᴇlsy|ᴀudiᴛiᴏn.

@helsy_oi

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

14subscribers

-2 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-1003974151237
TypeChannel
Username@helsy_oi
CreatedBetween 1 April 2026 and 29 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/helsy_oi

Growth

1416157 August 2026 — 16 subscribers11 August 2026 — 16 subscribers15 August 2026 — 14 subscribers7 August 202615 August 2026
3 measurements spanning 7 days, net -2. 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 14–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 02:1214-2
11 Aug 2026, 22:0116no change
7 Aug 2026, 19:1916first reading

Engagement

19 posts held, back to 29 May 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 16 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

19 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 15.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5357367730573949994315.8%
custom 5359362729998054836315.8%
custom 5359677886108301526315.8%
custom 5359812378714208106315.8%
custom 5429235740460487118315.8%
custom 5359341577284122760210.5%
custom 5359349419894403569210.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 19 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 19reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 29 May 2026 to 16 June 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

11 Jun 2026, 16:57 UTC26 viewsread 11 August 2026
Forwarded from @important_oiPhoto

𝐈𝐍𝐓𝐄𝐑𝐀𝐂𝐓𝐈𝐕𝐄❕ ୨ᰍ 🕳 𓂃 ≧﹏≦🩺 ⁺ 🩹 ( ?? ) Юнхэ и Саоки, вы большие гарпии. ☆🤍⌒(>。<) 🤍 . ZzZ 🤍 ꒰ !! ꒱ @helsy_oi

11 Jun 2026, 16:03 UTC22 views1 reactionsread 11 August 2026
Forwarded from @important_oiPhoto

𝐈𝐍𝐓𝐄𝐑𝐀𝐂𝐓𝐈𝐕𝐄❕ (!)☠ . 苦を🥛 --- 🤍 ໒ ໒ 📞какая вы бабочка. ꒰ 🥛 ⊹ 糀🤍 𓂅 ๓ 👁‍🗨ׄ ୨୧ .. 📓правила: 1. репост. 🧷2. ссылка на канал. 3. псевдоним. ᨦïᨩ〰 ˙ ࿐ 海 ☕️ 𝖹𝗓 𓈒 🖤 ⟡ статус: открыто.

custom 53573677305739499941

6 Jun 2026, 18:02 UTC22 views1 reactionsread 11 August 2026

Прошу актива от вас и комментариев на этом посте, от этого будет зависеть наше решение! По активу мы видим, интересно вам или нет🐈

custom 53593415772841227601

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

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.

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

“ꫝᴇlsy|ᴀudiᴛiᴏn.” (@helsy_oi), 14 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/helsy_oi.

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.