Channel
@dubrovskyiround2
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
48subscribers
+41 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003666922190 |
|---|---|
| Type | Channel |
| Username | @dubrovskyiround2 |
| Created | 18 May 2026 — measured — dated from the channel’s first post |
| First recorded | 31 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/dubrovskyiround2 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 09:21 | 48 | +11 |
| 9 Sept 2026, 15:42 | 37 | +24 |
| 1 Sept 2026, 02:47 | 13 | +6 |
| 31 Aug 2026, 14:45 | 7 | no change |
| 31 Aug 2026, 14:30 | 7 | first reading |
8 posts held, back to 18 May 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 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 18 May 2026. An engagement rate over an empty window would be a number about nothing.
6 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 66.7% | |
| 👍 | 2 | 33.3% |
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 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 6 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 18 May 2026 to 18 May 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.
Feature 2: Locked Notes in Saved Messages — After 🔒 I added a lightweight privacy layer for sensitive content stored inside Saved Messages. Instead of creating a separate private chat or changing the whole Saved Messages structure, users can lock individual saved messages when needed. How it works: 1. Long press a sensitive saved message 2. Tap "Lock" in the context menu 3. The message is moved to "Locked Notes" …
❤3👍2
Dubrovskyi | Round 2 pinned «Design Contest 2026, Round 2: Submission For this round, I focused on two Telegram features that are already useful but could better accommodate real-world user behavior: 1. Telegram Reminder (Before / After) 🗓 A faster way to create reminders for multiple…»
Feature 2: Locked Notes in Saved Messages — Before 😪 Saved Messages is no longer just a chat with yourself. 🚫 For many Telegram users, it serves as a personal storage space: documents, screenshots, addresses, codes, cards, files, links, and private notes are kept there because it’s fast and always available. Telegram already describes Saved Messages as personal cloud storage for messages and media. But sensitive …
Additional screens Main Reminder 🗓 The reminder screen keeps the original Telegram structure, but adds a clearer top switch between Calendar and Days of week. Multi-select 📆 Users can select several exact dates on the calendar and create one reminder flow for all selected dates. Days of week — 1 day 🗓 A simple weekly reminder for one selected weekday. Days of week — 6 days 🗓️ When many days are selected, the butt…
❤1
Feature 1: Telegram Reminder — After 🗓 I redesigned Telegram Reminder around two lightweight additions: Multi-select dates ✅ Users can select multiple dates directly in the calendar and create multiple reminders with the same text and time. This covers all remaining use cases where we can’t predict and standardize reminders. Days of the week ✅ Users can switch from calendar dates to weekdays and choose exactly whe…
Feature 1: Reminders in Telegram — Before 🗓 Reminders in Telegram are convenient because they offer a wide range of customizable settings for users. However, the current interface still lacks two very common types of reminders: 1. Multiple specific dates 🗓 Sometimes users need the same reminder for several different dates. Currently, they have to create the same reminder over and over again. 2. Days of the week 📆 …
Design Contest 2026, Round 2: Submission For this round, I focused on two Telegram features that are already useful but could better accommodate real-world user behavior: 1. Telegram Reminder (Before / After) 🗓 A faster way to create reminders for multiple dates and days of the week. 2. Locked Notes in Saved Messages (Before / After) 🔒 A privacy layer for sensitive saved items stored within Saved Messages. Both c…
Channel created
Showing the 8 most recent of 8 posts we hold for @dubrovskyiround2. 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.
Named by 4 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Dubrovskyi | Round 2” (@dubrovskyiround2), 48 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/dubrovskyiround2.
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.