Information regarding the City Of Examination and Admission Certificate for the candidates of Combined Graduate level Examination, 2026 (Tier-I) @parmar_ssc
❤166🙏27🔥18👍14❤🔥8👏2

Channel
@parmar_ssc
On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,335,340subscribers
+42,419 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001559424727 |
|---|---|
| Type | Channel |
| Username | @parmar_ssc |
| Description | SSC GK = PARMAR SSC |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/parmar_ssc |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 77% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
On 18 of the 253 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0016 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /2003425 Aug 2026, 06:30 UTC | 30 minutes | 30,100 → 40,400at least +10,200 | 25 → 28at most +4 | +16.3 |
| /2005726 Aug 2026, 12:01 UTC | 30 minutes | 68,900 → 81,200at least +12,200 | 119 → 122at most +4 | +19.5 |
| /2007827 Aug 2026, 14:29 UTC | 4 days | 137,000 → 177,000at least +39,000 | 134 → 143at most +10 | +62.2 |
| /2010331 Aug 2026, 13:14 UTC | 3 days | 208,000 → 251,000at least +42,000 | 286 → 292at most +7 | +67.0 |
| /201627 Sept 2026, 06:11 UTC | 34 minutes | 46,500 → 55,500at least +8,900 | 73 → 75at most +3 | +14.2 |
| /201737 Sept 2026, 13:20 UTC | 31 minutes | 83,000 → 97,100at least +14,000 | 97 → 99at most +3 | +22.3 |
| /201838 Sept 2026, 10:45 UTC | 3.7 hours | 113,000 → 132,000at least +18,000 | 212 → 218at most +7 | +28.7 |
| /201848 Sept 2026, 13:27 UTC | 4.3 hours | 107,000 → 125,000at least +17,000 | 87 → 92at most +6 | +27.1 |
| /201989 Sept 2026, 03:37 UTC | 12 hours | 105,000 → 122,000at least +16,000 | 213 → 218at most +6 | +25.5 |
| /201999 Sept 2026, 04:09 UTC | 12 hours | 102,000 → 123,000at least +20,000 | 155 → 159at most +5 | +31.9 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the key view_reaction_decoupling, last confirmed 22 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 16:00 | 1,335,340 | +1,619 |
| 15 Sept 2026, 11:18 | 1,333,721 | +2,176 |
| 13 Sept 2026, 17:19 | 1,331,545 | +2,450 |
| 11 Sept 2026, 22:01 | 1,329,095 | +3,416 |
| 9 Sept 2026, 11:56 | 1,325,679 | +6,586 |
| 6 Sept 2026, 04:59 | 1,319,093 | +14,798 |
| 3 Sept 2026, 20:39 | 1,304,295 | +619 |
| 2 Sept 2026, 11:44 | 1,303,676 | +285 |
| 1 Sept 2026, 09:53 | 1,303,391 | +221 |
| 31 Aug 2026, 09:43 | 1,303,170 | +195 |
| 30 Aug 2026, 06:27 | 1,302,975 | -2 |
| 29 Aug 2026, 06:07 | 1,302,977 | +103 |
| 28 Aug 2026, 03:34 | 1,302,874 | +179 |
| 27 Aug 2026, 01:16 | 1,302,695 | +416 |
| 26 Aug 2026, 04:18 | 1,302,279 | +157 |
| 25 Aug 2026, 05:13 | 1,302,122 | +225 |
| 24 Aug 2026, 00:15 | 1,301,897 | +1,516 |
| 22 Aug 2026, 06:06 | 1,300,381 | +700 |
| 20 Aug 2026, 22:04 | 1,299,681 | +1,100 |
| 19 Aug 2026, 19:03 | 1,298,581 | first reading |
426 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 105 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 21 September 2026 |
|---|---|
| Posts held | 426 (4 August 2026 – 21 September 2026) |
| Views total | 48,188,100 |
| Reactions total | 151,136 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 00:43 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 22 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 21 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 255 of this channel’s own posts over the last 30 days (1 of the 24-hour readings behind this are interpolated, not measured directly): across 243 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 7.9 hours of being posted; a typical post has already reached 21.5% of its 24-hour view count within the first hour, and 63.0% within the first six; the median 24-hour reach across those posts is 126,000 views — 9.44% of this channel’s own subscriber count (90th percentile 145,000).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /2041019 Sept 2026, 15:46 UTC | 49 minutes – 1.8 hours old | 33,300 views ~98 reactions | 60 minutes: 24,066 interp.still climbing at last reading | not yet at 24h | 35 minutesprovisional — final view count still climbing |
| /2040919 Sept 2026, 14:37 UTC | 528 minutes – 3.0 hours old | 53,500 views ~171 reactions | 60 minutes: 28,103 interp. → 3.0 hours: 53,500still climbing at last reading | not yet at 24h | 56 minutesprovisional — final view count still climbing |
| /2040719 Sept 2026, 10:40 UTC | 1310 minutes – 6.9 hours old | 83,200 views ~164 reactions | 60 minutes: 21,212 interp. → 3.0 hours: 42,612 interp. → 6.0 hours: 76,200still climbing at last reading | not yet at 24h | 2.9 hoursprovisional — final view count still climbing |
| /2040619 Sept 2026, 10:10 UTC | 146 minutes – 7.4 hours old | 85,200 views ~97 reactions | 60 minutes: 21,707 interp. → 3.0 hours: 45,000 → 6.0 hours: 73,900still climbing at last reading | not yet at 24h | 2.7 hoursprovisional — final view count still climbing |
| /2040519 Sept 2026, 09:21 UTC | 1524 minutes – 8.2 hours old | 85,900 views ~110 reactions | 60 minutes: 19,246 interp. → 3.0 hours: 44,300 → 6.0 hours: 68,100still climbing at last reading | not yet at 24h | 2.7 hoursprovisional — final view count still climbing |
| /2040419 Sept 2026, 07:02 UTC | 1928 minutes – 11 hours old | 95,900 views ~139 reactions | 60 minutes: 22,900 → 3.0 hours: 45,637 interp. → 6.0 hours: 69,700still climbing at last reading | not yet at 24h | 3.2 hoursprovisional — final view count still climbing |
| /2040319 Sept 2026, 07:01 UTC | 1929 minutes – 11 hours old | 95,100 views ~107 reactions | 60 minutes: 22,442 interp. → 3.0 hours: 45,818 interp. → 6.0 hours: 69,700still climbing at last reading | not yet at 24h | 3.2 hoursprovisional — final view count still climbing |
| /2040219 Sept 2026, 03:54 UTC | 2512 minutes – 14 hours old | 105,000 views ~185 reactions | 60 minutes: 18,226 interp. → 3.0 hours: 36,800 → 6.0 hours: 66,500 → 12 hours: 99,400still climbing at last reading | not yet at 24h | 4.2 hoursprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
232,683 reactions across 426 posts, in 7 distinct kinds. The most used accounts for 72.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 168,313 | 72.3% | |
| 👍 | 14,302 | 6.15% | |
| ❤🔥 | 12,619 | 5.42% | |
| 🙏 | 12,449 | 5.35% | |
| 😍 | 11,569 | 4.97% | |
| 🔥 | 7,632 | 3.28% | |
| 👏 | 5,799 | 2.49% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 426 of the 426 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 232,683 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 426 most recent posts we hold, published 4 August 2026 to 21 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Information regarding the City Of Examination and Admission Certificate for the candidates of Combined Graduate level Examination, 2026 (Tier-I) @parmar_ssc
❤166🙏27🔥18👍14❤🔥8👏2
SSC JHT 2026 Answer Key OUT !! @parmar_ssc
❤60👏10🔥10
SSC CGL 2026 | REASONING EXPECTED PAPER - 6 Extremely Sorry Everyone, kuch technical glitch k karan aapko application pe different mock dikh rhe the... but ab sb shi hai.. to jaldi se ye dinner k sath finish krlo 😋 👉 https://youtu.be/r_bKKg2ghZ8 ShubhRatri 🍀
❤67❤🔥3😍3🙏3👍2
7068824945 9235798380
❤556👍115🙏51😍36🔥27👏21❤🔥13
Photo, posted without a caption
❤318🔥27😍24👏12👍7
Selection Post
🙏310❤101👍23🔥15😍9❤🔥8👏4
Ye Q aaj as it is repeat hua hai
❤🔥376❤53🔥41👏24🙏22
Selection Post
❤285🔥33❤🔥16👏13🙏11😍4
SSC CGL 2026 | ENGLISH EXPECTED PAPER - 6 https://youtu.be/gER2qI-RD_k
❤78🔥8😍4
Reasoning Expected Mock-6 is LIVE! Due to a technical issue, a different mock was initially available on the app. Please attempt the updated Mock-6 now. Click Here 👉 MOCK-6 🎯 Solution Video: 8:30 PM And English Mock Solution will be Live at 7 PM Thankoo
❤118👍5🔥4
SSC CGL 2026 | MATHS EXPECTED PAPER - 6 https://youtu.be/FDK9Jr5ef_c
❤76❤🔥8🙏3🔥2
SSC CGL 2026 | TRIGONOMETRY (QUADRANT SYSTEM) | MATH HOTSHOT https://youtu.be/e1x3dDcpYic
❤105❤🔥7👍7🔥6
Showing the 12 most recent of 426 posts we hold for @parmar_ssc. 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.
@parmar_ssc edited 16 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The 2 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.
What type of chemical reaction occurs when quicklime reacts with water?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
STENO me EXPECTED PAPER ka Tagda response dekhte hue ab SELECTION POST k bhi EXPECTED PAPERS karvane ka Nirnay liya hai . To ye batao SELECTION POST me EXPECTED PAPER kis LEVEL ka karvaya jae ?
The shares total 115%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 426 most recent posts we hold, published 4 August 2026 to 21 September 2026. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 308 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
2 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“PARMAR SSC” (@parmar_ssc), 1,335,340 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/parmar_ssc.
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.