To: bc1qkx0znuznt7drrw9n4dna7klnp5zh4ua34k7mgv Amount: 0.001002 BTC ~ 1002 💎 36e8957977effdcb4c25735fd91dce4d273d7b83420f31bfdae93232d2fd4a54

Channel
Robot Automatic🃏- Pays
@proof_with_robot_s_pays
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
7,636subscribers
-185 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001342286698 |
|---|---|
| Type | Channel |
| Username | @proof_with_robot_s_pays |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/proof_with_robot_s_pays |
Topic
Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 04:57 | 7,636 | -15 |
| 14 Sept 2026, 05:55 | 7,651 | -7 |
| 10 Sept 2026, 12:16 | 7,658 | -24 |
| 5 Sept 2026, 15:17 | 7,682 | -23 |
| 1 Sept 2026, 10:57 | 7,705 | -9 |
| 29 Aug 2026, 04:05 | 7,714 | -9 |
| 26 Aug 2026, 12:32 | 7,723 | -28 |
| 23 Aug 2026, 08:02 | 7,751 | -19 |
| 19 Aug 2026, 17:35 | 7,770 | +5 |
| 16 Aug 2026, 08:18 | 7,765 | -1 |
| 13 Aug 2026, 04:57 | 7,766 | -31 |
| 10 Aug 2026, 11:33 | 7,797 | -26 |
| 7 Aug 2026, 12:58 | 7,823 | +2 |
| 7 Aug 2026, 06:00 | 7,821 | no change |
| 7 Aug 2026, 05:59 | 7,821 | first reading |
Engagement
237 posts held, back to 6 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 18 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.242%
- avg views ÷ 7,636 subscribers
- Avg views / post
- 18.4
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 237 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.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 237 (6 August 2026 – 28 August 2026) |
| Views total | 369 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 20:47 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
To: bc1qygv9feyc854xwzs3yqlzuj39azyft8ksy6hrzx Amount: 0.001081 BTC ~ 1081 💎 49116ece86c17fe85cf453cce211927913c5754aea466880d3fa7c14bba8ceca
To: bc1q0uvg5hgcx29mau8k5ee84mjndek4hcn6t2faqe Amount: 0.00147 BTC ~ 1470 💎 dfade7eadb6ad3b924a78a5669c9d54af82769c45768a68e2fa8b5ec283665a3
To: bc1q8atqwrfj5rs3wz8psdnuu53eecsrdgk5m5ergfh3sfj280w7pp5sqlejc8 Amount: 0.001946 BTC ~ 1946 💎 07ecc6bbda65879ea1b458c007d100ded8ee88d25e34f0b6c0ed811c76f87c54
To: bc1q5mdc4rp6p8e6mdav6jdcxq75pygdydyyfkwlsg Amount: 0.0013 BTC ~ 1300 💎 8edb63bbfba8b002ab104f7359b393663da4fa75f825679258a64bbacec29fb5
To: bc1q4ehw86f6ed7xhyqtg06w7qa06ccj0mwzryz420 Amount: 0.002987 BTC ~ 2987 💎 460eba73e101fa70306c7923716ae1263da32f47908cd50da35b5df4a35a5f86
To: bc1qsfan09q79epf8p8ygtczuv88kzczzpzlcel9xe Amount: 0.001249 BTC ~ 1249 💎 0854330c115793827a9620a606b6d9b2738851af7086fab4a4c6ea86b5b7d742
To: bc1qaxpr02xtnm98gxysutldpyhg2lm99lwn6wwp5x Amount: 0.001463 BTC ~ 1463 💎 10a8939735329d7b0c677f068e90285adaee142e6819efdd46491c532787e4ce
To: bc1qhwlrxchlyq0dzmtqsdstc75cpj0vk3shvhztq7 Amount: 0.001359 BTC ~ 1359 💎 de5272e028ff1fcedfc23591dd7034480c5cb4cdb851c5217adb29c9dbf67ae1
To: bc1qsm2z8k4va3u4hx2jen2scpndcmtwl3f48qzhtw Amount: 0.0011 BTC ~ 1100 💎 884927468fa946096dd727ca03288a66920a50a4902b9a0bd52153980fd88c11
To: bc1qhlrtdv95szx63ls89e6aq6ls9wdmdq4dg700el Amount: 0.002 BTC ~ 2000 💎 454437a3496801abbea0d339f7d8b9a8f4ffc159e2980a06cf07fdec124b9276
To: bc1q7qhjv7gveepu4mk333ha2r98tmrsaaztpy5mew Amount: 0.0018 BTC ~ 1800 💎 badb410505365c0941497009907e1449c14f08ee89133d1bb8ba01209dee7cfc
Showing the 12 most recent of 237 posts we hold for @proof_with_robot_s_pays. 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.
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.
@earnbtcbywatchingads · 38,215
Telegram ranks this channel #8 of 35 here — alongside 34 others — read 30 August 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.
“Robot Automatic🃏- Pays” (@proof_with_robot_s_pays), 7,636 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/proof_with_robot_s_pays.
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.