Channel

𝑺𝒖𝒑𝒆𝒓𝑱𝒊𝒏𝒙

@Super_Jinx2

On this record: Observations · Growth · Engagement · Posts · Citations · Cite this entry

1,616subscribers

-18 since we began measuring on 1 September 2026

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

Register entry

Telegram ID	-1003979676382
Type	Channel
Username	@Super_Jinx2
Created	Between 1 April 2026 and 30 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	1 September 2026
Last confirmed live	2 September 2026
Measurements held	2
Confirmed unchanged	1 time, most recently 2 September 2026
On Telegram	t.me/Super_Jinx2

Observations

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.

Views per post sit far below this size band

9.2 average views per post against 1,616 subscribers — an engagement rate of 0.569%. Across the 2,689 registered channels in the same cohort — 1,000–3,162 subscribers, posting mainly in Persian — the middle half sit between 7.69% and 31.1%, with a median of 16.1%.

What this was computed from
Window	30 days (7 August 2026 – 6 September 2026)
Posts measured	20 of 20 published in the window (20 exact, 0 rounded by Telegram)
Views totalled	184
Mature posts only	0.569% over 20 posts read at least 24h after publication
Subscribers	1,616 measured 2 September 2026
Cohort	b1000:fas · 2,689 channels · p10 3.27% · p25 7.69% · p50 16.1% · p75 31.1% · p90 52.9%
Position in cohort	0.930th percentile · 1/29 the cohort median
Uncertainty	±0.179% of the figure, from Telegram’s rounding
Post language	Persian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_low, last confirmed 6 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.

Growth

2 measurements taken within a single day, net -18. 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 1,613–1,637 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
2 Sept 2026, 15:34	1,616	-18
1 Sept 2026, 20:15	1,634	first reading

Engagement

20 posts held, back to 30 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days: 0.569%; avg views ÷ 1,616 subscribers
Avg views / post: 9.2; 20 posts measured
Reaction rate: —; this channel exposes no reaction counts
Posts in window: 20; of 20 held

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.

What these figures were computed from
Window	Rolling 30 days · latest post in window 30 August 2026
Posts held	20 (30 August 2026 – 30 August 2026)
Views total	184
Reactions total	—
Forwards / comments	not exposed by the public surface — not measured, not estimated
Readings taken	1 Sept 2026, 20:15 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

ایران متصل |𝗦𝘂𝗽𝗲𝗿𝗝𝗶𝗻𝘅
@Super_Jinx · 10,76515 posts

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.

Mentions

Named by 1 registered channel — 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.

ایران متصل |𝗦𝘂𝗽𝗲𝗿𝗝𝗶𝗻𝘅
@Super_Jinx · 10,7651 post

Names

Channels on the register whose handles appear in this channel's posts.

ایران متصل |𝗦𝘂𝗽𝗲𝗿𝗝𝗶𝗻𝘅
@Super_Jinx · 10,7651 post

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.

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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“𝑺𝒖𝒑𝒆𝒓𝑱𝒊𝒏𝒙” (@Super_Jinx2), 1,616 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/Super_Jinx2.

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.