3 Aug 2026, 20:11 UTCviews —
Channel name was changed to «kailax SO2 | Rankoff»
Channel
kailax SO2 | Rankoff
@kailax999
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,210subscribers
+124 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002045359368 |
|---|---|
| Type | Channel |
| Username | @kailax999 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/kailax999 |
Topic
Other / unclassifiable — 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 100% 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, 19:39 | 1,210 | +156 |
| 12 Sept 2026, 17:19 | 1,054 | +10 |
| 9 Sept 2026, 01:41 | 1,044 | -18 |
| 3 Sept 2026, 10:12 | 1,062 | -7 |
| 31 Aug 2026, 00:06 | 1,069 | -1 |
| 27 Aug 2026, 15:17 | 1,070 | -8 |
| 24 Aug 2026, 21:59 | 1,078 | +8 |
| 21 Aug 2026, 06:04 | 1,070 | -5 |
| 17 Aug 2026, 20:44 | 1,075 | -5 |
| 15 Aug 2026, 03:15 | 1,080 | -4 |
| 11 Aug 2026, 21:32 | 1,084 | -2 |
| 11 Aug 2026, 07:16 | 1,086 | first reading |
Engagement
4 posts held, back to 23 April 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 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 4 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
3 Aug 2026, 20:10 UTCviews —
Channel photo updated
3 Aug 2026, 20:09 UTCviews —
Channel name was changed to «Kailax SO2 | Rankoff»
23 Apr 2026, 17:23 UTCviews —
kailax SO2 | Rankoff pinned Deleted message
Showing the 4 most recent of 4 posts we hold for @kailax999. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Семья Berserkers 😈
@Berserkers_nt · 77,020
Telegram ranks this channel #12 of 50 here — alongside 49 others — read 19 August 2026
@Berserkers_nt · 77,020
Telegram ranks this channel #12 of 50 here — alongside 49 others — read 19 August 2026
Virtus.pro Mobile
@virtuspro_mobile · 23,574
Telegram ranks this channel #61 of 77 here — alongside 76 others — read 18 September 2026
@virtuspro_mobile · 23,574
Telegram ranks this channel #61 of 77 here — alongside 76 others — read 18 September 2026
SaiNts
@officialSaiNts · 32,910
Telegram ranks this channel #61 of 72 here — alongside 71 others — read 6 September 2026
@officialSaiNts · 32,910
Telegram ranks this channel #61 of 72 here — alongside 71 others — read 6 September 2026
Union | Standoff 2
@union_standoff2 · 25,439
Telegram ranks this channel #67 of 72 here — alongside 71 others — read 14 September 2026
@union_standoff2 · 25,439
Telegram ranks this channel #67 of 72 here — alongside 71 others — read 14 September 2026
GentlemaN
@artyom_gentleman · 92,584
Telegram ranks this channel #71 of 72 here — alongside 71 others — read 17 August 2026
@artyom_gentleman · 92,584
Telegram ranks this channel #71 of 72 here — alongside 71 others — read 17 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“kailax SO2 | Rankoff” (@kailax999), 1,210 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/kailax999.
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.