Telegram RegisterThe public register of Telegram

Channel

VAQUERO PS

@vaquerompps

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

3subscribers

+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-1001768097099
TypeChannel
Username@vaquerompps
CreatedBetween 1 December 2021 and 16 March 2022— 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/vaquerompps

Growth

39 August 2026 — 3 subscribers13 August 2026 — 3 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 11:333no change
9 Aug 2026, 14:503first reading

Engagement

20 posts held, back to 16 March 2022 — 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 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 8 April 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Links
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

16 Mar 2022, 06:46 UTC239 viewsread 13 August 2026

𖤍══PAGE 3O ݇-݈ ─────── O1. 𝗢𝗙𝗖 𝗥𝗘𝗗 𝗕𝗔𝗥𝗖𝗢𝗗𝗘 🛡⚔ ⎙ @ofcredbc ➥ @redbcmpps_bot O2. ⎙ ➥ O3. ⎙ ➥ O4. ⎙ ➥ O5. ⎙ ➥ O6. ⎙ ➥ O7. ⎙ ➥ O8. ⎙ ➥ O9. ⎙ ➥ 1O. ⎙ ➥ ║▌│█║▌│ █║▌│█│║ ║▌│█║▌│ █║▌│█│║ @VAQUEROOFC

16 Mar 2022, 06:42 UTC135 viewsread 13 August 2026

𖤍══PAGE 29 ݇-݈ ─────── O1. 𝗢𝗙𝗖 𝗘𝗔𝗚𝗟𝗘 𝗨𝗡𝗜𝗧𝗘𝗗 ⎙ @ofceagleunited ➥ @mppseglbot O2. 𝐎𝐅𝐂 𝐋𝐈Ø𝐍𝐆𝐄𝐑'泽 ⎙ @chliongersq ➥ @liongerpatnership_bot O3. 𝗡𝗔𝗘𝗥𝗘𝗩𝗘𝗡 𝗖𝗜𝗧𝗬 ⎙ @NAEREVENCITY ➥ @NAEREVENMPPSBOT O4. 𝗖𝗢𝗢𝗣𝗘𝗥 ⎙ @COOPEROFC ➥ @CooperPartner_bot O5. メ'𝘾𝙡è𝙠𝙞𝙙𝙯 ⎙ @CLEKIDZOFC ➥ @MPPSCLEKIDZ_bot O6. 𝐂𝐀𝐑𝐒𝐏𝐀𝐂𝐄 ⎙ @CarSpacez ➥ @MppsCspBot O7. University Cli…

16 Mar 2022, 06:42 UTC103 viewsread 13 August 2026

𖤍══PAGE 28 ݇-݈ ─────── O1. 𝐏𝐑𝐈𝐕𝐀𝐓𝐄 𝐑𝐎𝐎𝐌 ⎙ @PrivateRoom_15 ➥ @Mppspvrbot O2. 红 ° GLAM∅N EVENT ORGANIZER ⎙ @OFCGLAMONEO ➥ @PSGMEOBOT O3. 321. 𝗩𝗜$𝗨𝗔𝗟 𝗞𝗧𝗛 ⎙ @ofclapakkth ➥ @mppsvskthbot O4. 𝐀𝐆Λ𝐑𝐓𝐇Λ ⎙ @AGARTHAOFC ➥ @MPPSAGARTHABOT O5. 𝐎𝐅𝐂 𝕭𝐑𝐈𝐆𝐄𝐙𝐙 𝐆𝐀𝐍𝐊 🏴‍☠ ⎙ @OPICIBRIGEZZGANK ➥ @MPPSBRIGEZZBOT O6. 𝐎𝐅𝐂 𝐌𝐀𝐑𝐊𝐇𝐘𝐔𝐂𝐊 𝐂𝐈𝐓𝐘⁶² ⎙ @MARKHYUCKCITY62 ➥ @te…

16 Mar 2022, 06:42 UTC92 viewsread 13 August 2026

