Telegram RegisterThe public register of Telegram
Telegram profile photo for ريكارد

Channel

ريكارد

@Rekard96

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

11,030subscribers

+1,107 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001087346677
TypeChannel
Username@Rekard96
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held28
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/Rekard96

Topic

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 60% 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.

Views per post sit far above this size band

9,820 average views per post against 11,030 subscribers — an engagement rate of 89.0%. Across the 5,268 registered channels in the same cohort — 10,004–31,594 subscribers, posting mainly in Arabic — the middle half sit between 2.42% and 12.9%, with a median of 6.54%.

What this was computed from
Window30 days (10 August 2026 9 September 2026)
Posts measured12 of 12 published in the window (0 exact, 12 rounded by Telegram)
Views totalled117,780
Mature posts only95.7% over 11 posts read at least 24h after publication
Subscribers11,030 measured 7 September 2026
Cohortb10000:ara · 5,268 channels · p10 0.775% · p25 2.42% · p50 6.54% · p75 12.9% · p90 21.8%
Position in cohort99.924th percentile · 13.6× the cohort median
Uncertainty±0.272% of the figure, from Telegram’s rounding
Post languageArabic · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above 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_high, last confirmed 9 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

9,92311,03010,476.56 August 2026 — 9,923 subscribers6 August 2026 — 9,923 subscribers6 August 2026 — 9,962 subscribers9 August 2026 — 10,163 subscribers10 August 2026 — 10,245 subscribers11 August 2026 — 10,316 subscribers12 August 2026 — 10,354 subscribers14 August 2026 — 10,468 subscribers15 August 2026 — 10,502 subscribers16 August 2026 — 10,570 subscribers17 August 2026 — 10,607 subscribers19 August 2026 — 10,647 subscribers19 August 2026 — 10,658 subscribers21 August 2026 — 10,677 subscribers22 August 2026 — 10,711 subscribers24 August 2026 — 10,761 subscribers25 August 2026 — 10,774 subscribers26 August 2026 — 10,802 subscribers27 August 2026 — 10,825 subscribers28 August 2026 — 10,838 subscribers29 August 2026 — 10,859 subscribers29 August 2026 — 10,883 subscribers30 August 2026 — 10,907 subscribers31 August 2026 — 10,919 subscribers1 September 2026 — 10,927 subscribers2 September 2026 — 10,949 subscribers4 September 2026 — 10,987 subscribers7 September 2026 — 11,030 subscribers6 August 20267 September 2026
28 measurements spanning 33 days, net +1,107. 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 9,757–11,196 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
7 Sept 2026, 14:5711,030+43
4 Sept 2026, 15:2210,987+38
2 Sept 2026, 22:5510,949+22
1 Sept 2026, 21:4810,927+8
31 Aug 2026, 21:2610,919+12
30 Aug 2026, 21:2810,907+24
29 Aug 2026, 21:4610,883+24
29 Aug 2026, 00:4810,859+21
28 Aug 2026, 01:4510,838+13
27 Aug 2026, 04:0710,825+23
26 Aug 2026, 05:4810,802+28
25 Aug 2026, 04:4510,774+13
24 Aug 2026, 04:1510,761+50
22 Aug 2026, 13:2810,711+34
21 Aug 2026, 00:5610,677+19
19 Aug 2026, 21:3710,658+11
19 Aug 2026, 00:2210,647+40
17 Aug 2026, 21:1310,607+37
16 Aug 2026, 21:5210,570+68
15 Aug 2026, 15:0410,502first reading

Engagement

33 posts held, back to 26 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 40 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
89.0%
avg views ÷ 11,030 subscribers
Avg views / post
9,820
12 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
12
of 33 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
WindowRolling 30 days · latest post in window 2 September 2026
Posts held33 (26 June 20262 September 2026)
Views total117,780
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 02:32 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.

What this channel posts

Video runtime
8s
Average length
8s

Measured directly from 1 video 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.

Recent posts

2 Sept 2026, 17:58 UTC≈1,670 viewsread 3 September 2026

السلام عليكم راح انطيك قميصي وخصلة من شعري ورقم ام عباس وراح ادليك على المقبرة الي تحط بيهة السحر واذا رجعت حبيتك تعال عاتبني .

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

30 Aug 2026, 13:13 UTC≈4,440 viewsread 3 September 2026

السلام عليكم من اني وصغير ما احب العب غميضه لأن الي يختفي ما ادور عليه فهمت لو اعيدلك ؟

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

26 Aug 2026, 12:54 UTC≈7,670 viewsread 3 September 2026

السلام عليكم مرات لازم تنسحب من الشي الي تريده حتى الشي الي يريدك يلكاك

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

21 Aug 2026, 18:10 UTC≈10,100 viewsread 3 September 2026

السلام عليكم اذا ال wifi صار ثكيل عندك على غفلة فاعرف انه اكو واحد مكنك وجاي يستخدمة وياك

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

18 Aug 2026, 09:34 UTC≈12,300 viewsread 3 September 2026
Photo

السلام عليكم

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

17 Aug 2026, 16:08 UTC≈11,400 viewsread 3 September 2026

هذا حساب التيك توك مال قناة شوفولي اخر منشور ناشرة الاغنية كاعدة ويه الكلام ؟

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

16 Aug 2026, 20:10 UTC≈11,800 viewsread 3 September 2026

السلام عليكم بطل تفتح صفحة جديدة وية ناس تحب تشخبط هواي

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

15 Aug 2026, 16:31 UTC≈11,600 viewsread 3 September 2026
Photo

السلام عليكم

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

12 Aug 2026, 21:02 UTC≈11,900 viewsread 3 September 2026

لم أستطع , ساقاي لم تعودا قادرتين على الاستمرار والان لدي الكثير من الشكوك حول ما اذا كنت سأستمر في فعل ذلك لفترة اطول L.messi 2026-8-12

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

12 Aug 2026, 13:19 UTC≈11,700 viewsread 3 September 2026

هاا حتى لو تحبة وشكلة حلو هم ذبة بالزبالة اوك؟

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

12 Aug 2026, 13:07 UTC≈11,600 viewsread 3 September 2026

السلام عليكم اذا اشتريت حذاء وثاني يوم لبستة وطلع يأذي رجلك ، ذبة بالزبالة حتى لو جان سعرة غالي

Signed 𝚁𝙴𝙺𝙰𝚁𝙳

Showing the 12 most recent of 33 posts we hold for @Rekard96. 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.

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.

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

“ريكارد” (@Rekard96), 11,030 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/Rekard96.

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.