15 Nov 2019, 00:26 UTCviews —
The account of the user that created this channel has been inactive for the last 5 months. If it remains inactive in the next 10 days, that account will self-destruct and this channel will no longer have a creator.
Channel
BTCForest Payments|Forecast
@BTCforest_Payments
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
13subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001193885452 |
|---|---|
| Type | Channel |
| Username | @BTCforest_Payments |
| Created | Between 1 March 2018 and 21 May 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BTCforest_Payments |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 02:17 | 13 | no change |
| 6 Aug 2026, 17:52 | 13 | first reading |
Engagement
20 posts held, back to 21 May 2019 — 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 15 November 2019. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 174
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
5 Nov 2019, 06:52 UTCviews —
The account of the user that created this channel has been inactive for the last 5 months. If it remains inactive in the next 20 days, that account will self-destruct and this channel will no longer have a creator.
26 Oct 2019, 05:31 UTCviews —
The account of the user that created this channel has been inactive for the last 5 months. If it remains inactive in the next 30 days, that account will self-destruct and this channel will no longer have a creator.
22 May 2019, 08:23 UTC952 viewsread 12 August 2026
New Reinvestment Added: User Junior Madmax decided to reinvest his profit of 0.00041400 BTC Forest.
22 May 2019, 04:35 UTC921 viewsread 12 August 2026
New Reinvestment Added: User JEAN Wolmarans decided to reinvest his profit of 0.00252000 BTC Forest.
21 May 2019, 10:43 UTC881 viewsread 12 August 2026
New Investment Added: User Thembisile Mnisi invested 0.00630000 BTC Forest . BTC Forest Transaction ID: https://www.blockchain.com/btc/tx/efa980c92bc38a7d7f7bb9d9a535fe1e6ace02be36f6fbcb859d1eebaf6139f7 🎁 Deposit Bonus: 0.00126
21 May 2019, 10:06 UTC723 viewsread 12 August 2026
New Withdrawal Successfully Sent: User Lediadelorbe withdrawn his bitcoin forest profit amount of 0.00022398 BTC Forest. BTC Forest Transaction ID: https://www.blockchain.com/btc/tx/4a2d4dc3577213032eef26ba4b38ce5112af7bcdeaf71c637c497a9d43cb70ee
21 May 2019, 10:06 UTC549 viewsread 12 August 2026
New Withdrawal Successfully Sent: User JennySolo withdrawn his bitcoin forest profit amount of 0.00071000 BTC Forest. BTC Forest Transaction ID: https://www.blockchain.com/btc/tx/4a2d4dc3577213032eef26ba4b38ce5112af7bcdeaf71c637c497a9d43cb70ee
21 May 2019, 10:06 UTC446 viewsread 12 August 2026
New Withdrawal Successfully Sent: User dave_d withdrawn his bitcoin forest profit amount of 0.00026000 BTC Forest. BTC Forest Transaction ID: https://www.blockchain.com/btc/tx/4a2d4dc3577213032eef26ba4b38ce5112af7bcdeaf71c637c497a9d43cb70ee
21 May 2019, 10:06 UTC376 viewsread 12 August 2026
New Withdrawal Successfully Sent: User Anneesh withdrawn his bitcoin forest profit amount of 0.00026000 BTC Forest. BTC Forest Transaction ID: https://www.blockchain.com/btc/tx/4a2d4dc3577213032eef26ba4b38ce5112af7bcdeaf71c637c497a9d43cb70ee
21 May 2019, 10:06 UTC338 viewsread 12 August 2026
New Withdrawal Successfully Sent: User Mrgray16 withdrawn his bitcoin forest profit amount of 0.00259420 BTC Forest. BTC Forest Transaction ID: https://www.blockchain.com/btc/tx/4a2d4dc3577213032eef26ba4b38ce5112af7bcdeaf71c637c497a9d43cb70ee
21 May 2019, 10:06 UTC319 viewsread 12 August 2026
New Withdrawal Successfully Sent: User witolddreas withdrawn his bitcoin forest profit amount of 0.00449000 BTC Forest. BTC Forest Transaction ID: https://www.blockchain.com/btc/tx/4a2d4dc3577213032eef26ba4b38ce5112af7bcdeaf71c637c497a9d43cb70ee
Showing the 12 most recent of 20 posts we hold for @BTCforest_Payments. 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.
Citation-graph rank
Citation-graph rank — 845,720 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 2 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“BTCForest Payments|Forecast” (@BTCforest_Payments), 13 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/BTCforest_Payments.
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.