Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝇃𝇃 ִֺ ִ۪ 𓐄ㅤneftushinfo

Channel

𝇃𝇃 ִֺ ִ۪ 𓐄ㅤneftushinfo

@neftyachan

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

171subscribers

-61 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003800758586
TypeChannel
Username@neftyachan
Created26 May 2026measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live9 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/neftyachan

Growth

171232201.514 August 2026 — 232 subscribers14 August 2026 — 232 subscribers23 August 2026 — 207 subscribers31 August 2026 — 201 subscribers9 September 2026 — 171 subscribers14 August 20269 September 2026
5 measurements spanning 26 days, net -61. 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 162–241 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 18:22171-30
31 Aug 2026, 10:03201-6
23 Aug 2026, 22:15207-25
14 Aug 2026, 23:16232no change
14 Aug 2026, 23:03232first reading

Engagement

7 posts held, back to 26 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 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 7 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

156 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 34.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52065275557204812815434.6%
custom 52832714444096526605233.3%
custom 52831913604494460285032.1%

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

Measured over the 7 most recent posts we hold, published 26 May 2026 to 14 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.

Recent posts

12 Aug 2026, 15:43 UTC136 views75 reactionsread 14 August 2026
Photo

✨🥹🥹🥹 𐍅 ꭷ⃪ֲ̼֬υ⃪⵿ۜ֩ꭈׁׅ ꭷ⃪ֲ̼֬ϷᎥᝲ⃪ܹ̈ꤙᎥᝲ⃪ܹ̈ꭷ⃪ֲ̼֬ꤙ 💭💭 💄💄💄💄 𝝰̷ֳׂꤐꭷ⃪ֲ̼֬υ⃪⵿ۜ֩𑀱 𐌌ꫀ݃۫ 🖤🖤

custom 520652755572048128126custom 528327144440965266025custom 528319136044944602824

12 Aug 2026, 15:42 UTC132 views81 reactionsread 14 August 2026
Photo

🥹🥹 𝐧⃪ֵֶׂۭ֘֯ۚꫀ݃۫⨍𝚝⃪⵿ۣؔ⃕ყ᪶ิ‌ัࣰ‌𝝰̷ֳׂ🥹ѕ𑂴ჩ⃪᮫ؔ⃗‌ꫀ݃۫/ჩ⃪᮫ؔ⃗‌ꫀ݃۫ꭈׁ 🖤🖤 🥹 bday - 08.11 🥹13 y.o 🥹 🩸🩸🩸 ✨🥹 ѕ𑂴𝛒ۖ࣫ꨵ5ѕ𑂴ꭷ2ѕ𑂴᥊ׁׅ8 INTP 🥹🥹 ժׁო | ժׁׅ𝐧ֵᎥᝲ | 𝝰̷ׂ𝐧ֵꭷ𝐧ֵ | 𝛒ꭷꫀოܹܳѕ 🪦

custom 520652755572048128128custom 528327144440965266027custom 528319136044944602826

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

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

“𝇃𝇃 ִֺ ִ۪ 𓐄ㅤneftushinfo” (@neftyachan), 171 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/neftyachan.

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.