Other / unclassifiable — 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 69% 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.
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.
Content that also appears on other registered channels
Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 7 of the 9 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 86 comparable posts for this entry, running 9 December 2018 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Across the whole group of 3, the earliest publisher we hold is @PPPPJ. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 8 August 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
47 measurements spanning 79 days, net -77,780. 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 3,172,017–3,273,131 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)
Subscribers
Change
24 Oct 2026, 14:59
3,183,684
-659
23 Oct 2026, 17:40
3,184,343
+78
22 Oct 2026, 15:59
3,184,265
-638
21 Oct 2026, 10:47
3,184,903
-1,552
20 Oct 2026, 06:27
3,186,455
-1,150
19 Oct 2026, 08:50
3,187,605
-1,059
18 Oct 2026, 05:20
3,188,664
-871
17 Oct 2026, 05:19
3,189,535
-91
16 Oct 2026, 01:47
3,189,626
-239
14 Oct 2026, 23:20
3,189,865
-297
13 Oct 2026, 15:29
3,190,162
-4,876
9 Oct 2026, 19:55
3,195,038
-4,271
5 Oct 2026, 13:36
3,199,309
-7,334
29 Sept 2026, 20:00
3,206,643
-1,629
18 Sept 2026, 04:19
3,208,272
-2,202
15 Sept 2026, 23:20
3,210,474
-2,057
14 Sept 2026, 04:18
3,212,531
-2,507
12 Sept 2026, 10:18
3,215,038
-3,047
10 Sept 2026, 05:20
3,218,085
-6,738
6 Sept 2026, 20:40
3,224,823
first reading
Engagement
19,735 posts held, back to 24 February 2018 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3,945 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.224%
avg views ÷ 3,183,684 subscribers
Avg views / post
7,130
3,414 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
3,414
of 19,735 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 24 October 2026
Posts held
19,735 (24 February 2018 – 24 October 2026)
Views total
24,356,171
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
24 Oct 2026, 21:30 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.
View velocity
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 3,394 of this channel’s own posts over the last 30 days: across 105 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 2 days of being posted; a typical post has already reached 8.48% of its 24-hour view count within the first hour, and 36.5% within the first six; the median 24-hour reach across those posts is 26,300 views — 0.826% of this channel’s own subscriber count (90th percentile 29,780).
8 most recently posted, with a view-velocity reading
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.
Showing the 12 most recent of 19,735 posts we hold for @PPPJP. 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.
Posts edited after publishing
@PPPJP edited 9 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.
First edit seen
8 August 2026
Most recent edit
8 September 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 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.
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.
Handles this channel named that no longer answer
Dead references
13
handles named in this channel’s posts, vacant today
Evidenced gone
10
we ourselves saw one of these resolve, at some point
Never seen alive
3
vacant every time we have ever looked
@PPPJP named 13 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@x_aether named in 12 posts, 30 September 2026 – 4 October 2026 · confirmed gone 22 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@iiyiiyyy named in 3 posts, 14 October 2026 – 17 October 2026 · confirmed gone 18 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@atr_vn named in 3 posts, 7 October 2026 – 10 October 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@zo7ell named in 2 posts, 8 August 2026 – 8 August 2026 · confirmed gone 15 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@t11jxn named in 1 post, 11 October 2026 – 11 October 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@shda12 named in 1 post, 14 September 2026 – 14 September 2026 · confirmed gone 4 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@sa_p6 named in 1 post, 6 September 2026 – 6 September 2026 · confirmed gone 28 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@zgsyio named in 1 post, 4 September 2026 – 4 September 2026 · confirmed gone 15 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@ffiff12 named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 4 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@marhar2922 named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 5 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@fant_dev_e_liq named in 1 post, 17 September 2026 – 17 September 2026
@exvrx named in 1 post, 2 September 2026 – 2 September 2026
@avav162171 named in 1 post, 8 August 2026 – 8 August 2026
Channels Telegram recommends alongside this one
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.
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.
𓏺 M!𝖷 𝖠𝗅𝗂 . @PWUUU · 27,475 Telegram ranks this channel #1 of 33 here — alongside 32 others — read 9 September 2026
ᗩՏᛕˡᵒⁿᵉʳ.❗🤍 @db245 · 30,274 Telegram ranks this channel #1 of 72 here — alongside 71 others — read 6 September 2026
عبارات، اقتباسات، خواطر @nnsxs · 36,774 Telegram ranks this channel #1 of 58 here — alongside 57 others — read 31 August 2026
هَلْوَسْةّ ¾ @xMvMx · 40,270 Telegram ranks this channel #1 of 62 here — alongside 61 others — read 29 August 2026
آيات قرآنيه احاديث اذكار ادعيه @CC_O5 · 64,882 Telegram ranks this channel #1 of 59 here — alongside 58 others — read 21 August 2026
عريان السيد خلف عبارات اقتباسات @areain_al · 81,148 Telegram ranks this channel #1 of 86 here — alongside 85 others — read 18 August 2026
اقتباسات @mmmsc · 108,359 Telegram ranks this channel #1 of 46 here — alongside 45 others — read 18 August 2026
سَيَستَجيب @mqmq1x · 81,684 Telegram ranks this channel #1 of 61 here — alongside 60 others — read 18 August 2026
- عَلي @FCB10Le · 106,493 Telegram ranks this channel #1 of 68 here — alongside 67 others — read 14 August 2026
حُـب . @op_35 · 294,443 Telegram ranks this channel #1 of 77 here — alongside 76 others — read 10 August 2026
- أبيات عبارات فصحىَ @nnKnn · 1,206,754 Telegram ranks this channel #1 of 57 here — alongside 56 others — read 8 August 2026
اقتباسات ستوريات مَشـَاعر • @YYYYD · 1,641,535 Telegram ranks this channel #1 of 57 here — alongside 56 others — read 8 August 2026
افتارات اغاني كروبات عاشكها @PPPPJ · 2,315,112 Telegram ranks this channel #1 of 59 here — alongside 58 others — read 8 August 2026
اقتباسات عبارات ستوريات حب زخرفه كروبات @TT_BNW · 54,401 Telegram ranks this channel #2 of 48 here — alongside 47 others — read 23 August 2026
نجوم ✨ @starsZE · 125,177 Telegram ranks this channel #2 of 64 here — alongside 63 others — read 15 August 2026
اقتباسات ، عبارات حب ، خواطر حزينه ، خلفيات @zt_d6 · 111,569 Telegram ranks this channel #2 of 75 here — alongside 74 others — read 14 August 2026
اخبار طلاب العراق @FN_73 · 150,226 Telegram ranks this channel #2 of 69 here — alongside 68 others — read 12 August 2026
إقتباسات مترجمة @HH_H7S · 266,544 Telegram ranks this channel #2 of 70 here — alongside 69 others — read 10 August 2026
قرآن ادعيه دينيه دعاء ،🕌 @zzzxx8 · 327,744 Telegram ranks this channel #2 of 84 here — alongside 83 others — read 10 August 2026
اغاني صور افتارات بنات . @NNNZN · 1,383,509 Telegram ranks this channel #2 of 49 here — alongside 48 others — read 8 August 2026
- كتابات دوستويفسكي ، اقتباسات حب ، خواطر . @zrzzzz · 1,393,414 Telegram ranks this channel #2 of 56 here — alongside 55 others — read 8 August 2026
اقتباسات حب ، عبارات حزينه ، ستوريات 🖤 . @zzzzzz · 2,012,583 Telegram ranks this channel #2 of 52 here — alongside 51 others — read 8 August 2026
ثالث عيَوني @TSS4X · 38,795 Telegram ranks this channel #3 of 67 here — alongside 66 others — read 31 August 2026
عريان السيد خلف @ST_SSSSSSSS · 54,797 Telegram ranks this channel #3 of 78 here — alongside 77 others — read 23 August 2026
This channel appears in 353 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.
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 24 October 2026 — this
entry's latest reading, not the date you are reading this.
“اقتباسات عبارات ستوريات 0:0” (@PPPJP), 3,183,684 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/PPPJP.
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.
