Telegram RegisterThe public register of Telegram
Telegram profile photo for Payment proof 🧾

Channel

Payment proof 🧾

@payment_binancet

On this record: Topic Β· Growth Β· Engagement Β· Reactions Β· Posts Β· Posts edited after publishing Β· Citations Β· Cite this entry

66,242subscribers

+1,308 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1004383057968
TypeChannel
Username@payment_binancet
DescriptionWe strictly adhere to all Telegram Terms of Service and Anti-Spam policies
CreatedBetween 1 June 2026 and 2 August 2026 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/payment_binancet

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

64,93469,17467,0547 August 2026 β€” 64,934 subscribers7 August 2026 β€” 64,934 subscribers8 August 2026 β€” 65,028 subscribers9 August 2026 β€” 65,461 subscribers10 August 2026 β€” 65,569 subscribers11 August 2026 β€” 65,902 subscribers12 August 2026 β€” 66,266 subscribers13 August 2026 β€” 66,447 subscribers15 August 2026 β€” 67,119 subscribers16 August 2026 β€” 66,843 subscribers17 August 2026 β€” 66,760 subscribers18 August 2026 β€” 67,023 subscribers19 August 2026 β€” 66,824 subscribers20 August 2026 β€” 66,757 subscribers21 August 2026 β€” 66,638 subscribers23 August 2026 β€” 65,797 subscribers24 August 2026 β€” 65,413 subscribers25 August 2026 β€” 65,482 subscribers26 August 2026 β€” 66,400 subscribers27 August 2026 β€” 67,394 subscribers28 August 2026 β€” 68,065 subscribers29 August 2026 β€” 68,283 subscribers30 August 2026 β€” 68,860 subscribers31 August 2026 β€” 69,174 subscribers1 September 2026 β€” 69,099 subscribers2 September 2026 β€” 69,161 subscribers4 September 2026 β€” 68,794 subscribers6 September 2026 β€” 68,230 subscribers9 September 2026 β€” 67,545 subscribers11 September 2026 β€” 67,180 subscribers13 September 2026 β€” 66,875 subscribers15 September 2026 β€” 66,685 subscribers17 September 2026 β€” 66,242 subscribers66,2427 August 202617 September 2026
33 measurements spanning 41 days, net +1,308. 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 64,298–69,810 and does not start at zero.
Measurement log β€” every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
17 Sept 2026, 12:1866,242-443
15 Sept 2026, 12:2066,685-190
13 Sept 2026, 20:3666,875-305
11 Sept 2026, 23:5767,180-365
9 Sept 2026, 12:5867,545-685
6 Sept 2026, 05:2068,230-564
4 Sept 2026, 00:3768,794-367
2 Sept 2026, 13:2369,161+62
1 Sept 2026, 15:1269,099-75
31 Aug 2026, 18:1369,174+314
30 Aug 2026, 19:2368,860+577
29 Aug 2026, 19:5468,283+218
28 Aug 2026, 16:3368,065+671
27 Aug 2026, 17:5967,394+994
26 Aug 2026, 15:3266,400+918
25 Aug 2026, 16:4265,482+69
24 Aug 2026, 15:4765,413-384
23 Aug 2026, 00:1565,797-841
21 Aug 2026, 11:3366,638-119
20 Aug 2026, 13:3566,757first reading

Engagement

1,361 posts held, back to 2 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 96 pages of Telegram’s post history, 20 posts per page.

ERR Β· 30 days
0.242%
avg views Γ· 66,242 subscribers
Avg views / post
160
1,035 posts measured
Reaction rate
0.592%
reactions Γ· views Β· ER floor
Posts in window
1,035
of 1,361 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. It is computed over the 166 of 1,035 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days Β· latest post in window 21 September 2026
Posts held1,361 (2 August 2026 – 21 September 2026)
Views total166,065
Reactions total194
Forwards / commentsnot exposed by the public surface β€” not measured, not estimated
Readings taken23 Sept 2026, 01:57 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.

Reaction mix

193 reactions across 149 posts, in 6 distinct kinds. The most used accounts for 78.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❀15278.8%
πŸ”₯147.25%
🀩136.74%
πŸ‘84.15%
πŸ˜‡42.07%
πŸŽ‰21.04%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities β€” πŸ™ is thanks in one channel and mourning in another β€” so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one β€” 4.34K, 1.2M β€” so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 165 of the 1,000 sampled posts in this sample. Summed by Telegram’s own count on each post β€” not by adding up the per-emoji breakdown above β€” those same posts carry 193 reactions in total: the kind of figure the paragraph above means by β€œa reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 24 August 2026 to 21 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

