Channel
@vl3ir
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
31subscribers
-4 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003036128657 |
|---|---|
| Type | Channel |
| Username | @vl3ir |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/vl3ir |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 14:17 | 31 | -2 |
| 25 Aug 2026, 01:36 | 33 | -1 |
| 16 Aug 2026, 20:34 | 34 | -1 |
| 10 Aug 2026, 23:15 | 35 | no change |
| 9 Aug 2026, 12:46 | 35 | first reading |
9 posts held, back to 14 March 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 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 9 posts for this entry, the most recent from 13 April 2026. An engagement rate over an empty window would be a number about nothing.
147 reactions across 9 posts, in 16 distinct kinds. The most used accounts for 20.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5379787017477438527 | 30 | 20.4% | |
| custom 5411364969952334411 | 29 | 19.7% | |
| custom 5249051709090584417 | 22 | 15.0% | |
| custom 5341669899984973550 | 11 | 7.48% | |
| custom 5248979613769553349 | 10 | 6.80% | |
| custom 5444915600906273647 | 9 | 6.12% | |
| custom 5343541805646359028 | 7 | 4.76% | |
| custom 4949560263696188565 | 6 | 4.08% | |
| custom 5380078370878929259 | 5 | 3.40% | |
| custom 5379930830162375932 | 4 | 2.72% | |
| custom 5445284482762425119 | 4 | 2.72% | |
| custom 5242391945686299768 | 3 | 2.04% | |
| custom 5208550107359751901 | 2 | 1.36% | |
| custom 5210666976480863797 | 2 | 1.36% | |
| custom 5445145038059224424 | 2 | 1.36% | |
| custom 5242588212806823745 | 1 | 0.68% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 9 of the 9 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 147reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 14 March 2026 to 13 April 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
File, posted without a caption
custom 541136496995233441118custom 54452844827624251193custom 49495602636961885652custom 52489796137695533492custom 52425882128068237451custom 52490517090905844171custom 53800783708789292591
Signed あ
Photo, posted without a caption
custom 53797870174774385278custom 52490517090905844177custom 53435418056463590283custom 54113649699523344113custom 53800783708789292592custom 49495602636961885651custom 53416698999849735501
Signed あ
File, posted without a caption
custom 537978701747743852710custom 52489796137695533492custom 54113649699523344112custom 54449156009062736471
Signed あ
Photo, posted without a caption
custom 53797870174774385276custom 52423919456862997683custom 52490517090905844172custom 53800783708789292591
Signed あ
Photo, posted without a caption
custom 52489796137695533496custom 53435418056463590283custom 52490517090905844172custom 54451450380592244241
Signed あ
File, posted without a caption
custom 54449156009062736478custom 52490517090905844172custom 54113649699523344112custom 49495602636961885651custom 53416698999849735501custom 53435418056463590281
Signed あ
Photo, posted without a caption
custom 53416698999849735508custom 52106669764808637972custom 53799308301623759322custom 54113649699523344111custom 54452844827624251191
Signed あ
Photo, posted without a caption
custom 52490517090905844175custom 53799308301623759322custom 54113649699523344112custom 49495602636961885651custom 53416698999849735501
Signed あ
Photo, posted without a caption
custom 53797870174774385276custom 52490517090905844173custom 52085501073597519012custom 49495602636961885651custom 53800783708789292591custom 54113649699523344111custom 54451450380592244241
Signed あ
Showing the 9 most recent of 9 posts we hold for @vl3ir. 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 — 652,838 of 1,629,372entries 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 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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“Kairos” (@vl3ir), 31 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/vl3ir.
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.