Telegram RegisterThe public register of Telegram
Telegram profile photo for Сказать что хотел?

Channel

Сказать что хотел?

@NyChtoZaEblan

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

110subscribers

-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-1002520387403
TypeChannel
Username@NyChtoZaEblan
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 18 September 2026
On Telegramt.me/NyChtoZaEblan

Growth

1101121117 August 2026 — 112 subscribers9 August 2026 — 112 subscribers31 August 2026 — 111 subscribers10 September 2026 — 110 subscribers7 August 202610 September 2026
4 measurements spanning 34 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 110–112 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 12:00110-1
31 Aug 2026, 07:04111-1
9 Aug 2026, 06:32112no change
7 Aug 2026, 16:46112first reading

Engagement

8 posts held, back to 3 December 2025the 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 8 posts for this entry, the most recent from 19 January 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

67 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 60326017183892144681420.9%
custom 54651402840755491111319.4%
custom 54656050210118113541319.4%
custom 60330719314087806881217.9%
custom 5787432680052231113811.9%
custom 546341955696801454357.46%
custom 546314372128336171722.99%

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

Measured over the 8 most recent posts we hold, published 3 December 2025 to 19 January 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

19 Jan 2026, 13:00 UTC259 views14 reactionsread 9 August 2026
Photo

Лень писать умные вещи, покажу собаку, уже 4 месяца малютке Весит 15кг к слову…

custom 54656050210118113545custom 54634195569680145434custom 54651402840755491114custom 60326017183892144681

22 Dec 2025, 10:02 UTC≈18,300 views9 reactionsread 9 August 2026
Photo

По ХО-ХО-ХО Хлам Если бы я производил салюты, то назвал бы свою батарею именно так, название свободно, забирайте.. К сожалению сам я сейчас из пиротехники произвожу только шептунов у себя дома(( Как по мне - охуенный нейминг, а на упаковке был бы довольный дед и грустный клоун. Так сказать, тонко, не многие поймут, с юморком, по-нашему! Тем более на фоне того, что я увидел на рынке пиротехники... Вы обращали вним

custom 60330719314087806889

16 Dec 2025, 19:14 UTC402 views13 reactionsread 9 August 2026
Photo

Когда ты - алкаш, то люди дарят тебе то, что нужно

custom 54651402840755491119custom 57874326800522311132custom 54631437212833617171custom 54656050210118113541

13 Dec 2025, 14:46 UTC323 views2 reactionsread 9 August 2026

пидорасы источник не указали)

custom 60326017183892144682

13 Dec 2025, 14:46 UTC389 views6 reactionsread 9 August 2026
Forwarded from @shot_shotPhoto

Аферисты массово взламывают и блокируют айфоны школьников под видом установки программы, которая скрывает онлайн от родителей в Telegram По информации SHOT, мошенники рассылают детям сообщения с предложением установить популярное среди сверстников приложение AuyGram. Это программа, которая позволяет скрывать онлайн-статус (режим «невидимки»), читать удалённые сообщения и пользоваться собственными премиум-функциями в

custom 60326017183892144685custom 54634195569680145431

9 Dec 2025, 21:12 UTC345 views10 reactionsread 9 August 2026
Photo

Ситуация: Мой восьмилетний племянник сегодня стал жертвой мошенников Развели и пообещали какой то ауграм в ЛС с фейка некой Кристиночки. Ну хоть на нюдсы не развели! Малютка залогинился в чужую учетку эпл и ему залочили айфон, радует, что это был старый 12-ый айфон, который был списан (все лучшее - детям) Такие дела! Самое важное обсудить с детьми, что НИКТО ничего БЕСПЛАТНО никогда никому в интернете просто так

custom 60326017183892144686custom 60330719314087806883custom 54631437212833617171

3 Dec 2025, 13:54 UTC303 views7 reactionsread 9 August 2026
Photo

Музей мусора в Калининграде - это все еще лучший музей города

custom 54656050210118113547

Showing the 8 most recent of 8 posts we hold for @NyChtoZaEblan. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“Сказать что хотел?” (@NyChtoZaEblan), 110 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/NyChtoZaEblan.

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.