21 Sept 2026, 12:13 UTC513 views3 reactionsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 1796237728 πŸ’° Total Requested: 24.00 USDT βœ… Net Amount Credited: 24.00 USDT πŸ’³ Wallet Address: 0x00e70C78fd2bEEF40a664f3271715FE8E65c33Ff πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

❀3

21 Sept 2026, 11:05 UTC553 views4 reactionsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 7116353985 πŸ’° Total Requested: 10.00 USDT βœ… Net Amount Credited: 10.00 USDT πŸ’³ Wallet Address: 0x492fF94ab519Eb523b30eAAD183ef3dAA7b1d79C πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

❀3πŸ‘1

21 Sept 2026, 09:45 UTC554 views1 reactionsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 7885738739 πŸ’° Total Requested: 10.15 USDT βœ… Net Amount Credited: 10.15 USDT πŸ’³ Wallet Address: 0xd4119A28FCFD49CB84710d7538207509f9bC8A30 πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

❀1

21 Sept 2026, 09:19 UTC523 views2 reactionsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 7942430181 πŸ’° Total Requested: 11.00 USDT βœ… Net Amount Credited: 11.00 USDT πŸ’³ Wallet Address: 0xeaC2d69FeCB5A1e20F4ab10E0c4eADb114fa51cA πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

❀2

21 Sept 2026, 09:07 UTC506 views1 reactionsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 7094756832 πŸ’° Total Requested: 10.00 USDT βœ… Net Amount Credited: 10.00 USDT πŸ’³ Wallet Address: 0x1C272b352551c7d37c4383ef310c081AE7668010 πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

❀1

21 Sept 2026, 08:08 UTC443 views1 reactionsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 7109298220 πŸ’° Total Requested: 10.00 USDT βœ… Net Amount Credited: 10.00 USDT πŸ’³ Wallet Address: 0x0bEb2c3e6e045c953c9B9d3f0e8B42a8fC16F710 πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

❀1

21 Sept 2026, 07:59 UTC331 views1 reactionsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 7109298220 πŸ’° Total Requested: 10.00 USDT βœ… Net Amount Credited: 10.00 USDT πŸ’³ Wallet Address: 0x0bEb2c3e6e045c953c9B9d3f0e8B42a8fC16F710 πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

❀1

21 Sept 2026, 06:43 UTC263 views1 reactionsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 6381050647 πŸ’° Total Requested: 11.00 USDT βœ… Net Amount Credited: 11.00 USDT πŸ’³ Wallet Address: 0x0aF36ea17fDf3f2D5cAf27Aa2B8A47D2ebF68A96 πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

❀1

21 Sept 2026, 05:25 UTC261 viewsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 5975388735 πŸ’° Total Requested: 10.00 USDT βœ… Net Amount Credited: 10.00 USDT πŸ’³ Wallet Address: 0x0803E6fe34a3b464e52039916aa611686E61435d πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

21 Sept 2026, 04:50 UTC252 viewsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 8509573771 πŸ’° Total Requested: 10.00 USDT βœ… Net Amount Credited: 10.00 USDT πŸ’³ Wallet Address: 0xb76C9d92e44c904a5FE41dd55415B5AfFb9F08Ce πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

21 Sept 2026, 00:53 UTC281 viewsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 8857966597 πŸ’° Total Requested: 10.00 USDT βœ… Net Amount Credited: 10.00 USDT πŸ’³ Wallet Address: 0x9B6DDd49b68ac10383633a442EfbC5c954C7be18 πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

21 Sept 2026, 00:02 UTC287 viewsread 23 September 2026

πŸš€ NEW SUCCESSFUL WITHDRAWAL πŸš€ πŸ‘€ User: ID: 7567360508 πŸ’° Total Requested: 11.00 USDT βœ… Net Amount Credited: 11.00 USDT πŸ’³ Wallet Address: 0xD7711Ae360bd5Dc3bf381afB26cbaFC5Efae64b1 πŸ€– Bot: @Riward_Box_bot πŸ›‘ Status: 100% Verified & Paid

Showing the 12 most recent of 1,361 posts we hold for @payment_binancet. 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

@payment_binancet edited 1 post 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
14 August 2026
Most recent edit
14 August 2026

Mentions

Named by 1 registered channel β€” 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.

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.

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.

β€œPayment proof πŸ§Ύβ€ (@payment_binancet), 66,242 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/payment_binancet.

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.