vouch @YeorinMonroe for my 3 pcs twt acc with 100 ffs, tysm!

Channel
୨ৎVOUCHES NI GANDA>ᴗ<
@VouchesNiYeorin
On this record: Growth · Engagement · Posts · Citations · Cite this entry
3subscribers
+1 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 | -1003910223238 |
|---|---|
| Type | Channel |
| Username | @VouchesNiYeorin |
| Created | 6 May 2026 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/VouchesNiYeorin |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 00:37 | 3 | +1 |
| 14 Aug 2026, 03:00 | 2 | no change |
| 8 Aug 2026, 11:20 | 2 | first reading |
Engagement
12 posts held, back to 6 May 2026 — 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 12 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
opened na!!! thank you very much very very lejet seller and very quick to reply. Thank you for the visib acc 🙂↕️🙂↕️
vouch @YeorinMonroe for my visib twt acc thank u for the fast transac !! 💓
oki na daw po
vouch @YeorinMonroe for my visib twt acc thank u for the fast transac !! 💓
opened na daw po. sold (3) 100 ffs visib twt accs!!
vouching @YeorinMonroe for x acc visib !! very smooth and fast transaction 🩷🩷
HOOOO VOUCH!!
LEJET SILER!!! VOUCHHH!!!
VOUCHE!!!!!🩷
Channel created
Channel photo updated
Showing the 12 most recent of 12 posts we hold for @VouchesNiYeorin. 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 2 registered channels — 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“୨ৎVOUCHES NI GANDA>ᴗ<” (@VouchesNiYeorin), 3 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/VouchesNiYeorin.
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.