Telegram RegisterThe public register of Telegram
Telegram profile photo for Payments - Free Bitcoin Daily 🎁

Channel

Payments - Free Bitcoin Daily 🎁

@pays_get_free_bitcon

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

7,123subscribers

-375 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-1001746347645
TypeChannel
Username@pays_get_free_bitcon
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/pays_get_free_bitcon

Topic

Marketing & affiliate — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 38% 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.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@pays_get_free_bitcon/20514 · this entry7 Aug 2026, 02:44 UTC@Bxitcoin/30247 Aug 2026, 18:12 UTC1.0015 hours
@pays_get_free_bitcon/20516 · this entry7 Aug 2026, 03:37 UTC@Bxitcoin/30267 Aug 2026, 18:12 UTC1.0015 hours
@pays_get_free_bitcon/20517 · this entry7 Aug 2026, 09:35 UTC@Bxitcoin/30277 Aug 2026, 18:12 UTC1.008.6 hours
@pays_get_free_bitcon/20518 · this entry7 Aug 2026, 14:12 UTC@Bxitcoin/30287 Aug 2026, 18:12 UTC1.004.0 hours
@pays_get_free_bitcon/20519 · this entry7 Aug 2026, 14:58 UTC@Bxitcoin/30297 Aug 2026, 18:12 UTC1.003.2 hours
@pays_get_free_bitcon/20520 · this entry7 Aug 2026, 17:09 UTC@Bxitcoin/30307 Aug 2026, 18:12 UTC1.0064 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Bxitcoin9 (8/8 hand-verifiable sample passed)1.004.0 hoursthis entry (90)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 25 comparable posts for this entry, running 5 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @proof_get_free_bitcoin. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

7,1237,4987,310.57 August 2026 — 7,498 subscribers7 August 2026 — 7,498 subscribers7 August 2026 — 7,497 subscribers10 August 2026 — 7,473 subscribers14 August 2026 — 7,432 subscribers17 August 2026 — 7,410 subscribers20 August 2026 — 7,388 subscribers24 August 2026 — 7,352 subscribers26 August 2026 — 7,328 subscribers29 August 2026 — 7,301 subscribers1 September 2026 — 7,270 subscribers5 September 2026 — 7,231 subscribers10 September 2026 — 7,186 subscribers14 September 2026 — 7,161 subscribers18 September 2026 — 7,123 subscribers7 August 202618 September 2026
15 measurements spanning 42 days, net -375. 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 7,067–7,554 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 23:177,123-38
14 Sept 2026, 09:397,161-25
10 Sept 2026, 18:197,186-45
5 Sept 2026, 16:187,231-39
1 Sept 2026, 13:127,270-31
29 Aug 2026, 23:087,301-27
26 Aug 2026, 18:557,328-24
24 Aug 2026, 01:567,352-36
20 Aug 2026, 14:047,388-22
17 Aug 2026, 16:177,410-22
14 Aug 2026, 10:087,432-41
10 Aug 2026, 23:217,473-24
7 Aug 2026, 19:317,497-1
7 Aug 2026, 13:467,498no change
7 Aug 2026, 13:357,498first reading

Engagement

119 posts held, back to 5 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 13 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 119 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 Aug 2026, 11:18 UTC1 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: bc1qxr403r9ag6yfc6laxxrtvrm7845pygk3kj0vgj 🔹 Amount withdrawn: 0.001437 BTC 🌐 Transaction ID: 122a480a421d0347ac005b5da8a3ba4edbe1af2fbec02d37ed1fe5381b8b5472

20 Aug 2026, 11:15 UTC1 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: bc1qt597h6zrpalshtsxg4yvf6mmrkjkfww0hk4gqk 🔹 Amount withdrawn: 0.002991 BTC 🌐 Transaction ID: 644be1f055129a764002aacce4d53f308277429c5f961e9146772244066650d6

