Telegram RegisterThe public register of Telegram

Channel

NEOD'TECH PS SIDE

@NEODTECHPS

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001751955986
TypeChannel
Username@NEODTECHPS
CreatedBetween 1 December 2021 and 9 December 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/NEODTECHPS

Growth

17 August 2026 — 1 subscribers14 August 2026 — 1 subscribers7 August 202614 August 2026
2 measurements spanning 7 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 16:311no change
7 Aug 2026, 04:341first reading

Engagement

20 posts held, back to 9 December 2021the 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 7 January 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Jan 2022, 02:33 UTCviews —

NEOD'TECH PS SIDE pinned «PATNERSHIP NEOD'TECH PAGE O8 ㅤ ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ O1. 𝗣𝗢𝗜𝗦𝗢𝗡 𝗗𝗔𝗥𝗧𝗦 𝗢𝗙𝗖༆ (V) ㅤ* @POISONDARTSOFCC ㅤ* @PoisondartBot O2. 𝗟𝗔𝗡★𝗡𝗚 𝗞𝗧𝗛 ㅤ* @OFCLANANGKTH ㅤ* @LGKTHMPPSBOT O3.𝗦𝗧𝗔𝗥𝗖𝗛𝗬𝗟𝗔𝗕𝗘𝗟 ㅤ* @STARCHYLABEL ㅤ* @STARCHYPSBOT ㅤㅤ𝗔𝗘𝗦𝗧𝗥𝗢𝗖𝗜𝗟𝗬 ㅤ* @AESTROCILYOFC ㅤ*…»

7 Jan 2022, 02:14 UTCviews —

NEOD'TECH PS SIDE pinned «PATNERSHIP NEOD'TECH PAGE 14 ㅤ ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ O1. 𝐃𝐑𝐀𝐆𝐎𝐍 Ⓥ︎𝐎𝐋𝐀𝐍𝐒 ㅤ* @ofcdragonvolans ㅤ* @ofcmppsdgvbot O2. KAWANAN CHANYEOL ㅤ* @kawananchanyeol ㅤ* @kcypsbot O3. 𝕬𝐑𝐍𝐀𝐖𝐀𝐌𝐀 🇧🇧 ㅤ* @arnawamaofc ㅤ* @mppsarnwbot O4. 𝐎𝐅𝐂 𝐋𝐎𝐂𝐀𝐋𝐄 𝟐𝟏𝟐 ㅤ* @OFCLOCALE212…»

7 Jan 2022, 02:12 UTCviews —

NEOD'TECH PS SIDE pinned «PATNERSHIP NEOD'TECH PAGE 13 ㅤ ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ O1. 404. PROVINSI KTH [ LIBUR ] ㅤ* @provinsikth ㅤ* @pvkthpsbot O2. 𝟳𝟵𝟱. 𝗟𝗢𝗥𝗗 𝗞𝗧𝗛 ✦ [ LIBUR ] ㅤ* @kthlordofc ㅤ* @ldkthmppsbot O3. ✮ - 𝐓𝑹𝑬𝚨NCTI𝐙 [ LIBUR ] ㅤ* @OFCTREANCTIZ ㅤ* @MPPSANTIZBOT O4. The…»

15 Dec 2021, 03:40 UTC41 viewsread 14 August 2026

PATNERSHIP NEOD'TECH PAGE 13 ㅤ ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ O1. 404. PROVINSI KTH [ LIBUR ] ㅤ* @provinsikth ㅤ* @pvkthpsbot O2. 𝟳𝟵𝟱. 𝗟𝗢𝗥𝗗 𝗞𝗧𝗛 ✦ [ LIBUR ] ㅤ* @kthlordofc ㅤ* @ldkthmppsbot O3. ✮ - 𝐓𝑹𝑬𝚨NCTI𝐙 [ LIBUR ] ㅤ* @OFCTREANCTIZ ㅤ* @MPPSANTIZBOT O4. The Vamcastle ㅤ* @OfcVamcastle ㅤ* @Castmppstle_bot O5. V4ПƬΛΣGGЦK ㅤ* @V4NTAEGGUK ㅤ* @MPV4TGBOT O6. 𝐎𝐅𝐂 • 𝕺𝐁𝐄𝐋𝐀𝐙𝐙𝐎 ㅤ* @OFCOBELAZZO ㅤ* @Mppsopz_bot O7. INFINITE ㅤ* @

