7 May 2026, 00:21 UTC2 viewsread 12 August 2026
bruh
Channel
Vichillant Proof
@Vichiproofs
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
6subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001642581847 |
|---|---|
| Type | Channel |
| Username | @Vichiproofs |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 12 October 2026 |
| On Telegram | t.me/Vichiproofs |
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 2 October 2026 and assigned it the closest of 31 fixed categories, at 65% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 19:42 | 6 | -1 |
| 12 Aug 2026, 17:47 | 7 | no change |
| 7 Aug 2026, 14:26 | 7 | first reading |
Engagement
10 posts held, back to 27 April 2025 — 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 10 posts for this entry, the most recent from 7 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
10 Nov 2025, 04:54 UTC17 viewsread 12 August 2026
LIST ORDERAN NOVEMBER 2025 1. upfoll ig nolog 100f by F ✅ 2. canva invite 1 month by Z ✅
11 Sept 2025, 07:50 UTC79 viewsread 12 August 2026
LIST ORDERAN SEPTEMBER 2025 1. upboard 10 bbc by B ✅ 2. upfoll ig web 100f by J ✅ 3. t.u BTN noktel nfs by H ✅ 4. upfoll ig login hit base 100f by N ✅ 5. upview 2kv by K ✅ 6. upfoll ig web 400f by C ✅ 7. upview 4,9kv by O ✅ 8. upreact nprem 55r by J ✅ 9. upreact nprem 500r by S ✅ 10. upfoll ig login hit base 300f by M ❌ 11. upfoll ig nolog 400f by S ❌ 12. upfoll ig nolog 250f by H ❌ 13. akun gmail 5 by P ✅ 14. upfol…
27 Jul 2025, 03:07 UTC153 viewsread 12 August 2026
mau nulis list orderan keburu lupa yeah
10 Jun 2025, 08:11 UTC158 viewsread 12 August 2026
mulai sekarang aku jarang up testi foto ya, liat aja dari RnK
10 Jun 2025, 08:11 UTC152 viewsread 12 August 2026
Photo
{𖤝} as a form of proof of the piece of mind number { 316 - 322 }. thank so lonely for shopping at @VichiStaa, hope you come back again guys!! #upfollig #upreact (2) #boostch (2) #upview (2)
17 May 2025, 16:38 UTC114 viewsread 12 August 2026
Photo
{𖤝} as a form of proof of the piece of mind number { 311 - 315 }. thank so lonely for shopping at @VichiStaa, hope you come back again guys!! #upfollig (2) #viu #boostch (2)
17 May 2025, 16:26 UTCviews —
Vichillant Proof pinned «LIST ORDERAN MEI 2025 1. uplike ig nolog 100f by H ✅ 2. viu anlim 1m by N ✅ 3. 2 boost ch by D ✅ 4. 2 boost ch by E ✅ 5. 4 boost ch by G ✅ 6. uplike ig nolog 500L by Z ❌ 7. upfoll ig nolog 200f by O ✅ 8. akun ig kosongan 10 by S ✅ 9. 4 boost ch by C ✅ 10.…»
11 May 2025, 11:01 UTC112 viewsread 12 August 2026
gaada antrian, drop order sini 🤩🤩
27 Apr 2025, 22:37 UTC121 viewsread 12 August 2026
Photo
{𖤝} as a form of proof of the piece of mind number { 306 - 310 }. thank so lonely for shopping at @VichiStaa, hope you come back again guys!! #upfollig (3) #cnit #acc ig kosongan #uplikeig
Showing the 10 most recent of 10 posts we hold for @Vichiproofs. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Vichillant Proof” (@Vichiproofs), 6 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Vichiproofs.
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.