Channel
@qwikmine
On this record: Growth · Engagement · Posts · Citations · Cite this entry
139subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002044920321 |
|---|---|
| Type | Channel |
| Username | @qwikmine |
| Created | 15 January 2024 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/qwikmine |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 11:45 | 139 | -1 |
| 8 Aug 2026, 22:30 | 140 | no change |
| 7 Aug 2026, 13:50 | 140 | -1 |
| 7 Aug 2026, 12:11 | 141 | first reading |
7 posts held, back to 15 January 2024 — 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 7 posts for this entry, the most recent from 26 January 2024. An engagement rate over an empty window would be a number about nothing.
Qwikmine pinned «QWIK site is now available with us! We will begin IMACD and share updates as soon as the first racks are live (ETA 29-30 Jan) 3rd party devices, $GDAG and $TOOLS device setup charges incl transport will be taken care of by respective entity opex budgets…»
QWIK site is now available with us! We will begin IMACD and share updates as soon as the first racks are live (ETA 29-30 Jan) 3rd party devices, $GDAG and $TOOLS device setup charges incl transport will be taken care of by respective entity opex budgets With this we kick off! https://twitter.com/qwikmine/status/1750797251625009211
Qwikmine pinned «Trading for $QWIK has commenced. - Taxes have been set as per https://docs.qwikmine.com - Contract is renounced - Liquidity has been locked for 1 year on #Blocktools vault To be noted this will be utilized to distribute to ecosystem holders in the near…»
Trading for $QWIK has commenced. - Taxes have been set as per https://docs.qwikmine.com - Contract is renounced - Liquidity has been locked for 1 year on #Blocktools vault To be noted this will be utilized to distribute to ecosystem holders in the near future. TBA Respective % allocations as per Docs have commenced and will continue over the forthcoming days as we formalize the opex rollouts $QWIK community may p…
Qwikmine pinned «$QWIK seeks to introduce a new concept in the ERC-20 space by means of tokenizing revenue share from hosting solutions undertaken in the mining datacenter. Counting down to a launch-time of 4pm UTC today, interested users will find the below helpful links…»
$QWIK seeks to introduce a new concept in the ERC-20 space by means of tokenizing revenue share from hosting solutions undertaken in the mining datacenter. Counting down to a launch-time of 4pm UTC today, interested users will find the below helpful links to participate in the $QWIK launch. Thank You for your support! Analyze Contract: https://repo.sourcify.dev/contracts/full_match/1/0xd7dB52DAA32b738eD55b23A487aF…
Channel created
Showing the 7 most recent of 7 posts we hold for @qwikmine. 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 — 290,619 of 1,350,102entries 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.
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.
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.
“Qwikmine” (@qwikmine), 139 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/qwikmine.
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.