https://twitter.com/nearblocks/status/1840360888559173940

Channel
Nearblocks.io Updates
@nearblocks
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,273subscribers
+226 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001771916455 |
|---|---|
| Type | Channel |
| Username | @nearblocks |
| Created | 14 February 2022 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/nearblocks |
Topic
Technology — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 38% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 10:36 | 1,273 | +11 |
| 10 Nov 2026, 10:37 | 1,262 | +2 |
| 7 Nov 2026, 01:29 | 1,260 | +4 |
| 4 Nov 2026, 04:57 | 1,256 | +5 |
| 1 Nov 2026, 01:48 | 1,251 | +6 |
| 29 Oct 2026, 08:45 | 1,245 | +6 |
| 26 Oct 2026, 06:27 | 1,239 | +15 |
| 22 Oct 2026, 21:38 | 1,224 | -1 |
| 20 Oct 2026, 01:58 | 1,225 | +7 |
| 17 Oct 2026, 00:48 | 1,218 | +5 |
| 14 Oct 2026, 07:16 | 1,213 | +10 |
| 10 Oct 2026, 13:16 | 1,203 | +15 |
| 4 Oct 2026, 19:59 | 1,188 | +30 |
| 25 Sept 2026, 06:19 | 1,158 | +20 |
| 17 Sept 2026, 05:20 | 1,138 | +6 |
| 13 Sept 2026, 05:40 | 1,132 | +8 |
| 9 Sept 2026, 00:36 | 1,124 | +8 |
| 3 Sept 2026, 14:20 | 1,116 | +5 |
| 31 Aug 2026, 12:38 | 1,111 | +10 |
| 25 Aug 2026, 05:53 | 1,101 | first reading |
Engagement
8 posts held, back to 14 February 2022 — 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 page 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 8 posts for this entry, the most recent from 29 September 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://twitter.com/nearblocks/status/1839636115638104386
https://twitter.com/nearblocks/status/1838911332005056656
https://twitter.com/nearblocks/status/1838071050174906571
https://twitter.com/NEARProtocol/status/1835942184241254466
https://twitter.com/LearnNear/status/1835696431279079700
Channel photo updated
Channel created
Showing the 8 most recent of 8 posts we hold for @nearblocks. 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.
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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“Nearblocks.io Updates” (@nearblocks), 1,273 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/nearblocks.
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.