Channel
intelecto PCS
@intelectopcs
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,491subscribers
+104 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001174527966 |
|---|---|
| Type | Channel |
| Username | @intelectopcs |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/intelectopcs |
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 12 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 15:17 | 6,491 | +7 |
| 8 Oct 2026, 03:58 | 6,484 | +1 |
| 2 Oct 2026, 00:19 | 6,483 | +12 |
| 16 Sept 2026, 04:37 | 6,471 | -7 |
| 12 Sept 2026, 13:18 | 6,478 | +35 |
| 8 Sept 2026, 13:00 | 6,443 | +25 |
| 3 Sept 2026, 17:57 | 6,418 | +57 |
| 31 Aug 2026, 20:13 | 6,361 | -7 |
| 28 Aug 2026, 21:28 | 6,368 | no change |
| 28 Aug 2026, 10:02 | 6,368 | -8 |
| 25 Aug 2026, 02:08 | 6,376 | -11 |
| 21 Aug 2026, 10:34 | 6,387 | +11 |
| 18 Aug 2026, 18:24 | 6,376 | -8 |
| 15 Aug 2026, 20:08 | 6,384 | -3 |
| 12 Aug 2026, 11:45 | 6,387 | 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.
@PranaPCSofficial · 21,654
Telegram ranks this channel #19 of 71 here — alongside 70 others — read 23 September 2026
@UPSC_Static_GK_GS_Quiz_SSC_GD · 156,174
Telegram ranks this channel #22 of 83 here — alongside 82 others — read 12 August 2026
@Geography_in_Hindi_Class_Notes · 136,429
Telegram ranks this channel #41 of 76 here — alongside 75 others — read 13 August 2026
@aloksir · 85,907
Telegram ranks this channel #53 of 71 here — alongside 70 others — read 18 August 2026
@Guideratul · 56,883
Telegram ranks this channel #64 of 72 here — alongside 71 others — read 23 August 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 October 2026 — this entry's latest reading, not the date you are reading this.
“intelecto PCS” (@intelectopcs), 6,491 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/intelectopcs.
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.