Channel
@Aeneops
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
4subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001741469366 |
|---|---|
| Type | Channel |
| Username | @Aeneops |
| Created | Between 1 December 2021 and 3 February 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/Aeneops |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 4 November 2026 and assigned it the closest of 31 fixed categories, at 26% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 21:08 | 4 | +1 |
| 13 Aug 2026, 15:32 | 3 | no change |
| 7 Aug 2026, 04:50 | 3 | first reading |
20 posts held, back to 3 February 2022 — 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 16 July 2022. An engagement rate over an empty window would be a number about nothing.
ᅠᅠ ✧ — PAGE 05 — ✧ O1. ✭ @JASUKEVILLAGEOFFICIAL ✷ @enhysq ✭ @JAYABERSAMAJSKENHYBOT 𖦹 ACTIVE O2. ✭ @ofcredbc ✭ @redbrcodempps_bot 𖦹 ACTIVE O3. ✭ @meditrinahospital ✭ @MppsMH_bot 𖦹 ACTIVE O4. ✭ @OFCPENGKHIANAT ✭ @OFCMPPHBOT 𖦹 ACTIVE O5. ✭ @MARKASGENZOFC ✷ @NCTZYOFC ✷ @NCTAESPAOFC ✷ @LAKESWARAEO …
Sticker, posted without a caption
ᅠᅠ ✧ — PAGE 04 — ✧ O1. ✭ @GEMAMANSIONS ✭ @OFCGEMAPSBOT 𖦹 ACTIVE O2. ✭ @THVJENCOMPANY ✭ @kawantjencbot 𖦹 ACTIVE O3. ✭ @KJRIOFC ✭ @MPPSKJRIH_BOT 𖦹 ACTIVE O4. ✭ @JAEROSETOWN ✭ @thetownmpps_bot 𖦹 ACTIVE O5. ✭ @OFCPERFECCIONBANGTAN ✭ @MEDPARTPERFECCION_BOT 𖦹 ACTIVE O6. ✭ @ZEPHWOLFOFC ✭ @ZEPHWOLFMP…
Sticker, posted without a caption
ᅠᅠ ✧ — PAGE 03 — ✧ O1. ✭ @MAESTROJEKATEHA ✭ @MPPSMJKBOT 𖦹 ACTIVE O2. ✭ @OFCALESTRA ✷ @OFCAROCE ✷ @OFCACASTRA ✭ @MPPSALESTRA_BOT 𖦹 ACTIVE O3. ✭ @IVERANERS ✭ @IVERANERSPSBOT 𖦹 ACTIVE O4. ✭ @ofcJjaeyongcity ✭ @mppsjaeyongcitybot 𖦹 ACTIVE O5. ✭ @OFCBARTENDOSGANK ✭ @mppsbartendosgankbot 𖦹 ACTIVE …
Sticker, posted without a caption
ᅠᅠ ✧ — PAGE 02 — ✧ O1. ✭ @OFCNMC ✭ @NMCPSBOT 𖦹 ACTIVE O2. ✭ @BUMIOFC ✭ @bumipartnerbot 𖦹 ACTIVE O3. ✭ @ADLYRWO ✭ @ADLYRMPPSWO_BOT 𖦹 ACTIVE O4. ✭ @CGVJKMILLENIUM ✷ @LUCIFEROUSOFC ✷ @KIMKTHOFC ✭ @CGVJKMBOT 𖦹 ACTIVE O5. ✭ @POTTERKOPOFC ✭ @MPSKOPBOT 𖦹 ACTIVE O6. ✭ @OFCSK8TER ✷ @OFCDEMOK…
Sticker, posted without a caption
ᅠᅠ ✧ — PAGE 01 — ✧ O1. ✭ @eutuxiaEORP ✷ @eutuxiafmradio ✷ @ZEUSTHRONES ✭ @eutuxiamediapartner 𖦹 ACTIVE O2. ✭ @SGRDUDA ✷ @OFCSUGARJANDA ✭ @SDUDAMPPSBOT 𖦹 ACTIVE O3. ✭ @KINGTAEMINKOOK ✭ @psktmkbot 𖦹 ACTIVE O4. ✭ @Alfarendraofc ✷ @Stlcourt_ofc ✷ @Ofccassiopeia ✷ @basecassiopeia ✭ @ofcpsgabungan_bo…
Sticker, posted without a caption
ᅠᅠ ✧ — PAGE 00 — ✧ O1. ✭ ✭ 𖦹 ACTIVE O2. ✭ ✭ 𖦹 ACTIVE O3. ✭ ✭ 𖦹 ACTIVE O4. ✭ ✭ 𖦹 ACTIVE O5. ✭ ✭ 𖦹 ACTIVE O6. ✭ ✭ 𖦹 ACTIVE O7. ✭ ✭ 𖦹 ACTIVE O8. ✭ ✭ 𖦹 ACTIVE O9. ✭ ✭ 𖦹 ACTIVE 1O. ✭ ✭ 𖦹 ACTIVE
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @Aeneops. 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.
@Aeneops named 48 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“MARKAS BESAR AENEO GANK.” (@Aeneops), 4 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/Aeneops.
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.