Telegram RegisterThe public register of Telegram
Telegram profile photo for 📤 Payments - Claim BIT Today ⚒

Channel

📤 Payments - Claim BIT Today ⚒

@payments_claim_bit_today

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

1,510subscribers

-23 since we began measuring on 30 August 2026

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

Register entry

Telegram ID-1001785744365
TypeChannel
Username@payments_claim_bit_today
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/payments_claim_bit_today

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 17 September 2026 and assigned it the closest of 31 fixed categories, at 32% 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

5.5 average views per post against 1,510 subscribers — an engagement rate of 0.364%. Across the 5,984 registered channels in the same cohort — 1,000–3,162 subscribers — the middle half sit between 6.01% and 26.4%, with a median of 13.2%.

What this was computed from
Window30 days (26 August 2026 – 25 September 2026)
Posts measured20 of 20 published in the window (20 exact, 0 rounded by Telegram)
Views totalled110
Mature posts only0.427% over 11 posts read at least 24h after publication
Subscribers1,510 measured 17 September 2026
Cohortb1000 · 5,984 channels · p10 2.69% · p25 6.01% · p50 13.2% · p75 26.4% · p90 46.3%
Position in cohort0.886th percentile · 1/36 the cohort median
Uncertainty±0.191% 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 25 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,5101,5331,521.530 August 2026 — 1,533 subscribers30 August 2026 — 1,533 subscribers3 September 2026 — 1,532 subscribers9 September 2026 — 1,524 subscribers13 September 2026 — 1,518 subscribers17 September 2026 — 1,510 subscribers30 August 202617 September 2026
6 measurements spanning 18 days, net -23. 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,507–1,536 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 19:161,510-8
13 Sept 2026, 13:561,518-6
9 Sept 2026, 08:151,524-8
3 Sept 2026, 19:201,532-1
30 Aug 2026, 22:001,533no change
30 Aug 2026, 21:451,533first reading

Engagement

20 posts held, back to 28 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.364%
avg views ÷ 1,510 subscribers
Avg views / post
5.5
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 30 August 2026
Posts held20 (28 August 2026 – 30 August 2026)
Views total110
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 22:00 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

30 Aug 2026, 19:43 UTC2 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1ql5ujnapx5dfphfy5speujrjukq7vl4s33xxkre ▪ Amount: 0.00102 Bitcoin ~ 510000 🧧 50bbc38177b77b0f6e480f43ecfabf8fd66094e6020f7273a27e3b9a5e15d7b0

30 Aug 2026, 19:32 UTC2 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1qklf8xqgwyg24z27lrcvmhd3yhesg0wslg5sr7s ▪ Amount: 0.001902 Bitcoin ~ 951000 🧧 27c9f3af7c5887808a2ef9e80e37c4ab077f81fdb974b82fb9b3dafaf258969a

30 Aug 2026, 18:26 UTC2 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1q03hwuclcn8rtukh3efk5j8veczzh93rr4j707r ▪ Amount: 0.0014 Bitcoin ~ 700000 🧧 46c3aeab0511a8a15ad6fb3b15210899c85fb850e7d71fc81aa04c835402f79c

30 Aug 2026, 14:55 UTC4 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1qm6q7cu427ee0waxspca5u248prfe5lcduktame ▪ Amount: 0.002176 Bitcoin ~ 1088000 🧧 5ffa4662fbebbddd1d71047c90791fefa448b0cc0c5af28ccce1382643a1e278

30 Aug 2026, 10:34 UTC5 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1qums0yuqpx850wklesjxlyv8r98ksh6q2l7h3n2 ▪ Amount: 0.002599 Bitcoin ~ 1299500 🧧 d1e3675b767324b369812dd8c22df832999bb7d395285f1359a9d97e45e80f06

30 Aug 2026, 06:59 UTC6 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1qxunu7pnamna9f3ll09ltzhkqcgrnsc6u3mgl2m ▪ Amount: 0.00102 Bitcoin ~ 510000 🧧 74295e6d37d57ca5db184253116773af1999c8d278ab88fbce4b96b90a1c9a9b

30 Aug 2026, 05:22 UTC6 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1q2jja45wvc6luyvg3uhx07u07r0nftjzlfeapaj ▪ Amount: 0.001732 Bitcoin ~ 866000 🧧 59e89ed5316222b67cb6ea1e5a054d209b972a44deb7a99e96938ee356c08e20

30 Aug 2026, 02:49 UTC6 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1q6hgjau8pwt0z53zzyytd42helk76q8ttknwc7r ▪ Amount: 0.001281 Bitcoin ~ 640500 🧧 984a1c8a3dee6d8ebb7c8d44f623249a6979d6b515b999c78747c53c563ecd28

29 Aug 2026, 22:11 UTC6 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1qlccs4hzf5j8e6hq7wv7x62ew7ykrwwz5plxydkm20pr4cmqxtgdqdu5zwx ▪ Amount: 0.001404 Bitcoin ~ 702000 🧧 a545d178ecfa062cd45ca07e14e14503df29bf869e43847449c81d50965dd862

29 Aug 2026, 20:05 UTC5 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1q6smpacnutdqddj47lykxryeh23xf7rgscua2s7 ▪ Amount: 0.00101 Bitcoin ~ 505000 🧧 192f53212b1b8d1130332dfaf7044afd1a967e1206781a474b9bf4a9441999b8

29 Aug 2026, 17:47 UTC5 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1qtmndxqxz9yxw9gfxpj5j9h6h7yjdgm65u70a07 ▪ Amount: 0.001978 Bitcoin ~ 989000 🧧 c81b1e0a7f34253db553c5ea17898c90b9c08fb51d56f48b4ea9aaf1394dbb1b

29 Aug 2026, 13:07 UTC6 viewsread 30 August 2026

🎊 Successful withdrawal 🎊 ▪ To: bc1qe6xa7t275wdazgyscev99n3t9a46lr5akqxvjx ▪ Amount: 0.00195 Bitcoin ~ 975000 🧧 0889cfd5e39b9d29fa417f1612e2f671a78dee85e215a9022db2fdef0db91971

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

Payment - BTC ads
@earnbtcbywatchingads · 38,215
Telegram ranks this channel #9 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“📤 Payments - Claim BIT Today ⚒” (@payments_claim_bit_today), 1,510 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/payments_claim_bit_today.

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.