Telegram RegisterThe public register of Telegram

Channel

RESVEET MPPS

@resveetmpps

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2subscribers

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

Register entry

Telegram ID-1001915961259
TypeChannel
Username@resveetmpps
Created9 May 2023measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held1
On Telegramt.me/resveetmpps

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 03:352first reading

Engagement

19 posts held, back to 9 May 2023the 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 19 posts for this entry, the most recent from 4 July 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

4 Jul 2023, 05:55 UTC60 viewsread 14 August 2026

╔════༺•••❁•••༻════╗ 𝙰𝚃𝚃𝙰𝙲𝙷𝙼𝙴𝙽𝚃 𝙾𝟺 ╚════༺•••❁•••༻════╝ ៚ @SHANIEFLOSOFC @SHANIESMPPS_BOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @VXONEOFC @VXONEMPPS_BOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @ @ 【 ᴀᴄᴛɪᴠᴇ/ᴠᴀᴋᴜᴍ 】 ៚ @ @ 【 ᴀᴄᴛɪᴠᴇ/ᴠᴀᴋᴜᴍ 】 ៚ @ @ 【 ᴀᴄᴛɪᴠᴇ/ᴠᴀᴋᴜᴍ 】

29 Jun 2023, 07:16 UTC69 views0 reactionsread 14 August 2026

╔════༺•••❁•••༻════╗ 𝙰𝚃𝚃𝙰𝙲𝙷𝙼𝙴𝙽𝚃 𝙾𝟹 ╚════༺•••❁•••༻════╝ ៚ @ELIXIRAGENCY @ELIXIRMPPS_BOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @VESARIUSGALAXYOFC @VGXMPPSBOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @THEPOWERWISDOM @TPWMPPS_BOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @HAILSATANOFC @HAILSMPPS 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @WINKCAFE @THEWINKCFE_BOT 【 ᴀᴄᴛɪᴠᴇ 】

27 Jun 2023, 14:47 UTC76 viewsread 14 August 2026

╔════༺•••❁•••༻════╗ 𝙰𝚃𝚃𝙰𝙲𝙷𝙼𝙴𝙽𝚃 𝙾𝟸 ╚════༺•••❁•••༻════╝ ៚ @IRIDESCENTOFC @IRDMPPSBOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @ELPHIDRAGENCY @MPPSELPHIDRABOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @EUVEGENIA0FC @MPPSVEN_BOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @EISZAPFENAGENCY @MPPSEISZAPFENBOT 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @Orphicagency @Orphicmmpsbot 【 ᴀᴄᴛɪᴠᴇ 】

27 Jun 2023, 14:47 UTC72 viewsread 14 August 2026

╔════༺•••❁•••༻════╗ 𝙰𝚃𝚃𝙰𝙲𝙷𝙼𝙴𝙽𝚃 𝙾𝟷 ╚════༺•••❁•••༻════╝ ៚ @CharmyLandOFC @CharmyOffc_bot 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @FLORISTOFC @FLORISTOFCbot 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @MasterMisteri_OFCAGC @OFCMasterMisteri_Bot 【 ᴀᴄᴛɪᴠᴇ 】 ៚ @GARZAVOS_OFC @GARZAVOS_MPPS 【 ᴀᴄᴛɪᴠᴇ】 ៚ @FLUMMOXOFC @FlummoxMpfp_bot 【 ᴀᴄᴛɪᴠᴇ 】

27 Jun 2023, 14:46 UTC68 viewsread 14 August 2026

╔════༺•••❁•••༻════╗ 𝙰𝚃𝚃𝙰𝙲𝙷𝙼𝙴𝙽𝚃 𝙾𝙾 ╚════༺•••❁•••༻════╝ ៚ @ @ 【 ᴀᴄᴛɪᴠᴇ/ᴠᴀᴋᴜᴍ 】 ៚ @ @ 【 ᴀᴄᴛɪᴠᴇ/ᴠᴀᴋᴜᴍ 】 ៚ @ @ 【 ᴀᴄᴛɪᴠᴇ/ᴠᴀᴋᴜᴍ 】 ៚ @ @ 【 ᴀᴄᴛɪᴠᴇ/ᴠᴀᴋᴜᴍ 】 ៚ @ @ 【 ᴀᴄᴛɪᴠᴇ/ᴠᴀᴋᴜᴍ 】

27 Jun 2023, 14:44 UTC62 viewsread 14 August 2026

╔════༺•••❁•••༻════╗ 𝐃𝐀𝐓𝐀 Ꮢ𝐄𝐒𝐕𝐄𝐄𝐓 ΛᎶ𝐄𝐍𝐂𝐘 ╚════༺•••❁•••༻════╝ ɴᴀᴍᴀ ⦂ Ꮢ𝐄𝐒𝐕𝐄𝐄𝐓 ΛᎶ𝐄𝐍𝐂𝐘 ᴄʜ ᴏꜰᴄ ⦂ @RESVEETOFC ʙᴏᴛ ᴏꜰᴄ ⦂ @resveetofficial_bot ʙᴏᴛ ᴍᴘᴘꜱ ⦂ @mppsresveet_robot ᴄʜ ᴍᴘᴘꜱ ⦂ @resveetmpps ꜱᴛᴀᴛᴜꜱ ⦂ ᴀᴄᴛɪᴠᴇ 【 𝙽𝙾𝙽 𝙼𝙾𝙽𝙾 】 ➴➵➶➴➵➶➴➵➶➴➵➶➴➴➵➶➴ ɴᴀᴍᴀ ⦂ Ꮢ𝐄𝐒𝐕𝐄𝐄𝐓 ΛᎶ𝐄𝐍𝐂𝐘 ᴄʜ ᴏꜰᴄ ⦂ @RESVEETOFC ʙᴏᴛ ᴏꜰᴄ ⦂ @resveetofficial_bot ʙᴏᴛ ᴍᴘᴘꜱ ⦂ @mppsresveet_robot ᴄʜ ᴍᴘᴘꜱ ⦂ @resveetmpps ꜱᴛᴀᴛᴜꜱ ⦂ ᴀᴄᴛɪᴠᴇ 【 𝙼𝙾𝙽𝙾 】 ➴➵➶➴➵➶

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

Citation-graph rank

Citation-graph rank — 1,317,437 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“RESVEET MPPS” (@resveetmpps), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/resveetmpps.

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.