𖤍══PAGE 27 ݇-݈ ─────── O1. 332. DUNKLĒR BØY ⎙ @dunklerboy ➥ @PSDUNKLERBOY_BOT O2. 𝐎FC BLACK WINDOW ⎙ @OFCBLACKWINDOW ➥ @BWPATNERBOT O3. CIRCLE PHOENIX° ⎙ @OFCPHNXBAR ➥ @TEAMPHNXBOT SUB U: PHOENIX LOTTO° ⎙ @PHNXPOKER 𝐋𝐄𝐖𝐃𝐒 𝐙𝐎𝐍𝐄 𝐏𝐑𝐎𝐌𝐎𝐓𝐄 ⎙ @LEWDSZONEPM O4. 𝐄𝐔𝐏𝐇𝐎𝐑𝐈𝐀 𝐄𝐗𝐏𝐑𝐄𝐒𝐒 ⎙ @EUPHORIAEXPRESS ➥ @mppswitheuphoria_bot O5. 𝐎𝐅𝐂 𝐌𝐄𝐍𝐓𝐑𝐈𝐂𝐇 ⎙ @OFCMENTR…

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

Names

Channels on the register whose handles appear in this channel's posts.

[vakum] 𝐕𝐀𝐐𝐔𝐄𝐑𝐎 𝐎𝐅𝐂
@VAQUEROOFC · 928 postsMEMORIES OF AZTEC EVENT ORGANIZER
@AZTEXICOFC · 2981 postbubar
@bbqofc · 8681 postCALEND MENFESS
@calendariamenfess · 101 post[HIRING]ㅤㅤ. CALENDARIA BAR & CLUB
@CALENDARIAOFFICIAL · 481 postVAKUM ✶ 𝐂𝐆𝐕𝐉𝐊 𝐌𝐈𝐋𝐋𝐄𝐍𝐈𝐔𝐌 ≛
@CGVJKMILLENIUM · 7711 postメ'𝘾𝙡è𝙠𝙞𝙙𝙯
@CLEKIDZOFC · 7421 posteuphoria express, memories
@EUPHORIAEXPRESS · 61 post𝐆𝐄𝐍𝐄𝐑𝐀𝐋𝐒 𝐇𝐎𝐒𝐏𝐈𝐓𝐀𝐋
@GENERALSHOSPITAL · 4411 post𝗠𝗘𝗠𝗢𝗥𝗜𝗘𝗦 𝗢𝗙 𝗚𝗩𝗦
@GUINEAVEROUSCHOOL · 8961 post𝐇𝐎𝐋𝐘𝐂𝐎𝐍 𝐎𝐅𝐂
@holyconofc · 641 postkeep
@INCENTERTAINMENT · 31 post𝐎𝐅𝐂 Ӡ Ƽ９´𝐑𝐀𝐊𝐀𝐍𝐀
@OFC359RAKANA · 1941 post👀
@ofc_cartwheel · 331 postMEMORIES || 𝐎𝐅𝐂 𝐂𝐀𝐒𝐓𝐋𝐄 𝐁𝐎𝐘𝐒
@OFCCASTLEBOYS · 861 postROMBAK
@ofcedderkop · 4181 postMemories – 𝐎𝐅𝐂 𝐅𝐎𝐗 𝐂𝐎𝐑𝐏𝐎𝐑𝐀𝐓𝐈𝐎𝐍
@OFCFOXCORP · 801 post𝗠𝗔𝗡𝗦𝗜𝗢𝗡 𝗡𝗦𝗔
@OFCNSASQ · 3071 post𝗦𝗨𝗚𝗔𝗥 𝗣𝗔𝗣𝗜
@OFCSUGARPAPI · 1811 postMEMORIES. 𝐎𝐅𝐂 𝕭𝐑𝐈𝐆𝐄𝐙𝐙 𝐆Λ𝐍𝐊
@opicibrigezzgank · 651 post[MEMORIES] OFC PARATAKAM
@paratakamofc · 2831 postPHOENIX LOTTO°
@PHNXPOKER · 421 postᴺ 𝖵𝖩𝖱 𝖲𝖤𝖦𝖤𝖭𝖳 ⌕
@VJRSEGENT · 1861 post© @HAWLOGROUP
@zonalowell · 2061 post

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.

“VAQUERO PS” (@vaquerompps), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/vaquerompps.

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.