Telegram RegisterThe public register of Telegram
Telegram profile photo for L1GA PASS

Channel

L1GA PASS

@l1ga_pass

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

23,332subscribers

+166 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002788372273
TypeChannel
Username@l1ga_pass
DescriptionL1GA PASS - это сезонный ивент для игроков Лиги Ставок. Делай ставки, выполняй задания, фарми Liga coins и забирай редкие скины и фрибеты! Чат: @l1gapass_chat Официальный сайт: https://pass.ligastavok.ru/ Регламент акций: https://bit.ly/4qprvCE
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live28 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 28 September 2026
On Telegramt.me/l1ga_pass

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 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 why it has no browse page of its own yet.

Growth

21,29223,33222,3127 August 2026 — 23,166 subscribers7 August 2026 — 23,166 subscribers8 August 2026 — 23,145 subscribers9 August 2026 — 23,126 subscribers10 August 2026 — 23,088 subscribers11 August 2026 — 23,053 subscribers12 August 2026 — 23,002 subscribers13 August 2026 — 22,970 subscribers14 August 2026 — 22,896 subscribers15 August 2026 — 22,850 subscribers17 August 2026 — 22,806 subscribers18 August 2026 — 22,759 subscribers19 August 2026 — 22,689 subscribers20 August 2026 — 22,655 subscribers21 August 2026 — 22,590 subscribers22 August 2026 — 22,488 subscribers24 August 2026 — 22,407 subscribers25 August 2026 — 22,383 subscribers26 August 2026 — 22,331 subscribers27 August 2026 — 22,315 subscribers28 August 2026 — 22,197 subscribers29 August 2026 — 22,152 subscribers30 August 2026 — 22,086 subscribers31 August 2026 — 22,058 subscribers1 September 2026 — 22,007 subscribers2 September 2026 — 21,940 subscribers4 September 2026 — 21,903 subscribers7 September 2026 — 21,768 subscribers10 September 2026 — 21,488 subscribers12 September 2026 — 21,437 subscribers14 September 2026 — 21,381 subscribers15 September 2026 — 21,350 subscribers17 September 2026 — 21,292 subscribers28 September 2026 — 23,332 subscribers7 August 202628 September 2026
34 measurements spanning 52 days, net +166. 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 20,986–23,638 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
28 Sept 2026, 16:5723,332+2,040
17 Sept 2026, 22:2121,292-58
15 Sept 2026, 17:3821,350-31
14 Sept 2026, 04:5721,381-56
12 Sept 2026, 12:4121,437-51
10 Sept 2026, 08:0221,488-280
7 Sept 2026, 00:3721,768-135
4 Sept 2026, 09:1921,903-37
2 Sept 2026, 21:4721,940-67
1 Sept 2026, 20:5722,007-51
31 Aug 2026, 18:5822,058-28
30 Aug 2026, 21:5322,086-66
29 Aug 2026, 18:5522,152-45
28 Aug 2026, 17:1722,197-118
27 Aug 2026, 14:2322,315-16
26 Aug 2026, 13:3522,331-52
25 Aug 2026, 11:3222,383-24
24 Aug 2026, 13:4622,407-81
22 Aug 2026, 18:1722,488-102
21 Aug 2026, 06:2622,590first reading

Engagement

90 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 58 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
19.7%
avg views ÷ 23,332 subscribers
Avg views / post
4,600
25 posts measured
Reaction rate
0.511%
reactions ÷ views · ER floor
Posts in window
26
of 90 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 September 2026
Posts held90 (22 July 2026 – 28 September 2026)
Views total114,989
Reactions total588
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 08:15 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.

What this channel posts

Photos
557
Videos
16
Links
409

Lifetime counters from Telegram’s own channel header, read 29 September 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.

Video runtime
2m 13s
Average length
44s

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.

Reaction mix

1,632 reactions across 89 posts, in 14 distinct kinds. The most used accounts for 29.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤48829.9%
custom 523117251185660746228817.6%
🔥28517.5%
👍20212.4%
😁885.39%
👏523.19%
🎉442.70%
💯442.70%
🌚422.57%
🕊251.53%
❤‍🔥221.35%
🤔221.35%
🥰181.10%
☃120.735%

