Channel
@CRYPTO_CARPOOL
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Cite this entry
264subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001391127397 |
|---|---|
| Type | Channel |
| Username | @CRYPTO_CARPOOL |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/CRYPTO_CARPOOL |
Crypto & trading — 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 99% 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.
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.
Posts published here appear word for word on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @CRYPTO_CARPOOL/4368 · this entry6 Dec 2021, 16:05 UTC | @bitcoinwizard1/47216 Dec 2021, 16:05 UTC | 1.00 | under a minute |
| @bitcoinwizard1/47226 Dec 2021, 16:53 UTC | @CRYPTO_CARPOOL/4369 · this entry6 Dec 2021, 16:53 UTC | 1.00 | under a minute |
| @CRYPTO_CARPOOL/4372 · this entry18 Jan 2022, 04:02 UTC | @bitcoinwizard1/472518 Jan 2022, 04:02 UTC | 1.00 | under a minute |
| @bitcoinwizard1/472618 Jan 2022, 12:00 UTC | @CRYPTO_CARPOOL/4373 · this entry18 Jan 2022, 12:00 UTC | 1.00 | under a minute |
| @CRYPTO_CARPOOL/4374 · this entry18 Jan 2022, 15:00 UTC | @bitcoinwizard1/472718 Jan 2022, 15:00 UTC | 1.00 | under a minute |
| @bitcoinwizard1/472818 Jan 2022, 15:31 UTC | @CRYPTO_CARPOOL/4375 · this entry18 Jan 2022, 15:31 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @bitcoinwizard1 | 13 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @bitcoinwizard1 (11–2) |
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 11 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 13 comparable posts for this entry, running 6 December 2021 to 18 January 2022. 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.
Across the whole group of 2, the earliest publisher we hold is @CRYPTO_CARPOOL — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 03:08 | 264 | -3 |
| 7 Aug 2026, 00:32 | 267 | no change |
| 6 Aug 2026, 15:04 | 267 | first reading |
20 posts held, back to 6 December 2021 — 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 pageof 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 20 posts for this entry, the most recent from 18 January 2022. An engagement rate over an empty window would be a number about nothing.
Our coin PIVX can be witnessed in the top gainer list of binance with a whooping 50% spike from the bottom and volume reaching almost 70 BTC. The pump reached sky touching peaks gradually with no prepump or prebuying. An amazing outstanding job done by our giant whales so far🚀✅ We witnessed many people who made amazing profits from PIVX especially those who got in with their entries in the first minute and congratul…
#PIVX🚀✌️
PIVX Top gainer on binance🚀✌️
Why #PIVX is bullish❓ Private instant verified transactions #PIVX is a type of private crypto currency operating since 2016 during initial stage it was one of the top crypto used on darknet as it’s fully private crypto Now after tons of upgrade #PIVX provide instant fully secured private transactions with very less fees also there are tons of upgrades ahead So we can expect atleast a couple’s of X’s from this gem i…
Why #PIVX is a must Buy project ❓ #PIVX is very undervalued gem as it’s having very low Mcap in comparison to there working product For now it is lying on very strong horizontal support on 1D and 1W timeframe so risk of buying here is very low Heavily oversold on higher timeframe big jump is expected anytime from #PIVX
#PIVX Targeting 2200 - 2500 - 3000👍
#PIVX is a like a ticking time bomb here as there are tons of upgrades ahead we can expect massive explosion from this one in a matter of time🚀
#PIVX flight is about to takeoff 🛫 Fasten your seatbelt’s ✌🏻
Recently #BINANCE announced multiple upgrades for #PIVX Also #Swarm campaign going on binance so we can expect big pump in coming days 🚀
#PIVX flight is about to takeoff 🛫 Fasten your seatbelt’s ✌🏻
Powerful TA + FA Based Call #PIVX on Binance https://www.binance.com/en/trade/PIVX_BTC?layout=pro
Powerful TA + FA Based Call #PIVX on Binance https://www.binance.com/en/trade/PIVX_BTC?layout=pro
Showing the 12 most recent of 20 posts we hold for @CRYPTO_CARPOOL. 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“CRYPTO PUMPS” (@CRYPTO_CARPOOL), 264 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/CRYPTO_CARPOOL.
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.