Telegram RegisterThe public register of Telegram

Channel

PS RAZEDOS

@arsiprazedos

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

5subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001616731658
TypeChannel
Username@arsiprazedos
CreatedBetween 1 December 2021 and 12 December 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/arsiprazedos

Growth

58 August 2026 — 5 subscribers13 August 2026 — 5 subscribers8 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 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:325no change
8 Aug 2026, 18:465first reading

Engagement

20 posts held, back to 12 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 16 July 2022. 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

13 Jul 2022, 13:08 UTC49 viewsread 13 August 2026

━━━ 𝐑𝐀𝐙𝐄𝐃𝐎𝐒 ━━━ ❑ PAGE 19 O1. ❑ 𝐎𝐅𝐂 𝐃𝐀𝐑𝐐𝐈𝐗Ø𝐓𝐄 ➪ CH . @OFCDARQIXOTE ➪ BOT . @darqixotempps_bot ➪ STATUS . ACTIVE O2. ❑ 𝐀𝐁𝐀𝐍𝐆𝐓𝐀𝐍 𝐒𝐐 ➪ CH . @Abangtansq ➪ BOT . @ABSQPartnerbot ➪ STATUS . ACTIVE O3. ❑ 𝐅INDING 𝐋OVE in 𝐅LIGHT ➪ CH . @FindingLoveOFC ➪ BOT . @mppsFLV_bot ➪ STATUS . ACTIVE • 𝐅inding 𝐋ove 𝐂ourier @FindingLoveCourier O4. ❑ 𝐌𝐄𝐍𝐆𝐊𝐄𝐂𝐄 𝐎𝐅𝐂 ➪ CH . @MENGKE

4 Jul 2022, 23:36 UTC40 viewsread 13 August 2026

━━━ 𝐑𝐀𝐙𝐄𝐃𝐎𝐒 ━━━ ❑ PAGE 18 O1. ❑ REPUBLIK KTH ➪ CH . @republikkth ➪ BOT . @psrpkthbot ➪ STATUS . ACTIVE O2. ❑ OFC VANTERIX ➪ CH . @OFCVANTERIX ➪ BOT . @VTRXMPPSBOT ➪ STATUS . ACTIVE O3. ❑ 𝐒𝐔𝐆𝐀𝐑 𝐃𝐀𝐌𝐘 ➪ CH . @OFCSUGARDAMY ➪ BOT . @SUGDAMMPPS_BOT ➪ STATUS . ACTIVE O4. ❑ 𝐀𝗘𝗦𝗣𝗛𝗘𝗡𝗖𝗧𝗦 ➪ CH . @AESPHENCTS ➪ BOT . @MPAEOSBOT ➪ STATUS . ACTIVE • 𝐒𝗨𝗚𝗔𝗥 𝐇𝗔𝗕𝗜𝗕𝗜𝗘

2 Jul 2022, 13:41 UTC37 viewsread 13 August 2026

━━━ 𝐑𝐀𝐙𝐄𝐃𝐎𝐒 ━━━ ❑ PAGE 17 O1. ❑ 𝟮𝟲𝟴. 𝗣𝗢𝗝𝗢𝗞 𝗡𝗚𝗢𝗣𝗜 ➪ CH . @OFCPOJOKNGOPI ➪ BOT . @MPPSPONGO_BOT ➪ STATUS . ACTIVE O2. ❑ 𝐎𝐅𝐂 𝐍𝐀𝐄𝐕𝐓𝐙𝐘 ➪ CH . @OFCNAEVTZY ➪ BOT . @MPPSNAEVTZY_BOT ➪ STATUS . ACTIVE O3. ❑ BIKERS AREA ➪ CH . @OFCBIKERS ➪ BOT . @partnerbikersbot ➪ STATUS . ACTIVE O4. ❑ 𝐗𝐀𝐋𝐕𝐄𝐑𝐎𝐒 ➪ CH . @XALVEROSOFC ➪ BOT . @XELMPPS_BOT ➪ STATUS . ACTIVE O5.

27 Jun 2022, 16:34 UTC42 viewsread 13 August 2026

━━━ 𝐑𝐀𝐙𝐄𝐃𝐎𝐒 ━━━ ❑ PAGE 16 O1. ❑ ØFC 𝐔𝐌𝐀𝐍𝐎 𝐑𝐈𝐒𝐏𝐄𝐓𝐓𝐀𝐁𝐈𝐋𝐄 ➪ CH . @OFCUMANORISPETTABILE ➪ BOT . @ofcUmanousps_bot ➪ STATUS . ACTIVE O2. ❑ 𝐍𝐈𝐄𝐕𝐀𝐍𝐆𝐎𝐎𝐊 ➪ CH . @ofcnievangook ➪ BOT . @mppsnievangookbot ➪ STATUS . ACTIVE O3. ❑ 𝐎𝐅𝐂 𝐌𝐄𝐑𝐕𝐄𝐋𝐋𝐄𝐑 ➪ CH . @ofcmervellersq ➪ BOT . @mppsmrvbot ➪ STATUS . ACTIVE O4. ❑ UNDEAD NIGHT CLUB ➪ CH . @UNDEADCLUBOFC ➪ BOT . @UNDEAD

27 Jun 2022, 11:32 UTC29 viewsread 13 August 2026

━━━ 𝐑𝐀𝐙𝐄𝐃𝐎𝐒 ━━━ ❑ PAGE 15 O1. ❑ 𝐃e𝐕olver 𝐂ircuit ➪ CH . @DeVolverCircuit ➪ BOT . @partnerdvcbot ➪ STATUS . ACTIVE O2. ❑ 553 𝐔𝐍𝐋𝐘𝐌𝐀𝐍𝐓𝐗𝐓 𝐎𝐅𝐂 ➪ CH . @OFCUMTXT ➪ BOT . @PSUMTITAESBOT ➪ STATUS . ACTIVE O3. ❑ 𝗗𝗥𝗘𝗔𝗠-𝗦𝗤𝗨𝗔𝗗 𝗭★𝗡𝗘 ➪ CH . @DRMSQZONE ➪ BOT . @DSZMPPS_BOT ➪ STATUS . ACTIVE O4. ❑ 𝐃𝐞𝐥𝐭𝐚𝐅𝐨𝐫𝐜𝐞 𝐎𝐟𝐜 ➪ CH . @DeltaForceOfc ➪ BOT . @mpssDeltaForcebot ➪ ST

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

Named by 1 registered channel — 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.

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.

“PS RAZEDOS” (@arsiprazedos), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/arsiprazedos.

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.