Telegram RegisterThe public register of Telegram
Telegram profile photo for STANDLEO PC

Channel

STANDLEO PC

@standleo_exe

On this record: Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

21,500subscribers

+527 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-1002559816398
TypeChannel
Username@standleo_exe
Created30 May 2025measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live3 September 2026
Measurements held26
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/standleo_exe

Growth

20,95221,54421,2487 August 2026 — 20,973 subscribers7 August 2026 — 20,973 subscribers7 August 2026 — 20,977 subscribers8 August 2026 — 20,962 subscribers10 August 2026 — 20,953 subscribers11 August 2026 — 20,976 subscribers12 August 2026 — 20,963 subscribers13 August 2026 — 20,952 subscribers15 August 2026 — 20,955 subscribers16 August 2026 — 21,099 subscribers17 August 2026 — 21,281 subscribers18 August 2026 — 21,369 subscribers19 August 2026 — 21,387 subscribers20 August 2026 — 21,375 subscribers22 August 2026 — 21,393 subscribers23 August 2026 — 21,413 subscribers25 August 2026 — 21,418 subscribers26 August 2026 — 21,448 subscribers26 August 2026 — 21,465 subscribers28 August 2026 — 21,491 subscribers29 August 2026 — 21,522 subscribers30 August 2026 — 21,526 subscribers31 August 2026 — 21,544 subscribers1 September 2026 — 21,521 subscribers2 September 2026 — 21,517 subscribers3 September 2026 — 21,500 subscribers21,5007 August 20263 September 2026
26 measurements spanning 27 days, net +527. 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,863–21,633 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
3 Sept 2026, 12:2121,500-17
2 Sept 2026, 09:1821,517-4
1 Sept 2026, 10:5721,521-23
31 Aug 2026, 08:3821,544+18
30 Aug 2026, 10:0321,526+4
29 Aug 2026, 06:2521,522+31
28 Aug 2026, 03:0221,491+26
26 Aug 2026, 23:4321,465+17
26 Aug 2026, 02:2221,448+30
25 Aug 2026, 03:3621,418+5
23 Aug 2026, 19:4921,413+20
22 Aug 2026, 07:2621,393+18
20 Aug 2026, 21:5321,375-12
19 Aug 2026, 23:4221,387+18
18 Aug 2026, 20:4321,369+88
17 Aug 2026, 18:0521,281+182
16 Aug 2026, 17:0821,099+144
15 Aug 2026, 00:2420,955+3
13 Aug 2026, 15:0820,952-11
12 Aug 2026, 13:4420,963first reading

Engagement

7 posts held, back to 30 May 2025the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 47 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
61.2%
avg views ÷ 21,500 subscribers
Avg views / post
13,200
2 posts measured
Reaction rate
2.51%
reactions ÷ views · ER floor
Posts in window
2
of 7 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 16 August 2026
Posts held7 (30 May 202516 August 2026)
Views total26,300
Reactions total660
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 22:10 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.

Reaction mix

3,279 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 44.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎1,46444.6%
1,01330.9%
👍52616.0%
🔥1424.33%
👏782.38%
🥰561.71%

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 6 of the 7 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 3,279 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 30 May 2025 to 16 August 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

16 Aug 2026, 23:37 UTC≈13,400 views176 reactionsread 28 August 2026
File

Файл STANDLEO 3.5 ПК Гугл диск (если ошибка то качайте файл из поста) Яндекс Диск (для русских) ❗️❗️❗️СКАЧАТЬ С НОРМАЛЬНОЙ СКОРОСТЬЮ ТУТ STANDLEO.COM (еще там ежедневный промокод) Для запуска нужно: 0. Удалить все старые версии или папки! 1. Скачать архив 2. Извлечь папку с файлами 3. Запустить ярлык standleo.exe в папке 4. Выбрать Google аккаунт при входе. Если у вас проблема с этим, смотрите туториал Игра работает

133👏17👍14🔥8🥰4

16 Aug 2026, 14:57 UTC≈12,900 views484 reactionsread 28 August 2026

Промокод за задержку 3.5 тут @standleo_public_chat

👎38163🔥18👍11🥰11

11 Apr 2026, 09:00 UTC≈75,200 views536 reactionsread 28 August 2026
File

Файл STANDLEO 3.4 ПК Гугл диск (если ошибка то качайте файл из поста) Наш сайт (для русских) ❗️❗️❗️СКАЧАТЬ С НОРМАЛЬНОЙ СКОРОСТЬЮ ТУТ STANDLEO.COM (еще там ежедневный промокод) Для запуска нужно: 0. Удалить все старые версии или папки! 1. Скачать архив 2. Извлечь папку с файлами 3. Запустить ярлык standleo.exe в папке 4. Выбрать Google аккаунт при входе. Если у вас проблема с этим, смотрите туториал Игра работает н

350👎97👍44🔥28👏17

22 Dec 2025, 16:30 UTC≈195,000 views1,216 reactionsread 28 August 2026

❗Днем выйдет обновление 3.2 на ПК (на андроид уже вышло тут @standleoapk26) Там будет контент из новой версии Standoff 2 и подарок Включаем уведомления и ждем Наш чат с промокодами Бот для донатов @standleodonatebot Бот с промокодами @standleopromocode_bot

👎860👍167107🔥41🥰41

11 Jun 2025, 13:31 UTC≈206,000 views472 reactionsread 28 August 2026
Forwarded from @th3le0tgPhoto

❗️Завтра 12 июня в 18:00 по МСК выходит обновление 2.8 на iOS & Андроид & ПК Там будет все из 0.34.0, важные исправления и подарок (такой подарок будет только у нас в приватке и только первые 72 часа) Наш чат со сливами и новостями @standleo_public_chat

299👍60👎44🔥38👏31

1 Jun 2025, 09:29 UTC≈167,000 views395 reactionsread 28 August 2026

❗️У кого проблемы с заходом сделайте так: Зайдите в Windows defender - Защита от вирусов и угроз - параметры защиты от вирусов и других угроз - управление настройками - в самом низу исключения - добавить - папка - папка с игрой В игре нету вирусов, это античит которому нужно проверить файлы перед тем как впустить вас в игру, а операционная система такие действия блокирует

👍230👎8261👏13🔥9

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

Posts edited after publishing

@standleo_exe 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.

First edit seen
17 August 2026
Most recent edit
17 August 2026

Forward network

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.

Mentions

Named by 6 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.

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

“STANDLEO PC” (@standleo_exe), 21,500 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/standleo_exe.

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.