
Channel
πππππ ππππππβοΈ
@ph22c
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
4,695subscribers
-124 since we began measuring on 7 September 2026
Risers and fallers across the register Β· movement among entries of 3,162β10,000.
Register entry
| Telegram ID | -1001761695896 |
|---|---|
| Type | Channel |
| Username | @ph22c |
| Created | Between 1 December 2021 and 30 April 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/ph22c |
Topic
Gaming β 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 62% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 00:45 | 4,695 | -9 |
| 8 Nov 2026, 13:47 | 4,704 | -3 |
| 5 Nov 2026, 00:31 | 4,707 | -8 |
| 1 Nov 2026, 16:29 | 4,715 | -6 |
| 30 Oct 2026, 02:08 | 4,721 | -3 |
| 27 Oct 2026, 00:46 | 4,724 | -2 |
| 24 Oct 2026, 02:50 | 4,726 | -7 |
| 21 Oct 2026, 13:27 | 4,733 | -6 |
| 18 Oct 2026, 10:11 | 4,739 | -6 |
| 15 Oct 2026, 18:46 | 4,745 | -9 |
| 12 Oct 2026, 08:17 | 4,754 | -14 |
| 5 Oct 2026, 10:00 | 4,768 | -21 |
| 27 Sept 2026, 06:37 | 4,789 | -14 |
| 18 Sept 2026, 01:19 | 4,803 | -2 |
| 14 Sept 2026, 03:55 | 4,805 | -5 |
| 10 Sept 2026, 05:16 | 4,810 | -9 |
| 7 Sept 2026, 12:48 | 4,819 | first 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.
Appears in Telegramβs recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly β each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone elseβs query is independent of having been queried itself.
@panadolsz Β· 26,238
Telegram ranks this channel #38 of 90 here β alongside 89 others β read 12 September 2026
@Vit3mins Β· 21,260
Telegram ranks this channel #56 of 84 here β alongside 83 others β read 23 September 2026
@pharmacy_college2 Β· 26,702
Telegram ranks this channel #71 of 81 here β alongside 80 others β read 12 September 2026
@physsiccaallpharmaccyy Β· 18,582
Telegram ranks this channel #78 of 90 here β alongside 89 others β read 5 October 2026
@STAFF_IQ Β· 30,800
Telegram ranks this channel #84 of 86 here β alongside 85 others β read 7 September 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegramβs list for THAT channel, not this one β see how this is measured.
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 13 November 2026 β this entry's latest reading, not the date you are reading this.
βπππππ ππππππβοΈβ (@ph22c), 4,695 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/ph22c.
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.