Job listings — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
5 measurements spanning 63 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 92–95 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Oct 2026, 02:21
92
-2
14 Sept 2026, 15:55
94
-1
22 Aug 2026, 22:13
95
+1
9 Aug 2026, 13:02
94
no change
7 Aug 2026, 20:19
94
first reading
Engagement
6 posts held, back to 18 November 2021 — 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 6 posts for this entry, the most recent from 31 January 2023. An engagement rate over an empty window would be a number about nothing.
Reaction mix
6 reactions across 2 posts, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
6
100.0%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 2 of the 6 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 18 November 2021 to 31 January 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
3️⃣ Senior UX/UI designer
💸 Ricompensa: €5.000 per chi ci aiuta a trovarlo 💸
Avascan, il blockchain explorer preferito per la rete Avalanche, è alla ricerca di un designer UX/UI che si unisca al nostro team di sviluppo del sito web e porti avanti la nostra missione di migliorare la leggibilità dei dati e la facilità di comprensione da parte degli utenti in un ambiente che è ancora molto complicato tecnologicamente.…
🚨 Le due posizioni Backend Node e Frontend React sono sempre aperte 🚨
🤑 RAL Backend: €70-90k. RAL Frontend: €60-80k 🤑
💸 Ed i Bounty validi più che mai (5000€)💸
ℹ️ Per info e chiarimenti potete scrivere a @lorenzofvilla ℹ️
📝 Per mandare la candidatura trovate il form nelle relative pagine degli annunci 📝
2️⃣Senior Front-end React Developer
💸 Ricompensa: €5.000 per chi ci aiuta a trovarlo 💸
Descrizione
Avascan, il blockchain explorer preferito per la rete Avalanche, è alla ricerca di uno sviluppatore front-end di talento da inserire nel nostro team di sviluppo web. Stiamo cercando uno sviluppatore React che contribuisca alla gestione della migrazione del sito web dell'esploratore Avascan.
Requisiti
- Conoscenza del…
1️⃣Senior Back-end Node.js Developer
💸 Ricompensa: €5.000 per chi ci aiuta a trovarlo 💸
Descrizione
Avascan, l’explorer di riferimento per la rete Avalanche, sta cercando uno sviluppatore back-end italiano di talento che possa entrare nel team a lungo termine. Siamo alla ricerca di un esperto di Node.js che gestirà in autonomia più progetti all’interno di Avascan.
Requisiti
- Essere italiano
- Esperienza Node.js
-…
Avascan (@AvascanExplorer), l’explorer di riferimento di Avalanche, sta cercando nuove figure da inserire nel team. Questo canale facilita la lettura e la condivisione delle posizioni lavorative.
- Per ogni offerta è previsto un bounty per chi ci segnala la figura professionale che a noi interessa;
- Il bounty viene corrisposto al termine del periodo di prova del candidato (solitamente della durata di 1 mese), una v…
Showing the 6 most recent of 6 posts we hold for @avascan_bounties. 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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@avascan_bounties named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@avascanexplorer named in 1 post, 10 August 2026 – 10 August 2026
@l_f_v1 named in 1 post, 10 August 2026 – 10 August 2026
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 10 October 2026 — this
entry's latest reading, not the date you are reading this.
“Avascan Bounties” (@avascan_bounties), 92 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/avascan_bounties.
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.