https://t.me/darkbatbatman
Channel
me
@oppppppppppmmmm
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
16subscribers
-1 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004471465987 |
|---|---|
| Type | Channel |
| Username | @oppppppppppmmmm |
| Created | Between 1 June 2026 and 22 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/oppppppppppmmmm |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 1 October 2026 and assigned it the closest of 31 fixed categories, at 46% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 07:40 | 16 | -1 |
| 30 Sept 2026, 04:18 | 17 | -5 |
| 16 Sept 2026, 13:20 | 22 | -4 |
| 9 Sept 2026, 01:15 | 26 | +2 |
| 30 Aug 2026, 21:54 | 24 | +6 |
| 23 Aug 2026, 09:53 | 18 | +1 |
| 22 Aug 2026, 20:15 | 17 | first reading |
Engagement
20 posts held, back to 22 August 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 20 posts for this entry, the most recent from 22 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
5 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 2 | 40.0% | |
| ❤🔥 | 1 | 20.0% | |
| 🔥 | 1 | 20.0% | |
| 😁 | 1 | 20.0% |
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 6 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 5 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 22 August 2026 to 22 August 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.
Recent posts
تکرار هر روز که بیدار میشه ، قبل از هرکاری گوشیش را چک میکند تا شاید پیام یا زنگ مهمی داشته باشد اما هیچ چیز نیست و بعد با ناامیدی برنامه هایش را چک میکند وقتی میبیند انجاهم چیزی نیست موزیک پلیرش را باز میکند و اهنگی را که او را در افکارش غرق میکند پلی میکند و با خود میگوید چرا؟ چرا هر روز اینکار را میکنم وقتی مطمئنم هیچ اتفاقی نیوفتاده، چرا هر روز اینکار را تکرار میکنم!
هزار نقاب و یک چهره دختر هر روز روبهروی دیواری میایستاد که پر بود از صورتها؛ صورتهایی خندان، گریان، خشمگین، خسته و بیتفاوت، اما هیچکدام صورت خودش نبود. سالها بود که مردم به او میگفتند چگونه بخندد، چگونه گریه کند، چگونه زیبا باشد و حتی چگونه غمگین به نظر برسد. او نیز، بیآنکه بداند، کمکم چهرهی خودش را فراموش کرده بود. آن روز، آینهای در دست گرفت و برای نخستینبار به خودش نگاه کرد. وحشت کرد. چهرهای که در …
https://t.me/yami_yami_yami_yami
این پیاموفور کنید تا با عکسی که تگتون میکنم براش سناریو بنویسید. جوین باشی قشنگتره جواب ها : https://t.me/oppppppppppmmmm
https://t.me/AuroraTalksDaily
https://t.me/yami_yami_yami_yami
https://t.me/Whatigonnasay
https://t.me/fallofmytears
https://t.me/JRayblue
🔥1
https://t.me/perdidov
https://t.me/piecesffm
😁1
Showing the 12 most recent of 20 posts we hold for @oppppppppppmmmm. 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
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.
Names
Channels on the register whose handles appear in this channel's posts.
@yami_yami_yami_yami · 3422 postsDaylight🩷
@AAEE_1989TV · 231 post𝐴𝑙𝑢𝑟𝑦
@AuroraTalksDaily · 1191 postᯓ𝖢𝖺𝗌𝗍𝗅︎𝖾 𝖯︎𝗁︎𝗈𝖾𝗇︎𝗂𝗑︎☁️🪽͛͛͛ᯓ
@CaStLe_PhOeNiX_028 · 631 post𝐵𝑎𝑡𝐶𝑎𝑣𝑒
@darkbatbatman · 961 postاُقیانوسِ مِشکی؛(.closed)
@fallofmytears · 1341 postتـآسـیـان ٬
@JRayblue · 5761 postShiro Oni
@memoryofmurder · 1101 post-
@mirova_87 · 4501 postᴍᴏᴏɴʟɪɢʜᴛᴛᴇᴀʀꜱミ
@MoonlightTears · 711 postPerdido | گمشده
@perdidov · 531 post𝒫𝒾𝑒𝒸𝑒𝓈
@piecesffm · 1671 post¿?𝓗𝓮𝓭𝓲𝔂𝓮🌱
@pikopeni · 781 postایده های یک انسان نامرئی🍂
@ready_to_get_wet_in_the_Rain · 1381 post𝙍𝙤𝙨𝙖𝙡𝙞𝙩𝙝
@Whatigonnasay · 2,4521 post
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“me” (@oppppppppppmmmm), 16 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/oppppppppppmmmm.
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.