Channel
@PEPEPMk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
18subscribers
-1 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002176667327 |
|---|---|
| Type | Channel |
| Username | @PEPEPMk |
| Created | Between 1 June 2024 and 23 August 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 9 September 2026 |
| On Telegram | t.me/PEPEPMk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 15:44 | 18 | -1 |
| 24 Aug 2026, 16:55 | 19 | no change |
| 23 Aug 2026, 15:45 | 19 | first reading |
20 posts held, back to 23 August 2024 — 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 20 posts for this entry, the most recent from 20 March 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 videos 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.
369 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 29.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 110 | 29.8% | |
| 🍓 | 88 | 23.8% | |
| 💋 | 86 | 23.3% | |
| 💘 | 84 | 22.8% | |
| 🤣 | 1 | 0.271% |
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 18 of the 20 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 369 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 23 August 2024 to 20 March 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.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
بنص الحرب وما ناسيك ومن ادور وجهي تنساني.
🍓1💋1💘1🤣1
عُيوني تِشتِهي تشوُفك
❤1🍓1💘1
الشاعر عبد الواكف المنتجي
🍓3💋3❤2💘1
@YYYYF ~ 03:28 ⏳
حالتي مثل علوه 💔 😑
🍓3💋3💘3❤2
تفيد🦄
🍓4💋4💘4❤2
علي رشم 🥹
❤5💋5💘5🍓3
فراكك باب خيــبر
💘11❤7💋7🍓6
حلو لو لا
❤9💘6🍓5💋5
كلبي 🤤
❤7💋4💘4🍓3
بس قلبي 🗿 ما لهف غيرك 💔
💘6💋4❤3🍓3
Showing the 12 most recent of 20 posts we hold for @PEPEPMk. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“لـــ𝐀𝐇𝐌𝐄𝐃” (@PEPEPMk), 18 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/PEPEPMk.
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.