Channel
@WildBitcoin
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
2,349subscribers
-104 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001366536840 |
|---|---|
| Type | Channel |
| Username | @WildBitcoin |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/WildBitcoin |
Crypto & trading — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 09:15 | 2,349 | -17 |
| 16 Sept 2026, 17:40 | 2,366 | -2 |
| 13 Sept 2026, 06:16 | 2,368 | -2 |
| 9 Sept 2026, 18:19 | 2,370 | -6 |
| 4 Sept 2026, 19:36 | 2,376 | -6 |
| 1 Sept 2026, 12:25 | 2,382 | -19 |
| 29 Aug 2026, 01:54 | 2,401 | -8 |
| 26 Aug 2026, 08:48 | 2,409 | -6 |
| 23 Aug 2026, 00:58 | 2,415 | -11 |
| 19 Aug 2026, 12:09 | 2,426 | -7 |
| 16 Aug 2026, 18:38 | 2,433 | -8 |
| 13 Aug 2026, 07:15 | 2,441 | -6 |
| 9 Aug 2026, 20:31 | 2,447 | -6 |
| 6 Aug 2026, 15:52 | 2,453 | no change |
| 6 Aug 2026, 06:48 | 2,453 | first reading |
19 posts held, back to 22 April 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 2 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 19 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Hello everyone, I am urgently looking for a genuine job opportunity that provides a legal work permit or visa sponsorship in any country. I am 34 years old, married, and responsible for five children, some of whom have ongoing medical needs. I have been without stable work for around ten months, and my situation has become extremely difficult. I am not asking for money or charity. I am only asking for a real opport…
BUY Zone Update BTC reached 57.8K a few days ago before rebounding directly toward 64K. Our original buy zone was set between 57K and 53K over a month ago. Since price rebounded before fully filling that range and has now moved higher, I'm adjusting the primary buy zone to 53K–48K. You may consider deploying up to 30% of available fiat within this range, based on your own risk management and investment plan. The …
BTC below $60k you can add Buy range "First Buy limits" Around $57-53K" Do you risk management math. We ask Allah reconcile and repay
JUST IN: Bitcoin is now down 32% this year. $ETH is down 45% this year @WatcherGuru
https://www.tradingview.com/chart/BTCUSD/F49BHbu4-Sell-in-May-and-go-away-Did-it-come-true/
#BTC Following the analysis above, BTC reached the 70K zone after 13 days. In the previous update, I mentioned the possibility of a move toward the 70K–68K range. That scenario has now played out. The next question is simple: Can bulls defend this zone? If 70K–68K is lost easily, then 64K–61K becomes the next area of interest for bears. Weeks ago, I reduced most BTC exposure based on this view, unless BTC was g…
After posting that update, I received many messages from people offering help and support. At first, I decided to let it go, but some reminded me that this was never just about a domain name. It represents years of work, memories, effort, and history built together. Good news and a true blessing during difficult days. The PCS domain and hosting have now been renewed successfully. I truly appreciate everyone who tri…
##HYPE Nearing a Major Trend Shift? for KUCOIN:HYPEUSDT by HamadaMark — TradingView
BTC SHOWS FILLING GAP CHANCES AS CHART ABOVE EXPLAINING.
🌟 VIP ROOM – NEW ERA 🌟 Not a signal group, but a full roadmap for real traders. Focused on TA, FA, mindset, and risk discipline 💼 💰 VIP Pricing (New Era) 🌱 1st Month Trial: $50 (testing month for new members) 📆 3 Months: $350 (for active traders who want to grow) 🗓 1 Year: $1000 (for long discipline and real test) 💎 Loyalty Offer (for old members & followers) 🗓 1 Year: $750 (for long discipline and real test) Onl…
#BTC Bears & Bulls Fight! for BITSTAMP:BTCUSD by HamadaMark — TradingView
https://www.tradingview.com/x/hNn5dzcm/
Showing the 12 most recent of 19 posts we hold for @WildBitcoin. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 3 registered channels — 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.
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.
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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Wild Bitcoin™🇵🇸” (@WildBitcoin), 2,349 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/WildBitcoin.
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.