Telegram RegisterThe public register of Telegram
Telegram profile photo for Payment Proofs

Channel

Payment Proofs

@rewardpayz

On this record: Topic · Observations · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

1,963subscribers

-38 since we began measuring on 3 September 2026

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

Register entry

Telegram ID-1002084176105
TypeChannel
Username@rewardpayz
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live18 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/rewardpayz

Topic

Marketing & affiliate — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 below this size band

6.8 average views per post against 1,963 subscribers — an engagement rate of 0.346%. Across the 7,569 registered channels in the same cohort — 1,000–3,161 subscribers — the middle half sit between 6.18% and 26.7%, with a median of 13.4%.

What this was computed from
Window30 days (23 August 2026 22 September 2026)
Posts measured20 of 20 published in the window (20 exact, 0 rounded by Telegram)
Views totalled136
Mature posts only0.346% over 20 posts read at least 24h after publication
Subscribers1,963 measured 18 September 2026
Cohortb1000 · 7,569 channels · p10 2.77% · p25 6.18% · p50 13.4% · p75 26.7% · p90 47.7%
Position in cohort0.793th percentile · 1/38 the cohort median
Uncertainty±0.147% of the figure, from Telegram’s rounding

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 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.

Growth

1,9632,0011,9823 September 2026 — 2,001 subscribers3 September 2026 — 2,001 subscribers4 September 2026 — 1,996 subscribers10 September 2026 — 1,983 subscribers14 September 2026 — 1,976 subscribers18 September 2026 — 1,963 subscribers3 September 202618 September 2026
6 measurements spanning 15 days, net -38. 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,957–2,007 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 23:411,963-13
14 Sept 2026, 05:201,976-7
10 Sept 2026, 09:551,983-13
4 Sept 2026, 20:581,996-5
3 Sept 2026, 19:222,001no change
3 Sept 2026, 18:472,001first reading

Engagement

20 posts held, back to 23 August 2026the 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.346%
avg views ÷ 1,963 subscribers
Avg views / post
6.8
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
WindowRolling 30 days · latest post in window 2 September 2026
Posts held20 (23 August 20262 September 2026)
Views total136
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 19:22 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.

Recent posts

2 Sept 2026, 01:39 UTC4 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @Lxjahainger 🧾 TXID: https://bscscan.com/tx/0xd96931dcc536f1443b37ebc3e412e1d471e82a003f0cc347d4b7cec13791792b 🚀 Join @paypertasks and start earning today!

1 Sept 2026, 22:41 UTC5 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @Dreamer111222333 🧾 TXID: https://bscscan.com/tx/0x38703234b207bf63a2b110331e20ca3113d588a8b0d7ea8bee1606108928b733 🚀 Join @paypertasks and start earning today!

1 Sept 2026, 22:23 UTC5 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @Muslinkz 🧾 TXID: https://bscscan.com/tx/0x645c72391b2ce82e66a6553fad285de819215b420d43552d44c0f69230d399bc 🚀 Join @paypertasks and start earning today!

1 Sept 2026, 09:36 UTC6 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @Lxjahainger 🧾 TXID: https://bscscan.com/tx/0xd46f1ddb97384b40a1a772ffefdb9ee8a6456405996a83d1b4937da9025bc6e7 🚀 Join @paypertasks and start earning today!

31 Aug 2026, 20:34 UTC6 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @tradersam04 🧾 TXID: https://bscscan.com/tx/0xd948cef958a58ec78fb99b766340a480724f8e9aca3848af53c01fe70c932c8d 🚀 Join @paypertasks and start earning today!

31 Aug 2026, 20:16 UTC5 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @Frlimited 🧾 TXID: https://bscscan.com/tx/0x05eb7f9dec30bb5104349d1eab20fe21cbddd367b9628eb35ad3f25934f3cff4 🚀 Join @paypertasks and start earning today!

31 Aug 2026, 19:42 UTC5 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @User 🧾 TXID: https://bscscan.com/tx/0x8787407dde10b159801b2147421c73d8d659e9f63108a13b3e43b71cc0a0428d 🚀 Join @paypertasks and start earning today!

31 Aug 2026, 07:54 UTC7 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @User 🧾 TXID: https://bscscan.com/tx/0x533aac05ed2809948033c2e573dc50684ea61295be5425adca53d3079f11cb4e 🚀 Join @paypertasks and start earning today!

31 Aug 2026, 05:32 UTC7 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @Frlimited 🧾 TXID: https://bscscan.com/tx/0x05b58bcb0e4df3a520ba41f40fb048bb8436eb88cbd1ed7fafdd9950dbda077f 🚀 Join @paypertasks and start earning today!

30 Aug 2026, 18:13 UTC6 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @Frlimited 🧾 TXID: https://bscscan.com/tx/0x7ba97447bc3af1e6b4656a3a2075629bcb789cfb11bac0f771f72aeaac9056bc 🚀 Join @paypertasks and start earning today!

29 Aug 2026, 21:07 UTC7 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @User 🧾 TXID: https://bscscan.com/tx/0x60e831288874396d11d7c686805c3061bb47aead2323b482ee80841c760f008e 🚀 Join @paypertasks and start earning today!

29 Aug 2026, 17:57 UTC7 viewsread 3 September 2026

✅ Withdrawal Successfully Paid! 👤 User: @Frlimited 🧾 TXID: https://bscscan.com/tx/0xcca3d3e9cd9b3b4eb1c219a8c41514a84fe76d49db683c16b9c9446892311914 🚀 Join @paypertasks and start earning today!

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

Mentions

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.

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.

DERRO AIRDROPS 1
@Derrochannel1 · 31,089
Telegram ranks this channel #17 of 33 here — alongside 32 others — read 3 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Payment Proofs” (@rewardpayz), 1,963 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/rewardpayz.

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.