Custom emoji. One 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 count beside it is 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 89 of the 90 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 1,632 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 90 most recent posts we hold, published 22 July 2026 to 28 September 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.

Recent posts

28 Sept 2026, 18:02 UTC≈1,490 views54 reactionsread 29 September 2026
Forwarded from @l1gastavokrivalsPhoto

РОЗЫГРЫШ 10 НОЖЕЙ ОТ 💚💚💚 💚💚💚💚 CS2 🔫 ❓ Условия участия: ➡️ Подпишись на L1GA STAVOK RIVALS ➡️ Жми кнопку «LSR» Призовой фонд: 1️⃣ Flip Knife | Gamma Doppler Phase 3 (Factory New) 2️⃣ Stiletto Knife | Case Hardened (Minimal Wear) 3️⃣ Falchion Knife | Fade (Factory New) 4. Survival Knife | Crimson Web (Minimal Wear) 5. Bowie Knife | Autotronic (Minimal Wear) 6. Shadow Daggers | Tiger Tooth (Factory New) 7. Navaja Knif…

❤30👍11🔥9custom 52311725118566074624

28 Sept 2026, 10:51 UTC≈2,720 views15 reactionsread 29 September 2026
Photo

🔥🔥🔥 Акс уже приступил к выполнению дейликов, а с чего ты начал новую неделю? ☀️ ❤️ — с чашечки кофеёчка 😁 — с утренней каточки

custom 52311725118566074628❤7

27 Sept 2026, 17:20 UTC≈2,620 views22 reactionsread 29 September 2026
Photo

🔥🔥🔥 Для самых усидчивых подготовили промики, успейте найти 🫥

❤9😁8custom 52311725118566074625

27 Sept 2026, 16:44 UTC≈2,220 views16 reactionsread 29 September 2026
Photo

🔥🔥🔥 А потом этот момент настаёт: мгновение, когда дыхание замедляется. И с каждой каткой ты лузаешь все ммры...

custom 52311725118566074629❤4🔥3

26 Sept 2026, 16:01 UTC≈2,050 views25 reactionsread 29 September 2026
Photo

🔥🔥🔥 Рубик опять украл какое-то заклинание, но в этот раз у Алхимика Но вместо колбы здесь какие-то символы, разберемся? 😢

❤10💯7🌚5🔥3

26 Sept 2026, 13:36 UTC≈1,670 views12 reactionsread 29 September 2026
Photo

🔥🔥🔥 Развесили новые дейлики — хватаем листовки и лутаем коины 🥰

🔥6☃2👍2custom 52311725118566074622

25 Sept 2026, 15:33 UTC≈1,920 views17 reactionsread 29 September 2026
Photo

🔥🔥🔥 Сыны Миража, общий сбор! Тут для вас фришный дейлик 🥂

custom 52311725118566074628👍5❤4

25 Sept 2026, 09:31 UTC≈80,400 views100 reactionsread 29 September 2026

Posted without readable text

🔥60❤21🌚13👍5☃1

24 Sept 2026, 18:24 UTC≈1,830 views15 reactionsread 29 September 2026
Photo

🔥🔥🔥 Дейлики обновлены, а для мейнеров Фантомки завезли кое-что особенное 😘

👍8custom 52311725118566074624🎉3

23 Sept 2026, 19:12 UTC≈1,690 views24 reactionsread 29 September 2026
Photo

🔥🔥🔥 Внимание! 24 сентября с 12:00 до 14:00 по московскому времени на сайте будут проходить технические работы, поэтому мы продлим время выполнения заданий 🖥

👍13❤5❤‍🔥5🤔1

23 Sept 2026, 17:10 UTC≈1,510 views15 reactionsread 29 September 2026
Photo

🔥🔥🔥 Вечерние дейлики на месте, самое время устраивать ночные гонки ☺️

custom 52311725118566074627❤3🔥3☃2

Showing the 12 most recent of 90 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.

Forward network

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.

Mentions

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.

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

“L1GA PASS” (@l1ga_pass), 23,332 subscribers as measured 28 September 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.