Telegram RegisterThe public register of Telegram
Telegram profile photo for Vile's vouches 🤝

Channel

Vile's vouches 🤝

@suggest

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

102subscribers

+21 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003651559038
TypeChannel
Username@suggest
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/suggest

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 27 September 2026 and assigned it the closest of 31 fixed categories, at 54% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

8110291.56 August 2026 — 81 subscribers9 August 2026 — 81 subscribers13 August 2026 — 83 subscribers19 August 2026 — 84 subscribers27 August 2026 — 88 subscribers3 September 2026 — 87 subscribers30 September 2026 — 89 subscribers10 October 2026 — 102 subscribers6 August 202610 October 2026
8 measurements spanning 65 days, net +21. 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 78–105 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 03:22102+13
30 Sept 2026, 12:4089+2
3 Sept 2026, 09:1687-1
27 Aug 2026, 10:1788+4
19 Aug 2026, 09:2484+1
13 Aug 2026, 09:5983+2
9 Aug 2026, 18:4581no change
6 Aug 2026, 12:0981first reading

Engagement

20 posts held, back to 2 July 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Aug 2026, 13:00 UTC56 viewsread 9 August 2026

15+ username claims done since start of august — too busy for vouches please pardon

6 Aug 2026, 12:54 UTC63 viewsread 9 August 2026

Thanks @grip for using my @middleman service for $5,000 👑

27 Jul 2026, 23:38 UTC233 viewsread 9 August 2026

I MM’d $15000 for @grip Thanks for using me! Amazing deal ❤️❤️

23 Jul 2026, 15:18 UTC261 viewsread 9 August 2026

Vouch vile got us our twitter account back for 23k, service took 3 weeks but all was ok will recommend 👍

23 Jul 2026, 15:18 UTC234 viewsread 9 August 2026

MM’d a $11,000 deal for @asylumic, held up his end of the bargain

23 Jul 2026, 15:18 UTC285 viewsread 9 August 2026

VOUCH @grip quick ig claim $4.5k Legit dude, Like $13k+ in business with him so far and No Problems

20 Jul 2026, 20:02 UTC266 viewsread 9 August 2026

extremely sorry, do not have the time to post vouches due to the ig rush, have done probably 65+ unbans this week

18 Jul 2026, 16:21 UTC289 viewsread 9 August 2026

vouch @grip 11.2k deal i went first and he is legit no issue :)

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

Names

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

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

“Vile's vouches 🤝” (@suggest), 102 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/suggest.

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.