Telegram RegisterThe public register of Telegram
Telegram profile photo for PSP VAULT

Channel

PSP VAULT

@PSP_Vault

Has discussion group

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

5,445subscribers

+2,393 since we began measuring on 8 September 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002677343005
TypeChannel
Username@PSP_Vault
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 September 2026
Last confirmed live5 November 2026
Measurements held16
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/PSP_Vault

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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

3,0525,4454,248.58 September 2026 — 3,052 subscribers11 September 2026 — 3,052 subscribers11 September 2026 — 3,130 subscribers14 September 2026 — 3,278 subscribers19 September 2026 — 3,411 subscribers28 September 2026 — 4,116 subscribers6 October 2026 — 4,332 subscribers13 October 2026 — 4,548 subscribers16 October 2026 — 4,656 subscribers19 October 2026 — 4,904 subscribers22 October 2026 — 5,084 subscribers25 October 2026 — 5,198 subscribers28 October 2026 — 5,294 subscribers30 October 2026 — 5,332 subscribers2 November 2026 — 5,387 subscribers5 November 2026 — 5,445 subscribers8 September 20265 November 2026
16 measurements spanning 57 days, net +2,393. 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 2,693–5,804 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 08:505,445+58
2 Nov 2026, 10:065,387+55
30 Oct 2026, 18:395,332+38
28 Oct 2026, 03:575,294+96
25 Oct 2026, 07:165,198+114
22 Oct 2026, 12:505,084+180
19 Oct 2026, 09:384,904+248
16 Oct 2026, 01:094,656+108
13 Oct 2026, 00:364,548+216
6 Oct 2026, 05:574,332+216
28 Sept 2026, 22:394,116+705
19 Sept 2026, 01:183,411+133
14 Sept 2026, 19:163,278+148
11 Sept 2026, 05:583,130+78
11 Sept 2026, 00:243,052no change
8 Sept 2026, 23:473,052first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

“PSP VAULT” (@PSP_Vault), 5,445 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/PSP_Vault.

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.