Telegram RegisterThe public register of Telegram
Telegram profile photo for DATA PARTNERSHIP

Channel

DATA PARTNERSHIP

@psofcmeriadoc

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001821754568
TypeChannel
Username@psofcmeriadoc
Descriptioncontacts to @OFCMERIADOC
CreatedBetween 1 October 2022 and 18 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live18 September 2026
Measurements held2
On Telegramt.me/psofcmeriadoc

Growth

29 August 2026 — 2 subscribers13 August 2026 — 2 subscribers9 August 202613 August 2026
2 measurements spanning 4 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”. The vertical axis spans 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 19:362no change
9 Aug 2026, 10:502first reading

Engagement

20 posts held, back to 18 February 2023 — 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 4 March 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

4 Mar 2023, 05:00 UTC137 viewsread 13 August 2026

ㅤ 🧜‍♀ 𝐌𝐄𝐑𝐈𝐀𝐃𝐎𝐂 🧜‍♂ ❗PAGE 15❗ ●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬๑ ❒ AKTIF ➪ 𝐎𝐅𝐂 𝐑𝐄𝐗𝐈𝐕𝐎𝐒 𝐆𝐀𝐍𝐊 ➪ @OFCREXIVOSGANK ➪ @MPPSRVSBOT ❒ AKTIF ➪ BØSS PRΣDΛTØRY ➪ @PREDATORY_OFC ➪ @PDRMPPSROBOT ❒ AKTIF ➪ 𝐂𝐇𝐄𝐑𝐈𝐒𝐇 𝐇𝐎𝐒𝐏𝐈𝐓𝐀𝐋༉ ➪ @CherishHospital ➪ @mppschsrobot ❒ AKTIF ➪ BRÜCKEN KARTE ➪ @BRUCKENKARTE ➪ @psuckart_bot ❒ AKTIF ➪ 𝐎𝐅𝐂 𝐁𝐀𝐉𝐈𝐍𝐆𝐀𝐍 𝐌𝐔𝐃𝐀 ➪ @ofcbajinganmuda ➪ @Baj…

4 Mar 2023, 05:00 UTC79 views0 reactionsread 13 August 2026

ㅤ 🧜‍♀ 𝐌𝐄𝐑𝐈𝐀𝐃𝐎𝐂 🧜‍♂ ❗PAGE 14❗ ●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬๑ ❒ AKTIF ➪ BRÜCKEN KARTE ➪ @BRUCKENKARTE ➪ @uckartmpps_bot ❒ AKTIF ➪ #JMHUNITED ➪ @JMHUNITED ➪ @PSMHUBOT ❒ AKTIF ➪ OFC BE SUCCLESSFUL ➪ @OFFICIALBSGROUP ➪ @PARTNERSHIPBSGROUP ❒ AKTIF ➪ SEVENTEEN MEANIE ➪ @SVTMEANIE ➪ @MEANIEMPPSBOT ❒ AKTIF ➪ POTION EVENT ORGANIZER ➪ @POTIONEO ➪ @peomppsbot…

4 Mar 2023, 04:53 UTC62 viewsread 13 August 2026

ㅤ 🧜‍♀ 𝐌𝐄𝐑𝐈𝐀𝐃𝐎𝐂 🧜‍♂ ❗PAGE 13❗ ●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬๑ ❒ AKTIF ➪ 𝗗𝗘𝗦𝗔 𝗝𝗝𝗛 ➪ @jjhvillage ➪ @DSJHMPPSROBOT ᚓ ≼𝚂𝚄𝙱 𝚄𝙽𝙸𝚃 ➪ 𝗡𝗢𝗠𝗔𝗥𝗞𝗥𝗘𝗡 𝗩𝗜𝗟𝗟𝗔𝗚𝗘 ➪ @NOMARKREN ❒ AKTIF ➪ 𝐃𝐀𝐑𝐊 𝐀𝐍𝐆𝐄𝐋𝐒 ➪ @OFCDARKANGELS ➪ @OFCMPPSSALS_BOT ❒ LIBUR ➪ ⍣𝐀₦𝐓𝐈𝐘Ø𝐔 𝐆Λ𝐍𝐊 ➪ @OFCANTIYOU ➪ @ANTIYOUMPPS_BOT ❒ AKTIF ➪ 𓅓✪ 𝐖𝐈𝐙𝐀𝐑𝐃 𝐐𝐔𝐀𝐑𝐓𝐎 ➪ @OFCWIZARDQUARTO ➪ @wztworkps_bot ❒ AKTIF ➪ OFC A…

