5 May 2026, 02:45 UTC≈2,170 viewsread 7 August 2026
https://x.com/RuneCrypto_/status/2051493360154587360?s=20
Signed Rune
Channel
arcane giveaways
@arcane_giveaways
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
3,332subscribers
+147 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002951230057 |
|---|---|
| Type | Channel |
| Username | @arcane_giveaways |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/arcane_giveaways |
Topic
Giveaways & airdrops — 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 14 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 04:39 | 3,332 | -6 |
| 12 Sept 2026, 13:21 | 3,338 | -4 |
| 8 Sept 2026, 06:37 | 3,342 | +180 |
| 2 Sept 2026, 16:34 | 3,162 | -2 |
| 30 Aug 2026, 22:46 | 3,164 | -3 |
| 28 Aug 2026, 01:47 | 3,167 | -1 |
| 25 Aug 2026, 00:55 | 3,168 | -4 |
| 21 Aug 2026, 11:05 | 3,172 | -5 |
| 18 Aug 2026, 01:12 | 3,177 | +2 |
| 14 Aug 2026, 21:53 | 3,175 | -4 |
| 11 Aug 2026, 04:51 | 3,179 | -3 |
| 7 Aug 2026, 20:54 | 3,182 | -3 |
| 6 Aug 2026, 22:02 | 3,185 | first reading |
Engagement
20 posts held, back to 20 February 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 3 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 20 posts for this entry, the most recent from 5 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
19 Mar 2026, 22:49 UTC≈4,060 viewsread 7 August 2026
Forwarded from @arcanegems
skill based giveaway https://x.com/runecrypto_/status/2034763868321264006?s=46
Signed Carranza
16 Mar 2026, 22:17 UTC≈4,000 viewsread 7 August 2026
hit this, more gives https://x.com/RuneCrypto_/status/2033668848671453651?s=20
Signed Carranza
23 Feb 2026, 14:56 UTC≈4,210 viewsread 7 August 2026
hit this post if it gets active, i'll give 100 winners here and use wagmi with my referral https://x.com/RuneCrypto_/status/2025947384421999062?s=20
Signed Carranza
20 Feb 2026, 00:54 UTC≈4,040 viewsread 7 August 2026
okay just gave 140 winners hope u turn that into a 100X
Signed Carranza
20 Feb 2026, 00:54 UTC≈3,740 viewsread 7 August 2026
This check has been fully claimed.
Signed Carranza
20 Feb 2026, 00:53 UTC≈3,460 viewsread 7 August 2026
hint: X
Signed Carranza
20 Feb 2026, 00:52 UTC≈3,390 viewsread 7 August 2026
guess the password, all lowercase, easy
Signed Carranza
20 Feb 2026, 00:52 UTC≈3,270 viewsread 7 August 2026
/claim wagmi@g56fd63 on https://t.me/wagmitradebot?start=r_GCarranza
Signed Carranza
20 Feb 2026, 00:51 UTC≈2,960 viewsread 7 August 2026
team fixed it instantly let’s try again
Signed Carranza
20 Feb 2026, 00:50 UTC≈2,850 viewsread 7 August 2026
“What was happening: when 100+ people tried to claim the same check at once, the escrow wallet got flooded with concurrent transfer requests. The first one would start processing, and all subsequent ones would get rejected because the escrow wallet already had a pending tx The serial queue I pushed in the last commit already fixes this, claims now execute one at a time instead of all at once. I just also added "unco…
Signed Carranza
20 Feb 2026, 00:45 UTC≈2,110 viewsread 7 August 2026
apparently was lagging cuz a lot of people tried to claim at same time, will make more tomorrow once they speed it up!
Signed Carranza
Showing the 12 most recent of 20 posts we hold for @arcane_giveaways. 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.
Mentions
Named by 1 registered channel — 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“arcane giveaways” (@arcane_giveaways), 3,332 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/arcane_giveaways.
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.