Channel
@PSAERLOKA
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001504635231 |
|---|---|
| Type | Channel |
| Username | @PSAERLOKA |
| Created | Between 1 May 2021 and 11 December 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/PSAERLOKA |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 20:33 | 2 | no change |
| 7 Aug 2026, 04:32 | 2 | first reading |
20 posts held, back to 11 December 2021 — 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 11 January 2022. An engagement rate over an empty window would be a number about nothing.
AERLOKA PARTNERSHIP ━━━━━━━━━━━━━━━━ ﹆𓄹✦ PAGE 16 01. 𝐌Λ𝐑𝐊Ø𝐆𝐀𝐍𝐊 ➳ @MARKOGANK ➵ @TEMANMARKO_BOT 02. SUMMERVILLE HIGH SCHOOL ➳ @OFCSUMMERVILLEHS ➵ @MPPSSMV_BOT 03. 𝗩𝗝𝗥 𝗦𝗘𝗚𝗘𝗡𝗧 ➳ @VJRSEGENT ➵ @VJRSEGENTPSBOT 04. Loveling hospital ➳ @lovelinghosptl ➵ @Pslvh_bot 05. 𝐁𝐎𝐍𝐇𝐄𝐔𝐑 𝐄𝐯𝐞𝐧𝐭 𝐎𝐫𝐠𝐚𝐧𝐢𝐳𝐞𝐫 ➳ @BONHEURORGANIZER ➵ @BREOMpps_bot 06. ➳ ➵ 07. ➳ ➵ 08. ➳ ➵ 09. ➳ ➵ 10. ➳ ➵
Sticker, posted without a caption
AERLOKA PARTNERSHIP ━━━━━━━━━━━━━━━━ ﹆𓄹✦ PAGE 15 01. 強 𝐎𝐅𝐂 𝐆𝐀𝐕𝐑𝐈𝐄𝐋 𝐒𝐐'𝟐𝟏 ➳ @OFFICIALGAVRIEL ➵ @Mppspfpgavriel_bot 02. 𝐎𝐅𝐂 ECTROLUX ➳ @OFC_ECTROLUX ➵ @Ectroluxmppsbot 03. OFC CH KOAB ➳ @KingOffAllBangtan ➵ @MPPSKOADBOT 04. REPUBLIK NAMJA ➳ @REPNAMJA ➵ @REPNAMJAMPPSBOT 05. 𝐋ATHI 𝐅AMS ➳ @ofchlathifams ➵ @lfpps_bot 06. 𝐎𝐅𝐂 𝐂𝐀𝐃𝐄𝐍𝐙𝐀 𝐆𝐀𝐍𝐊 [ ROMBAK ] ➳ @ofccadenzagnk ➵ @mppscdz_bot 07…
Sticker, posted without a caption
AERLOKA PARTNERSHIP ━━━━━━━━━━━━━━━━ ﹆𓄹✦ PAGE 14 01. ➳ ➵ 02. KOSAN RKJ ➳ @kosanrkj ➵ @psrkjbot 03. 𝐎𝐅𝐂 𝐂𝐘𝐏𝐇𝐄𝐑 𝐆𝐀𝐍𝐗 ➳ @OFCYPHERGANX ➵ @Cypherganxmpps_bot 04. $𝗧𝗔𝗥𝗞𝗩𝗢𝗟𝗞 ∅𝗙𝗖 ➳ @OFCSTARKVOLK ➵ @MPPSTARKVBOT 05. 𝐍𝐄Ø 𝐌𝐘𝐓𝐇𝐎𝐋𝐎𝐆𝐘 ➳ @NEOMYTHOLOGY ➵ @nmtpsrobot 06. 𝐎𝐅𝐂 𝐅𝐑𝐄𝐄𝐃𝐎𝐌𝐒𝐐`𝟐𝟏 ➳ @freedomsquad21 ➵ @mppsfos_bot 07. SUGAR DUDA ➳ @OFCSUGARDUDA ➵ @SDUDAMPPSBOT 08. OFC SWØRD ➳ @OFCS…
Sticker, posted without a caption
AERLOKA PARTNERSHIP ━━━━━━━━━━━━━━━━ ﹆𓄹✦ PAGE 13 01. Sexby Promote ➳ @sexbypm ➵ @PartnerSexby_bot 02. 𝗧✪𝗘𝗞𝗢𝗢𝗞 𝗠𝗦-𝟭𝟯 ➳ @OFCTKMSRPW ➵ @PARTNERTKMS_BOT 03. OFC DEVIDOS ➳ @ofcdevidos ➵ @mppsdevidosbot 04. ➳ ➵ 05. W𝐎𝐋𝐅 D𝐄𝐕𝐈𝐋🇰🇬 ➳ @ofcwolfdevil ➵ @PARTNERWLF_BOT 06. ERA 381 ➳ @ERA381 ➵ @official381bot 07. !¡ 𝐉𝐄𝐗𝐄𝐑 𝐒𝐐 !¡ ➳ @ofcjxr ➵ @babujxrbot 08. ➳ ➵ 09. 𝐄𝐍𝐇𝐘𝐏𝐄𝐍 𝐙𝐎𝐍𝐄 ➳ @E…
Sticker, posted without a caption
AERLOKA PARTNERSHIP ━━━━━━━━━━━━━━━━ ﹆𓄹✦ PAGE 12 01. ᨅ ⸼ ࣪ ᥱᥙᥒᥕ᥆ᥒіᥱs𝗍 Ꮺ𓂃ֶָ֪ ➳ @eunwoniest ➵ @eunwoniesttbot ➣ SUB UNIT ➙ IZ*TREND ➙ @OFCIZTREND 02. 𝐊𝐈𝐍𝐆𝐃𝐎𝐌 𝐏𝐀𝐊𝐄𝐓 ➳ @KINGDOMPAKET ➵ @Kantorkingdompaketbot 03. 𝐎𝐅𝐂 𝐏𝐀𝐑Λ𝐍𝐂𝐎𝐗 ➳ @PARANCOXOFC ➵ @PSPRCXBOT 04. OFC LESEHAN BUNDA 73 ❞ ➳ @ofclesehanbunda73 ➵ @lebun73mppsbot 05. 金 𝐃'𝐋𝐔𝐗𝐈𝐕𝐄𝐑 • 𝐒𝐐 ➳ @DLXOFC ➵ @DLXMPSBOT 06. NÆVIZT ➳ @naevi…
Sticker, posted without a caption
AERLOKA PARTNERSHIP ━━━━━━━━━━━━━━━━ ﹆𓄹✦ PAGE 11 01. DIZAESTER ➳ @DIZAESTER ➵ @DZSMPPSBOT 02. 𝐎𝕱𝐂.𝕯𝐄𝐉𝐀𝐍𝐂𝐎𝐊 ➳ @OFCDEJANCOK ➵ @DejancokmppsBot 03. 𝐍𝐈𝐓𝐇⁷⁶ : 𝐍𝐂𝐓 𝐢𝐧 𝐭𝐡𝐞 𝐇𝐨𝐮𝐬𝐞 ➳ @OFCNITH76 ➵ @mppsnithbot 04. 𝐎𝐅𝐂 • 𝕺𝐁𝐄𝐋𝐀𝐙𝐙𝐎 ➳ @OFCOBELAZZO ➵ @Mppsopz_bot 05. ➳ ➵ 06. 𝐌𝐨𝐫𝐚𝐭𝐡𝐨𝐫𝐧 𝐂𝐨𝐫𝐩 ➳ @MTCORP ➵ @TMJJPSBOT ➣ SUB UNIT ➙ 𝐓𝐀𝐄𝐌𝐀𝐑𝐊𝐉𝐀𝐄𝐉𝐎𝐇𝐍 ➙ @TAEMARKJAEJOHN ➣ SUB UNIT ➙ 𝐌𝐎𝐑𝐃𝐑𝐄𝐃 𝐒𝐂𝐇𝐎𝐎𝐋 …
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @PSAERLOKA. 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.
@PSAERLOKA named 98 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.
References a handle that is not a live channel — we have no record it ever was one.
48 more handles are in this same list but not shown individually here — capped at 50.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“PATHERSHIP AERLOKA” (@PSAERLOKA), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/PSAERLOKA.
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.