20 Aug 2026, 06:31 UTC8 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: 1Fw8LLB3vo2D3hKMB7UCJKusv6yHTZxg4N 🔹 Amount withdrawn: 0.00132 BTC 🌐 Transaction ID: ddfa2803173ed7fd07af4f04eeed51e2ea0b285e1b2f2e31343b976fe59abb0c

19 Aug 2026, 19:41 UTC23 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: bc1ql28z2dk8eu48hdzjjkvvw0qnjpqg75snzum2lf 🔹 Amount withdrawn: 0.0011 BTC 🌐 Transaction ID: 6f9823ff04a816a71269fd8d3a54b58284914b693f94ca8ed7372e515febf541

19 Aug 2026, 18:37 UTC23 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: bc1qxxh6htsjldwlllhfxdt7aj7j5k5tszgt77yx0k 🔹 Amount withdrawn: 0.001394 BTC 🌐 Transaction ID: 1de173294765c6bedfb0398c2893e353cc2d222587fc7ab84e71d088fa578d6e

19 Aug 2026, 18:05 UTC21 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: bc1qnmakv2qv0ty7utetflra36uxmn8eacy30tp58k 🔹 Amount withdrawn: 0.002142 BTC 🌐 Transaction ID: 788fb40a2961022b4070810f9b9269a5d17110f20eff1ce7f339ec13b277ef76

19 Aug 2026, 17:10 UTC21 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: bc1qymlnlglv5g8qma5nnuy7vrluwxn7vwyqskmswh 🔹 Amount withdrawn: 0.001731 BTC 🌐 Transaction ID: 90b0d520a189f036b55e5b3e96d04a60a306f73f012522f76550484255e61c59

19 Aug 2026, 13:35 UTC23 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: bc1q07lvrffze3lx6fw0wpkuxzv6hga0l96rw9506w 🔹 Amount withdrawn: 0.00108 BTC 🌐 Transaction ID: 35642607c1fcdf35004c66b3d3356b06a7c6a86a1f0a073e9c373258be8a281e

19 Aug 2026, 12:52 UTC20 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: bc1qftljxz6vu6wv92aev6wehfv6dhch2skq4d7rr8 🔹 Amount withdrawn: 0.002 BTC 🌐 Transaction ID: 6dbc9c53ff08be516a77b435d31cc825b4f59607f29622ae424465acfb6de431

19 Aug 2026, 12:50 UTC17 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: 1FDXxvxXSQ3C5yiGYuq9XSjWM8gTbbvhzn 🔹 Amount withdrawn: 0.002076 BTC 🌐 Transaction ID: f50a8493f761fcd5bd3e9a39a25df41e383b26ec3e25d51bae1aab4a67bd20ee

19 Aug 2026, 12:09 UTC16 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: 1LGxcJHWLr4wtDbKhMxfgYQSireGMUaTtd 🔹 Amount withdrawn: 0.002102 BTC 🌐 Transaction ID: 3f2e91b0583feb3304f6d33d7fdadb6b647f4c5d37c467dba77d2648fc1b1a94

19 Aug 2026, 07:41 UTC17 viewsread 20 August 2026

💸 New Withdrawal Sent 💸 🔹 To wallet: 1Dq9iLG8yaJe8iqzoWyAimd2LqhJW9u97M 🔹 Amount withdrawn: 0.001679 BTC 🌐 Transaction ID: 4556b097fcd35cc699489daaa977a3b61d8612df592cf957853a47cb43202e42

Showing the 12 most recent of 119 posts we hold for @pays_get_free_bitcon. 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 #4 of 35 here — alongside 34 others — read 30 August 2026
Crypto Musk
@DigibyteAirdropM · 93,100
Telegram ranks this channel #47 of 52 here — alongside 51 others — read 20 August 2026
TronMine News
@tronxomine · 50,443
Telegram ranks this channel #48 of 50 here — alongside 49 others — read 24 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists 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.

“Payments - Free Bitcoin Daily 🎁” (@pays_get_free_bitcon), 7,123 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/pays_get_free_bitcon.

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.