24 Mar 2018, 10:55 UTC≈4,240 viewsread 9 August 2026
Video
Напоминание: Каждому по ордену
Channel
Флешка Путина
@putindrive
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
114subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001272413550 |
|---|---|
| Type | Channel |
| Username | @putindrive |
| Created | 30 January 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/putindrive |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 06:01 | 114 | no change |
| 6 Aug 2026, 06:11 | 114 | first reading |
Engagement
20 posts held, back to 9 February 2018 — 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 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 20 posts for this entry, the most recent from 24 March 2018. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 26
- Videos
- 1
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 31s
- Average length
- 31s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
18 Mar 2018, 15:39 UTC≈4,630 viewsread 9 August 2026
Photo
Photo, posted without a caption
17 Mar 2018, 14:30 UTC≈4,570 viewsread 9 August 2026
Photo
Напоминание: согласовать
15 Mar 2018, 09:37 UTC≈3,680 viewsread 9 August 2026
Photo
Напоминание: Следующей новостью рассказать почему стараюсь давать меньше денег на деятельность Russia Today
13 Mar 2018, 13:49 UTC≈3,230 viewsread 9 August 2026
Photo
Напоминание: сделать Рекса следующим премьер-министром
13 Mar 2018, 06:02 UTC≈16,000 viewsread 9 August 2026
Photo
Photo, posted without a caption
7 Mar 2018, 21:37 UTC≈3,210 viewsread 9 August 2026
Photo
Напоминание: отправить в СБУ Украины как приложение к запросу Ксюши на посещение Крыма
7 Mar 2018, 12:42 UTC≈5,350 viewsread 9 August 2026
Photo
Напоминание: орден гендиректору Кинопоиска
5 Mar 2018, 11:25 UTC≈2,700 viewsread 9 August 2026
Photo
Напоминание: дать орден за достойную иронию
2 Mar 2018, 10:00 UTC≈3,410 viewsread 9 August 2026
Photo
Photo, posted without a caption
1 Mar 2018, 10:34 UTC≈15,900 viewsread 9 August 2026
Photo
Напоминание: строго наказать Рогозину, чтобы опять не перепутал космодромы
27 Feb 2018, 20:46 UTC≈3,600 viewsread 9 August 2026
Photo
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @putindrive. 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.
Citation-graph rank
Citation-graph rank — 957,005 of 1,169,250entries 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 1 registered channel — 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Флешка Путина” (@putindrive), 114 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/putindrive.
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.