Telegram RegisterThe public register of Telegram
Telegram profile photo for Нарешалка UA ️

Channel

Нарешалка UA ️

@nareshalka

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

1,282subscribers

-26 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001266992058
TypeChannel
Username@nareshalka
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/nareshalka

Growth

1,2821,3081,2957 August 2026 — 1,308 subscribers7 August 2026 — 1,308 subscribers10 August 2026 — 1,306 subscribers13 August 2026 — 1,305 subscribers16 August 2026 — 1,297 subscribers19 August 2026 — 1,294 subscribers22 August 2026 — 1,291 subscribers25 August 2026 — 1,282 subscribers7 August 202625 August 2026
8 measurements spanning 18 days, net -26. 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 1,278–1,312 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 17:161,282-9
22 Aug 2026, 07:091,291-3
19 Aug 2026, 07:341,294-3
16 Aug 2026, 17:341,297-8
13 Aug 2026, 13:051,305-1
10 Aug 2026, 17:171,306-2
7 Aug 2026, 12:461,308no change
7 Aug 2026, 08:471,308first reading

Engagement

19 posts held, back to 8 March 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 23 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

54 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 42.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2342.6%
👍713.0%
❤‍🔥611.1%
custom 545611529936123519047.41%
🔥47.41%
🥰47.41%
👀23.70%
😁23.70%
custom 529217361023916670111.85%
🗿11.85%

Custom emoji. 2 of the rows above are 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 17 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 54reactions 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 8 March 2026 to 23 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

23 Jun 2026, 07:45 UTC175 views2 reactionsread 7 August 2026

🟡 Вітаю, шановно спільното! Задля покращення нашого сервісу, просимо пройти невелике опитування (3 питання). Для вас це займе декілька хвилин, для нас - допоможе покращити взаємодію з Нарешалкою та посилити ваше навчання. Ви можете заповнювати форму, навіть якщо завершили навчання - ця інформація буде теж цінною для нас. https://forms.gle/tjEZPGdBReXoiuxT8

2

2 Jun 2026, 07:55 UTC268 views11 reactionsread 7 August 2026

🟡 Вітаю, шановно спільното! Ось і завершується ще один навчальний рік. Хочу привітати усіх, хто завершує своє навчання і тих, хто йде лише на канікули 😎 Які зміни у роботі Нарешалки будуть протягом літа: 1) Пошук тестів НаУрок, МійКлас, JustClass працюватимуть до 09.06.2026. 2) Розширення Нарешалки працюватиме без змін усе літо У випадку інших змін буде повідомлено додатково в наступних постах. Дякуємо, що користу

❤‍🔥52👀2👍1🥰1

31 May 2026, 18:10 UTC256 views2 reactionsread 7 August 2026

🟡 Чому налаштування розширення таке складне? Розширення будується таким чином, аби воно проходило перевірку безпеки в магазинах розширень. Саме тому в розширенні треба самостійно вводити посилання на налаштування та активовувати користувацькі скрипти у браузерних налаштуваннях розширення. Але налаштування відбувається лише один раз, тому маємо надію, що складнощів з цим після публікації інструкції не виникне. http

🔥1🥰1

28 May 2026, 13:56 UTC282 views1 reactionsread 7 August 2026

Роботу відновлено. Сервіс знову доступний.

1

28 May 2026, 13:05 UTC264 viewsread 7 August 2026

Нарешалка на позапланових технічних роботах.

28 May 2026, 10:52 UTC266 views2 reactionsread 7 August 2026
Photo

🟡 Оновлено інструкцію з користування сайтом та розширенням (нарешті). На даний момент у текстовому вигляді розписано інструкцію з користування розширенням, але скоро буде доповнено іншими пунктами. Перевіряємо тут -> https://nareshalka.com/instruction

1🔥1

22 May 2026, 06:06 UTC326 views1 reactionsread 7 August 2026

🟡 Увага! Оновлення розширення. 1) виправлення певних помилок у роботі розширення 2) Дебаг режим. У випадку, якщо у вас існують проблеми з роботою розширення, тепер ви маєте змогу легко поділитись логами з адміністрацією Нарешалки. Дебафи - розширення може не працювати у браузері Opera. Остання версія розширення - 1.10.0. https://chromewebstore.google.com/detail/нарешалка-ua/jhnbmiffgkgibcppakndnjjhenhkbmfd https

🔥1

18 May 2026, 17:38 UTC381 views2 reactionsread 7 August 2026

🟡 Роботу відновлено. Усі сервіси Нарешалки знову працюють. Технічні роботи НЕ були пов'язані з несправностями самої Нарешалки.

❤‍🔥1🥰1

18 May 2026, 15:13 UTC381 views5 reactionsread 7 August 2026

🟡 Увага - незаплановані технічні роботи!

4🔥1

16 Apr 2026, 07:21 UTC708 views5 reactionsread 7 August 2026

🟡 Усі преміум користувачі, які мали/мають преміум з 30 березня, отримають додаткові 16 днів преміуму. Ця умова не стосується тих, хто придбає його сьогодні та на наступні дні.

2👍1🥰1custom 52921736102391667011

14 Apr 2026, 10:15 UTC687 views3 reactionsread 7 August 2026
Photo

🟡 Увага - Оновлення розширення Нарешалки! 1. Виправлено роботу у браузері Google Chrome та інших браузерах, на основі Chromium 2. Інші виправлення. Тепер для роботи розширення потрібний дозвіл на виконання скриптів користувачів. На фото зображено як це зробити для Google Chrome. Аналогічно це робиться і для інших браузерів. Після активації оновіть сторінку з тестом. СЕРЕД ПОТОЧНИХ БАГІВ: У браузері Google Chrome м

👍3

12 Apr 2026, 15:37 UTC531 views3 reactionsread 7 August 2026
Video

🟡 Христос Воскрес! 🐣 Дисклеймер: відео є приколом, який не варто сприймати всерйоз. Дана публікація не несе ніякого політичного змісту.

👍21

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

20 Mar 2026, 13:25 UTCAnonymous Poll67 voters

↓↓↓ Ваша думка ↓↓↓

  1. 🟡 Робити54%
  2. 🟡 Не потрібно, читаємо інструкцію і самі створюємо посилання46%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 19 most recent posts we hold, published 8 March 2026 to 23 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 298,171 of 1,604,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 registered channels — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Нарешалка UA ️” (@nareshalka), 1,282 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/nareshalka.

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.