25 Mar 2022, 09:31 UTC95 viewsread 13 August 2026
Website has had a revamp! https://raskul.com - main site https://blog.raskul.com - blog https://rigs.raskul.com - shop POOL LINK https://pool.raskul.com
Channel
POOL.RASKUL.COM
@raskulbeampool
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001212117615 |
|---|---|
| Type | Channel |
| Username | @raskulbeampool |
| Description | Please ensure your Beam wallet is online and synchronised. |
| Created | Between 1 March 2018 and 29 June 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/raskulbeampool |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 14:31 | 3 | no change |
| 7 Aug 2026, 23:11 | 3 | first reading |
Engagement
20 posts held, back to 29 June 2020 — 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 25 March 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 10
- Links
- 46
Lifetime counters from Telegram’s own channel header, read 13 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
19 Sept 2021, 10:41 UTC431 viewsread 13 August 2026
ANNOUNCING THE BEAM PRIVACY GLASGOW RANGERS FAN TOKEN https://www.raskul.com/the-glasgow-rangers-fan-token/
26 Jul 2020, 15:13 UTC90 viewsread 13 August 2026
BLOCK! 817540 found by 1bb57062427eee901bb9c75ba4826986996f0fbe6697ed54d4b849c08564f0f5326 🙂
26 Jul 2020, 13:49 UTC90 viewsread 13 August 2026
NOTE: Performed a quick update and reboot of the server this morning. Mostly OS security patches. All running fine again.
24 Jul 2020, 16:13 UTC90 viewsread 13 August 2026
In celebration of our 100th confirmed block at pool, I have added a couple optimisations, and we will look at working on some new features - maybe a mining calculator or some stuff. stay tuned!
21 Jul 2020, 15:20 UTC87 viewsread 13 August 2026
FINAL NOTE: The bug has been fixed. NOTES: ISSUE; on Blockfound event, irregularly, the node would disconnect the pool with some SSL_ERROR FIX; Amended node config (was not a pool issue bug was node related)
21 Jul 2020, 14:21 UTC74 viewsread 13 August 2026
UPDATE: The much-elusive bug in the pool software has been found. To fix this, there will be some amount of downtime in the pool, please ensure that you have a failover pool specified in your miner software. I will try to ensure minimal downtime as is possible. Will further update when this is fixed.
18 Jul 2020, 11:40 UTC67 viewsread 13 August 2026
UPDATE: We have tracked the bug and will endeavour to fix it imminently, in the meantime, please could you all open your wallets to receive mining payments - and allow backed up utxo to clear from the pool. THANK YOU FOR YOUR PATIENCE!
13 Jul 2020, 15:40 UTC74 viewsread 13 August 2026
REITERATE: debugging process is still ongoing and this means that payments must be made manually. If you require a payout from the pool, please just ask!
9 Jul 2020, 21:14 UTC62 viewsread 13 August 2026
UPDATE: payouts for the current pending blocks have been actioned. this is a short-window and will attemot for 6hrs. If your wallet is not open in this time, Your payout will be sent again manually in the near future.
9 Jul 2020, 18:36 UTC56 viewsread 13 August 2026
UPDATE: THERE ARE NOW THREE BLOCKS PENDING TO BE PAID TO MINERS, IF YOU REQUIRE A MANUAL PAYMENT, PLEASE LET ME KNOW AND I WILL ACTION AT EARLIEST OPPORTUNITY. WE ARE STILL DEBUGGING AND WILL KEEP YOU ALL UPDATED, THANKS FOR YOUR PATIENCE!
9 Jul 2020, 06:45 UTC56 viewsread 13 August 2026
NOTICE: There has been a small bug realised in the pool - does not affect mining! However, automatic payouts are on hold whilst we investigate - if you require a manual payment from the currently pending block, to your mining address, please just ask and i will action asap. thank you for your patience.
Showing the 12 most recent of 20 posts we hold for @raskulbeampool. 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.
Forward network
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“POOL.RASKUL.COM” (@raskulbeampool), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/raskulbeampool.
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.