15 Dec 2021, 03:40 UTC49 viewsread 14 August 2026

PATNERSHIP NEOD'TECH PAGE 14 ㅤ ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ O1. 𝐃𝐑𝐀𝐆𝐎𝐍 Ⓥ︎𝐎𝐋𝐀𝐍𝐒 ㅤ* @ofcdragonvolans ㅤ* @ofcmppsdgvbot O2. KAWANAN CHANYEOL ㅤ* @kawananchanyeol ㅤ* @kcypsbot O3. 𝕬𝐑𝐍𝐀𝐖𝐀𝐌𝐀 🇧🇧 ㅤ* @arnawamaofc ㅤ* @mppsarnwbot O4. 𝐎𝐅𝐂 𝐋𝐎𝐂𝐀𝐋𝐄 𝟐𝟏𝟐 ㅤ* @OFCLOCALE212 ㅤ* @mpps212bot O5. KOSTAN MARKHYUCK ㅤ* @kostanMH ㅤ* @kostmhpsbot BLACK ZONE * @BIackZone O6. 𝐗𝐄𝐍𝐃𝐈𝐎𝐑𝐂 ᏔᏫ ㅤ* @xendiorcwo ㅤ* @MPPSXENDIORC_BOT O7. OFC

15 Dec 2021, 03:40 UTC53 viewsread 14 August 2026

PATNERSHIP NEOD'TECH PAGE 15 ㅤ ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ O1. OFC. DANGEREUX [ L ] ㅤ* @DANGEREUXOFC ㅤ* @mppsdangereuxbot O2. PASDALA ( LIBUR ) ㅤ* @PASDALAOFC ㅤ* @psdalampps_bot O3. 𝐎𝐅𝐂 𝐂𝐀𝐒𝐓𝐋𝐄 𝐉𝐉𝐊 ㅤ* @OFCCASTLEJJK ㅤ* @PSJJKC97BOT O4. 𝐏ARTHENON ㅤ* @OFCPARTHENON ㅤ* @PBPARTHENONBOT O5. 𝐄𝐍𝐇𝐀𝐒𝐏𝐀 ㅤ* @enhaspa_ofc ㅤ* @Enhaspampps_bot O6. OFC. KDDK REBORN ㅤ* @KDDKREBORN ㅤ* @KDDKRMPPSBOT O7. 𝕵𝐀𝐂𝐊𝐁𝐈𝐋𝐀𝐍 ㅤ* @JackbilanOfc ㅤ

15 Dec 2021, 03:40 UTC78 viewsread 14 August 2026

PATNERSHIP NEOD'TECH PAGE 16 ㅤ ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ O1. 強 𝐎𝐅𝐂 𝐆𝐀𝐕𝐑𝐈𝐄𝐋 𝐒𝐐'𝟐𝟏 ㅤ* @OFFICIALGAVRIEL ㅤ* @Mppspfpgavriel_bot O2. B-FURIOUS ㅤ* @bfurious ㅤ* @furiousps_bot O3. 𝐎𝐅𝐂 S‌𝐊𝐄𝐏𝐓𝐈𝐒 T‌𝗔𝐊𝐒𝐎𝐍𝐎𝐌𝐈 ㅤ* @SKEPTISTAKSONOMISQ ㅤ* @SKSTMPPSBOT O4. JENJAEM CITY ㅤ* @JENJAEMCITY ㅤ* @MPPSJENJAEM_BOT O5. 𝐎𝐅𝐂 𝐇𝐎𝐔𝐒𝐄 𝐎𝐅 𝐂𝐀𝐑𝐃'𝐒 ㅤ* @OfcHouseOfCards ㅤ* @MppsHOC_bot O6. 𝐃𝐑𝐀𝐂𝐎𝐒𝐓𝐘𝐀𝐍 𝐎𝐅𝐂 ㅤ* @dracostyanbar ㅤ* @DracostyanMppsbot O7.

Showing the 12 most recent of 20 posts we hold for @NEODTECHPS. 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.

Mentions

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“NEOD'TECH PS SIDE” (@NEODTECHPS), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/NEODTECHPS.

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.