Channel

1.14 ── &' 𝗚𝗟𝗢𝗥𝗜𝗢𝗨𝗦, 𝗟𝗘𝗜𝗔𝗥𝗘𝗦 𝗦𝗤𝗨𝗔𝗗

@LEIARESSQUAD

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

7,935subscribers

-582 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Topic

Gaming — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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

Engagement

7 posts held, back to 27 May 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 22 pages 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 7 posts for this entry, the most recent from 16 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime

27s

Average length

27s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

Showing the 7 most recent of 7 posts we hold for @LEIARESSQUAD. 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

9

handles named in this channel’s posts, vacant today

Evidenced gone

4

we ourselves saw one of these resolve, at some point

Never seen alive

5

vacant every time we have ever looked

@LEIARESSQUAD named 9 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.

Evidenced gone

We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.

Never seen alive

References a handle that is not a live channel — we have no record it ever was one.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“1.14 ── &' 𝗚𝗟𝗢𝗥𝗜𝗢𝗨𝗦, 𝗟𝗘𝗜𝗔𝗥𝗘𝗦 𝗦𝗤𝗨𝗔𝗗” (@LEIARESSQUAD), 7,935 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/LEIARESSQUAD.

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.