Telegram RegisterThe public register of Telegram
Telegram profile photo for DictatorMeme

Channel

DictatorMeme

@DictatorMeme1

On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

2,848subscribers

-60 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-1002132914613
TypeChannel
Username@DictatorMeme1
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live3 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/DictatorMeme1

Growth

2,8482,9082,8787 August 2026 — 2,908 subscribers7 August 2026 — 2,908 subscribers10 August 2026 — 2,907 subscribers14 August 2026 — 2,896 subscribers17 August 2026 — 2,878 subscribers21 August 2026 — 2,869 subscribers24 August 2026 — 2,864 subscribers28 August 2026 — 2,862 subscribers31 August 2026 — 2,855 subscribers3 September 2026 — 2,848 subscribers7 August 20263 September 2026
10 measurements spanning 27 days, net -60. 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 2,839–2,917 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 06:452,848-7
31 Aug 2026, 07:432,855-7
28 Aug 2026, 05:152,862-2
24 Aug 2026, 18:282,864-5
21 Aug 2026, 01:522,869-9
17 Aug 2026, 20:172,878-18
14 Aug 2026, 14:162,896-11
10 Aug 2026, 19:312,907-1
7 Aug 2026, 12:012,908no change
7 Aug 2026, 11:552,908first reading

Engagement

20 posts held, back to 30 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 20 posts for this entry, the most recent from 17 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Apr 2026, 19:49 UTC945 viewsread 7 August 2026

🤑Добавляем стикеры! https://t.me/addstickers/DictatorCryptoFight 🩸🤑Распространяем!

14 Sept 2025, 10:17 UTC≈1,470 viewsread 7 August 2026

🤑Открываем счёт и прогреваем кошельки. https://web3.okx.com/join/DICTATORCRYPTO

13 Sept 2025, 18:59 UTC≈1,200 viewsread 7 August 2026
Forwarded from @LegionDictatorCrypto

🤑Добавляем стикеры! https://t.me/addstickers/DictatorCryptoFight 🩸🤑Распространяем!

9 Sept 2025, 15:43 UTC≈1,470 viewsread 7 August 2026

🩸Активируемся! https://x.com/dictatorcrypt/status/1965182922874372443?s=46

21 Aug 2025, 12:14 UTC≈1,840 viewsread 7 August 2026

⚡️Легион!!! ⚡️Перекличка!!! ⚡️Переходим по ссылке и ставим реакцию!!! https://t.me/DictatorCryptoDCT/7510 ☝️Все без исключения.

9 Aug 2025, 16:18 UTC≈1,900 viewsread 7 August 2026

⚡️Делаем дело! https://x.com/dictatorcrypt/status/1954214771999264836?s=46

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

Mentions

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Not Guide [Ru]
@notguide_ru · 111,636
Telegram ranks this channel #10 of 62 here — alongside 61 others — read 20 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“DictatorMeme” (@DictatorMeme1), 2,848 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/DictatorMeme1.

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.