26 Feb 2023, 01:29 UTC78 viewsread 13 August 2026

ㅤ 🧜‍♀ 𝐌𝐄𝐑𝐈𝐀𝐃𝐎𝐂 🧜‍♂ ❗PAGE 12❗ ●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬๑ ❒ AKTIF ➪ 𝐂𝐑𝐘𝐋A‌𝐍𝔇 𝐒𝐐¹⁶ ➪ @OFCCRYLANDSQ ➪ @pscryland_bot ❒ AKTIF ➪ 𝐕 𝐈 𝐑 𝐀 𝐆 𝐎 ➪ @AREAVIRAGO ➪ @MPPSVIRAGOBOT ❒ AKTIF ➪ 红 ° GLAM∅N EVENT ORGANIZER ➪ @OFCGLAMONEO ➪ @PSGMRCBOT ᚓ ≼𝚂𝚄𝙱 𝚄𝙽𝙸𝚃 ➪ 𝐏𝐢𝐧𝐠𝐮𝐢𝐧𝐨 𝐊𝐮𝐫𝐢𝐫 ➪ @PINGUINOKURIR ❒ AKTIF ➪ 𝐒𝐓𝐈𝐊𝐞𝐬 𝐑𝐏 ➪ @STIKESRP ➪ @STIKRPSBOT ❒ AKTIF ➪ 𝐊𝐀𝐌𝐀𝐔𝐑𝐈 À 𝐋’…

26 Feb 2023, 01:29 UTC56 viewsread 13 August 2026

ㅤ 🧜‍♀ 𝐌𝐄𝐑𝐈𝐀𝐃𝐎𝐂 🧜‍♂ ❗PAGE 11❗ ●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬๑ ❒ AKTIF ➪ S‌𝐏𝐀𝐍𝐒𝐄𝐑𝐀 ➪ @OFCSPANSERASQ ➪ @MPPSSPSRBOT ❒ AKTIF ➪ 𝕿𝐎𝐗𝐎𝐏𝐇𝐈𝐋𝐈𝐓𝐄 𝐎𝐅𝐂 ➪@TOXOPHILITEOFC ➪ @MPPSTXPHBOT ❒ AKTIF ➪ ۩𝗢𝗙𝗖 𝗩𝗔𝗡𝗖𝗛𝗜𝗟𝗟𝗘𝗦۩ ➪ @OFCVANCHILLES ➪ @PSVANCHILLESBOT ❒ AKTIF ➪ VORSTRA RPW ➪ @OFCVORSTRA ➪ @VRPWPSBOT ❒ AKTIF ➪ @RPORGANIZER ➪ @RPORGANIZER ➪ @RPOMPPS_BOT ❒ AKTIF ➪…

22 Feb 2023, 13:25 UTC53 viewsread 13 August 2026

ㅤ 🧜‍♀ 𝐌𝐄𝐑𝐈𝐀𝐃𝐎𝐂 🧜‍♂ ❗PAGE 10❗ ●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬๑ ❒ AKTIF ➪ MONSTER PROMOTE ➪ @MONSTERPROMOTE ➪ @MONSP_PSBOT ❒ AKTIF ➪ 𓄂 𝕺𝐅𝐂. 𝕾𝐈𝐋𝐈𝐖𝐀𝐍𝐆𝐈 ➪ @ofc_siliwangi ➪ @siliwangimppsbot ❒ LIBUR ➪ 𝐎𝐅𝐂 𝐂À𝐑𝐒𝐓𝐕𝐀 𝐕𝐎𝐋𝐊𝐀 ➪ @OFCCARSTVAVOLKA ➪ @CARSTVAMPPSBOT ᚓ ≼𝚂𝚄𝙱 𝚄𝙽𝙸𝚃 ➪ 𝐃𝐘𝐋𝐑𝐔𝐆𝐀 𝐇𝐎𝐒𝐏𝐈𝐓𝐀𝐋 ➪ @DylrugaHospital ❒ AKTIF ➪ 𝗢𝗙𝗖 𝗦𝗧𝗢𝗥𝗠 𝗗𝗥𝗘𝗔𝗠 ➪ @OFCSTORMDREAM ➪ @MPPSTDREA…

Showing the 12 most recent of 20 posts we hold for @psofcmeriadoc. 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“DATA PARTNERSHIP” (@psofcmeriadoc), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/psofcmeriadoc.

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.