Posted without readable text
❤74custom 52538649586801195214

Channel
@l1ga_pass
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
21,721subscribers
-1,445 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002788372273 |
|---|---|
| Type | Channel |
| Username | @l1ga_pass |
| Description | L1GA PASS - это сезонный ивент для игроков Лиги Ставок. Делай ставки, выполняй задания, фарми Liga coins и забирай редкие скины и фрибеты! Чат: @l1gapass_chat Официальный сайт: https://pass.ligastavok.ru/ Регламент акций: https://bit.ly/4qprvCE |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/l1ga_pass |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 22:49 | 21,721 | -195 |
| 9 Nov 2026, 22:37 | 21,916 | -203 |
| 8 Nov 2026, 10:50 | 22,119 | -129 |
| 7 Nov 2026, 08:27 | 22,248 | -117 |
| 6 Nov 2026, 06:48 | 22,365 | -120 |
| 5 Nov 2026, 05:34 | 22,485 | -43 |
| 4 Nov 2026, 04:46 | 22,528 | -53 |
| 3 Nov 2026, 02:50 | 22,581 | -50 |
| 2 Nov 2026, 05:48 | 22,631 | -48 |
| 1 Nov 2026, 04:39 | 22,679 | -269 |
| 31 Oct 2026, 02:07 | 22,948 | -1,289 |
| 29 Oct 2026, 22:28 | 24,237 | -70 |
| 28 Oct 2026, 22:16 | 24,307 | -25 |
| 27 Oct 2026, 23:11 | 24,332 | -962 |
| 26 Oct 2026, 19:29 | 25,294 | -42 |
| 25 Oct 2026, 19:00 | 25,336 | -31 |
| 24 Oct 2026, 16:36 | 25,367 | -49 |
| 23 Oct 2026, 19:07 | 25,416 | -243 |
| 22 Oct 2026, 18:19 | 25,659 | -57 |
| 21 Oct 2026, 12:57 | 25,716 | first reading |
142 posts held, back to 22 July 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 135 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 142 (22 July 2026 – 11 November 2026) |
| Views total | 43,406 |
| Reactions total | 473 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 15:37 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 videos 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.
2,798 reactions across 141 posts, in 20 distinct kinds. The most used accounts for 30.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 861 | 30.8% | |
| 🔥 | 486 | 17.4% | |
| custom 5231172511856607462 | 467 | 16.7% | |
| 👍 | 268 | 9.58% | |
| 😁 | 188 | 6.72% | |
| 👏 | 105 | 3.75% | |
| 🌚 | 73 | 2.61% | |
| 🎉 | 71 | 2.54% | |
| 💯 | 56 | 2.00% | |
| 🕊 | 50 | 1.79% | |
| 🥰 | 44 | 1.57% | |
| 🤔 | 38 | 1.36% | |
| ❤🔥 | 29 | 1.04% | |
| ☃ | 27 | 0.965% | |
| custom 5253864958680119521 | 10 | 0.357% | |
| custom 5384381395533588639 | 9 | 0.322% | |
| custom 6064493624383508136 | 6 | 0.214% | |
| custom 5345865314234032148 | 4 | 0.143% | |
| custom 5372950572003527247 | 4 | 0.143% | |
| custom 5431578735314761227 | 2 | 0.071% |
Custom emoji. 7 of the rows above are 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 are Telegram’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 141 of the 142 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 2,798 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 142 most recent posts we hold, published 22 July 2026 to 11 November 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.
Telegram’s own ‘edited’ marker: 4 of 30 posts held from the last 30 days (13.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Posted without readable text
❤74custom 52538649586801195214
🔥🔥🔥 Интересно, а Брюмастер сдаёт бутылки?
custom 52538649586801195216😁4💯3❤1
🔥🔥🔥 Сегодня стреляем тройными 🤩
😁6custom 60644936243835081364❤2🥰1
🔥🔥🔥 Шаманчик, связывай! 🕺
👏8😁6custom 60644936243835081362
🔥🔥🔥 Время пострелять, между нами пальба… Пау-Пау-Пау-Пау-Попадаешь в жбанчик, остаешься хай-таб. Тащилка…🤩
👏7😁5🕊1
🔥🔥🔥 Я флекшу налом на @#$%&!*, но то что в моих кроссовках тебя не должно @#$%&!* 💰
👏6🔥3🥰1
🔥🔥🔥 Есть желание покидать флешки в лицо тиммейтам? Делайте, мы поддержим 🔈
❤6😁6👍2custom 54315787353147612272👏1
🔥🔥🔥 Здесь ведь чёрным по белому написано, что у него аллергия на "Мекансм", неандерталец!
custom 53843813955335886399😁2🕊1
🔥🔥🔥 Хола, Амигос, велком ту ЛигоПассо, гоу плей Эншент тудэй 🤠
🔥5custom 53458653142340321484🌚3
🔥🔥🔥 Сегодня — та самая ночь. И это повторится снова и снова. Должно повториться. Это не самая приятная ночь на Инферно. И даже не самая жаркая. Но ночь — именно та 🤷♂
custom 53729505720035272474💯2😁2
🔥🔥🔥 А ну быстро отклеивать этикетки от бананов! 🤩 Пару *наклеек* спрятаны на картинке 😏
👏6custom 52311725118566074626❤🔥1
🔥🔥🔥 Баскетболисты есть?
😁6custom 52311725118566074624👏2
Showing the 12 most recent of 142 posts we hold for @l1ga_pass. 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.
@l1ga_pass edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 2 registered channels — 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“L1GA PASS” (@l1ga_pass), 21,721 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/l1ga_pass.
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.