Telegram RegisterThe public register of Telegram
Telegram profile photo for TESTI VIP PS

Channel

TESTI VIP PS

@TESTIVIPPS

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

49,401subscribers

+2,000 since we began measuring on 24 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1003962634250
TypeChannel
Username@TESTIVIPPS
CreatedBetween 1 April 2026 and 24 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 August 2026
Last confirmed live5 November 2026
Measurements held45
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/TESTIVIPPS

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.

Growth

47,40154,76051,080.524 August 2026 — 47,401 subscribers24 August 2026 — 47,401 subscribers25 August 2026 — 47,694 subscribers26 August 2026 — 48,119 subscribers26 August 2026 — 48,342 subscribers27 August 2026 — 48,944 subscribers28 August 2026 — 49,094 subscribers29 August 2026 — 49,646 subscribers30 August 2026 — 50,089 subscribers31 August 2026 — 50,407 subscribers1 September 2026 — 51,018 subscribers2 September 2026 — 51,526 subscribers4 September 2026 — 51,956 subscribers6 September 2026 — 52,586 subscribers9 September 2026 — 53,691 subscribers12 September 2026 — 54,038 subscribers13 September 2026 — 54,408 subscribers15 September 2026 — 54,760 subscribers17 September 2026 — 54,670 subscribers27 September 2026 — 53,539 subscribers4 October 2026 — 52,548 subscribers9 October 2026 — 52,055 subscribers13 October 2026 — 51,597 subscribers14 October 2026 — 51,442 subscribers15 October 2026 — 51,312 subscribers16 October 2026 — 51,199 subscribers17 October 2026 — 51,058 subscribers19 October 2026 — 50,926 subscribers20 October 2026 — 50,819 subscribers21 October 2026 — 50,699 subscribers22 October 2026 — 50,590 subscribers23 October 2026 — 50,491 subscribers24 October 2026 — 50,378 subscribers25 October 2026 — 50,272 subscribers26 October 2026 — 50,173 subscribers27 October 2026 — 50,082 subscribers28 October 2026 — 50,013 subscribers29 October 2026 — 49,935 subscribers30 October 2026 — 49,860 subscribers31 October 2026 — 49,795 subscribers1 November 2026 — 49,710 subscribers2 November 2026 — 49,619 subscribers3 November 2026 — 49,551 subscribers4 November 2026 — 49,481 subscribers5 November 2026 — 49,401 subscribers49,40124 August 20265 November 2026
45 measurements spanning 73 days, net +2,000. 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 46,297–55,864 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
5 Nov 2026, 02:5149,401-80
4 Nov 2026, 01:2749,481-70
3 Nov 2026, 02:4049,551-68
2 Nov 2026, 05:5849,619-91
1 Nov 2026, 05:2749,710-85
31 Oct 2026, 05:0049,795-65
30 Oct 2026, 04:2149,860-75
29 Oct 2026, 06:5049,935-78
28 Oct 2026, 08:0950,013-69
27 Oct 2026, 09:4950,082-91
26 Oct 2026, 08:1650,173-99
25 Oct 2026, 06:5450,272-106
24 Oct 2026, 06:1050,378-113
23 Oct 2026, 03:0450,491-99
22 Oct 2026, 06:0050,590-109
21 Oct 2026, 03:0650,699-120
20 Oct 2026, 03:2850,819-107
19 Oct 2026, 00:0550,926-132
17 Oct 2026, 22:5651,058-141
16 Oct 2026, 20:5051,199first reading

Engagement

No public post preview. We read this entry on 24 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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

“TESTI VIP PS” (@TESTIVIPPS), 49,401 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/TESTIVIPPS.

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.