Channel
@archiveneybys
On this record: Growth · Engagement · Posts · Citations · Cite this entry
12subscribers
+4 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003878427935 |
|---|---|
| Type | Channel |
| Username | @archiveneybys |
| Created | Between 1 February 2026 and 9 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 4 times, most recently 18 September 2026 |
| On Telegram | t.me/archiveneybys |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 21:55 | 12 | +1 |
| 20 Aug 2026, 02:52 | 11 | +3 |
| 12 Aug 2026, 14:01 | 8 | no change |
| 11 Aug 2026, 16:15 | 8 | first reading |
20 posts held, back to 9 July 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 26 July 2026. An engagement rate over an empty window would be a number about nothing.
⠀⠀⠀ 𝐍𝐄𝐔𝐑𝐎𝐍 𝐀𝐁𝐘𝐒𝐒⠀ ⠀⠀⠀ ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀ page : 𝟬7 01. ⾕ : 𝐄𝐧𝐜𝐡𝐚𝐧𝐭𝐞𝐝 𝐂𝐚𝐬𝐭𝐥𝐞 𝐊𝐢𝐧𝐝𝐞𝐫𝐠𝐚𝐫𝐭𝐞𝐧 ⠀⠀ ■ : @Enchantedcastleofc ⠀⠀ ■ : @MPPSencinofc_Bot ⠀ ■ : LIBUR SUB UNIT : 𝐊𝐚𝐜𝐢𝐧 { 𝐊𝐚𝐧𝐭𝐢𝐧 𝐄𝐧𝐜𝐢𝐧 } 𖠿 @KANTINOFC 𖠿 LIBUR 02. ⾕ : POTION EVENT ORGANIZER ⠀⠀ ■ : @POTIONEO ⠀⠀ ■ : @PEOMPPSBOT ⠀ ■ : ACTIVE 03. ⾕ : ⠀⠀ ■ : ⠀⠀ ■ : ⠀ ■ : 04. ⾕ : ⠀⠀ ■ : ⠀⠀ ■ : ⠀ ■ : 05. ⾕ : ⠀⠀ ■ : ⠀⠀ ■ : …
Sticker, posted without a caption
⠀⠀⠀ 𝐍𝐄𝐔𝐑𝐎𝐍 𝐀𝐁𝐘𝐒𝐒⠀ ⠀⠀⠀ ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀ page : 𝟬6 01. ⾕ : ཐི༏ཋྀ 𝐅α𝖾𝗋υ𐓣𝖾 𝐄ꭑρ𝗂𝗋𝖾 𝐀𝖼αᑯ𝖾ꭑ𝗒 𓃗 ⠀⠀ ■ : @FAERUNEACADEMY ⠀⠀ ■ : @AllianceFEA_bot ⠀ ■ : ACTIVE 02. ⾕ : ”RYDESTER HIDE:OUT ..+/🫀🪬 ⠀⠀ ■ : @RYDESTER ⠀⠀ ■ : @MPPSTHERS_BOT ⠀ ■ : VAKUM 03. ⾕ : 𝗙𝗢𝗫𝗧𝗥𝗢𝗧 𝗔𝗟𝗟𝗜𝗔𝗡𝗖𝗘 ⠀⠀ ■ : @OFCFoxTrot ⠀⠀ ■ : @mppsfxtbot ⠀ ■ : ACTIVE 04. ⾕ : 𝓡𝐀𝐈𝐍𝐁𝐎𝐖 ÈÖ ⠀⠀ ■ : @OFCRAINBOWEO ⠀⠀ ■ : @DREAMMPPS_BOT ⠀ ■ …
Sticker, posted without a caption
⠀⠀⠀ 𝐍𝐄𝐔𝐑𝐎𝐍 𝐀𝐁𝐘𝐒𝐒⠀ ⠀⠀⠀ ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀ page : 𝟬5 01. ⾕ : 𝐎𝐅𝐂 𝐊𝐀𝐈𝐎𝐄𝐍𝐈𝐗 ⠀⠀ ■ : @KAIOENIX ⠀⠀ ■ : @HUOBANNIXBOT ⠀ ■ : VAKUM 02. ⾕ : [UNIT : FIMM ] — 𝗖𝗥𝗘𝗦𝗧𝗛𝗘𝗥 ⠀⠀ ■ : @OFCRESTHER ⠀⠀ ■ : @Mppscresther_bot ⠀ ■ : ACTIVE 03. ⾕ : 𝟮𝟰𝟵. 𝗠𝗢𝗥𝗧𝗛𝗔𝗟𝗬𝗦 𝗦𝗤𝗨𝗔𝗗 ⠀⠀ ■ : @OFCMORTHALYS ⠀⠀ ■ : @PARTNERMTHBOT ⠀ ■ : ACTIVE 04. ⾕ : 𝐎𝐅𝐂 𝐌𝐎𝐑𝐏𝐇𝐈𝐂 ⠀⠀ ■ : @ofcmorphic ⠀⠀ ■ : @psmorphicbot ⠀ ■ : ACTIVE 05. ⾕…
Sticker, posted without a caption
⠀⠀⠀ 𝐍𝐄𝐔𝐑𝐎𝐍 𝐀𝐁𝐘𝐒𝐒⠀ ⠀⠀⠀ ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀ page : 𝟬4 01. ⾕ : 𝗩𝗨𝗟𝗞𝗔𝗡𝗨𝗦 : 𝗡𝗘𝗪 𝗘𝗥𝗔 ⠀⠀ ■ : @VULKANUSOFC ⠀⠀ ■ : @VULKANUSMPPS_BOT ⠀ ■ : ACTIVE 02. ⾕ : 𝐀𝐓𝐇𝐄𝐑𝐀 𝐕𝐄𝐍𝐓𝐄𝐑𝐀𝐀𝐂𝐀𝐃𝐄𝐌𝐘 ⠀⠀ ■ : @OFC_AVACADEMY ⠀⠀ ■ : @MppsAVY_bot ⠀ ■ : LIBUR 03. ⾕ : 𝐂𝐀𝐄𝐋𝐕𝐈𝐑𝐎𝐍 𝐄𝐕𝐄𝐍𝐓 𝐎𝐑𝐆𝐀𝐍𝐈𝐙𝐄𝐑 ⠀⠀ ■ : @CAELVIRONOFC ⠀⠀ ■ : @MPPSCLEO_BOT ⠀ ■ : ACTIVE 04. ⾕ : 𝗘𝗡-𝗨𝗡𝗜𝗧𝗘𝗗 ⠀⠀ ■ : @OFCENUNITED ⠀⠀ ■ : @ENUNITEDMPPSBOT ⠀ ■ : V…
Sticker, posted without a caption
⠀⠀⠀ 𝐍𝐄𝐔𝐑𝐎𝐍 𝐀𝐁𝐘𝐒𝐒⠀ ⠀⠀⠀ ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀ page : 𝟬3 01. ⾕ : 𝐖INATA 𝐄VENT 𝐎RGANIZER ⠀⠀ ■ : @WINATAORGANIZER ⠀⠀ ■ : @WINATAPSBOT ⠀ ■ : ACTIVE 02. ⾕ : 𝗩𝗢𝗥𝗧𝗘𝗫𝗜𝗥 𝗡𝗘𝗫𝗨𝗦 ⠀⠀ ■ : @OFCVORTEXIRNEXUS ⠀⠀ ■ : @KawanVornex_bot ⠀ ■ : ACTIVE 03. ⾕ : 光狼. KŌUGARŌ ⠀⠀ ■ : @OFFICIALKOUGARO ⠀⠀ ■ : @Temankougarobot ⠀ ■ : ACTIVE 04. ⾕ : 𝗢𝗙𝗙𝗜𝗖𝗜𝗔𝗟 𝗧𝗛𝗘 𝗩𝗔𝗟𝗜𝗔𝗡𝗧 ⠀⠀ ■ : @OFCTHEVALIANT ⠀⠀ ■ : @kawanvaliant_bot ⠀…
Sticker, posted without a caption
⠀⠀⠀ 𝐍𝐄𝐔𝐑𝐎𝐍 𝐀𝐁𝐘𝐒𝐒⠀ ⠀⠀⠀ ㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡㅡ⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀ page : 𝟬2 01. ⾕ : 𝐎𝐅𝐂 𝐃𝐑𝐀𝐆𝐎𝐍 𝐂𝐀𝐒𝐓𝐋𝐄 🏰 ⠀⠀ ■ : @OFCDRAGONCASTLE ⠀⠀ ■ : @MPPSDRAGOSBOT ⠀ ■ : ACTIVE 02. ⾕ : 𝗥Ξ𝗕𝗜𝗥𝗧𝗛 : 𝗠𝗘𝗠𝗢𝗥𝗬 𝗗𝗘𝗩𝗜𝗗𝗘 ⠀⠀ ■ : @REBIRTHMD ⠀⠀ ■ : @REBMDMPPSbot ⠀ ■ : LIBUR 03. ⾕ : 𝗥Ξ𝗜𝗞Ξ𝗧𝗦𝗨-𝗞𝗜 [冷血記] ⠀⠀ ■ : @OFCREIKETSU ⠀⠀ ■ : @PSREIKETSUKIBOT ⠀ ■ : ACTIVE 04. ⾕ : CHROME OF CHRONOS ⠀⠀ ■ : @OFCCHRONOS ⠀⠀ ■ : @CocmppsBot ⠀ ■ : ACT…
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @archiveneybys. 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.
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.
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.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“PS NEURON ABYSS” (@archiveneybys), 12 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/archiveneybys.
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.