Telegram RegisterThe public register of Telegram
Telegram profile photo for StellarModels l Vouches

Channel

StellarModels l Vouches

@stellarsvouches

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

9subscribers

+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-1001953674270
TypeChannel
Username@stellarsvouches
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live7 September 2026
Measurements held3
Confirmed unchanged3 times, most recently 7 September 2026
On Telegramt.me/stellarsvouches

Growth

898.58 August 2026 — 8 subscribers12 August 2026 — 8 subscribers23 August 2026 — 9 subscribers8 August 202623 August 2026
3 measurements spanning 16 days, net +1. 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 8–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 22:359+1
12 Aug 2026, 16:018no change
8 Aug 2026, 08:068first reading

Engagement

20 posts held, back to 2 December 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 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 21 January 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Jan 2026, 14:35 UTC14 viewsread 12 August 2026

Bought the recruiting blueprint, worked exactly as promised. Got leads within the first €50 of ad spend. Solid system, would recommend.

11 Nov 2025, 09:13 UTC37 viewsread 12 August 2026

Massive thanks to @acquisitie – helped us secure models for $1,499 and $2,999. By far the best recruiter we’ve worked with.

29 Jan 2025, 14:58 UTC108 viewsread 12 August 2026

Best decision ever working with @acquisitie – helped me optimize my ads, and now they perform significantly better! Best recruiter for sure.

27 Jan 2025, 16:50 UTC112 viewsread 12 August 2026

vouch @acquisitie, very professional and helpful throughout the process! Helped me in securing a gem model 💯

26 Jan 2025, 14:02 UTC111 viewsread 12 August 2026

Vouch @acquisitie, provided me with multiple models for nearly 2 years now, always good business

25 Jan 2025, 13:21 UTC109 viewsread 12 August 2026

@acquisitie made it happen again: 2 models, $999–$1499. Hands down the best recruiter.

24 Jan 2025, 17:47 UTC403 viewsread 12 August 2026

Vouch @acquisitie – helped us secure 2 models for $1499. Great communication, easy to work with, and looking forward to growing this partnership!

24 Jan 2025, 14:47 UTC54 viewsread 12 August 2026

Trust @acquisitie to deliver every time – just signed a $999 model and couldn’t be happier.

23 Jan 2025, 21:08 UTC60 viewsread 12 August 2026

Vouch @acquisitie $2500 - good service good model, real hard working girl and everyone happy🤝

31 Dec 2024, 21:03 UTC39 viewsread 12 August 2026

Hey bro, just wanted to give you an update, the tweaks you gave me for my ads really helped, getting way better quality leads now and the cost of acquiring each lead also went down, really appreciate it!

5 Feb 2024, 19:55 UTC362 viewsread 12 August 2026

Thank you @wagwanblud Our deal went good but unfortunately the model ghosted me but overall the process was good and will continue buying models

Showing the 12 most recent of 20 posts we hold for @stellarsvouches. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“StellarModels l Vouches” (@stellarsvouches), 9 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/stellarsvouches.

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.