Channel
@pscmanthra
On this record: Topic · Growth · Engagement · Posts · Polls · Citations · Cite this entry
5,700subscribers
-57 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001499223226 |
|---|---|
| Type | Channel |
| Username | @pscmanthra |
| Created | Between 1 May 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/pscmanthra |
Education — 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 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 11:09 | 5,700 | +11 |
| 6 Oct 2026, 23:22 | 5,689 | +5 |
| 30 Sept 2026, 02:57 | 5,684 | -12 |
| 16 Sept 2026, 07:37 | 5,696 | -6 |
| 12 Sept 2026, 18:59 | 5,702 | -7 |
| 8 Sept 2026, 13:16 | 5,709 | -11 |
| 3 Sept 2026, 15:01 | 5,720 | +1 |
| 31 Aug 2026, 13:43 | 5,719 | +1 |
| 28 Aug 2026, 15:08 | 5,718 | -4 |
| 26 Aug 2026, 00:33 | 5,722 | -7 |
| 22 Aug 2026, 16:46 | 5,729 | -3 |
| 19 Aug 2026, 07:13 | 5,732 | -6 |
| 16 Aug 2026, 16:58 | 5,738 | -4 |
| 12 Aug 2026, 17:34 | 5,742 | -9 |
| 10 Aug 2026, 00:28 | 5,751 | -6 |
| 6 Aug 2026, 07:31 | 5,757 | no change |
| 6 Aug 2026, 07:24 | 5,757 | first reading |
20 posts held, back to 20 August 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pages 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 20 posts for this entry, the most recent from 29 November 2022. An engagement rate over an empty window would be a number about nothing.
Answer for Question 2
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Photo, posted without a caption
Answer for Question 4
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Photo, posted without a caption
Answer for Question 2
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Photo, posted without a caption
Answer for Question 2
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Photo, posted without a caption
Answer for Question 4
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Photo, posted without a caption
Answer for Question 3
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @pscmanthra. 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.
The 6 most recent of 10 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Answer for Question 2
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Answer for Question 4
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Answer for Question 2
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Answer for Question 2
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Answer for Question 4
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Answer for Question 3
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 20 August 2022 to 29 November 2022. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
“📚 KERALA PSC CURRENT AFFAIRS 📚” (@pscmanthra), 5,700 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/pscmanthra.
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.