18 Jul 2022, 17:39 UTCviews —
Channel created
Channel
TOP DROP
@topoviydrop
On this record: Previous handles · Growth · Engagement · Posts · Citations · Cite this entry
1,779subscribers
+196 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 | -1001606365778 |
|---|---|
| Type | Channel |
| Username | @topoviydrop |
| Created | 18 July 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/topoviydrop |
Previous handles
@topoviydrop was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
@mishki7km
held 7 August 2026 – 7 August 2026
held 7 August 2026 – 7 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 06:55 | 1,779 | -10 |
| 2 Sept 2026, 22:24 | 1,789 | -1 |
| 31 Aug 2026, 00:37 | 1,790 | +3 |
| 27 Aug 2026, 23:34 | 1,787 | -4 |
| 24 Aug 2026, 14:18 | 1,791 | -6 |
| 20 Aug 2026, 12:00 | 1,797 | +224 |
| 13 Aug 2026, 10:05 | 1,573 | -7 |
| 10 Aug 2026, 13:23 | 1,580 | -3 |
| 7 Aug 2026, 09:03 | 1,583 | no change |
| 7 Aug 2026, 08:54 | 1,583 | first reading |
Engagement
1 post held, back to 18 July 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3 pages 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 1 post for this entry, the most recent from 18 July 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
Showing the 1 most recent of 1 post we hold for @topoviydrop. 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“TOP DROP” (@topoviydrop), 1,779 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/topoviydrop.
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.