Channel
@Angelski999
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
574subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002395659121 |
|---|---|
| Type | Channel |
| Username | @Angelski999 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 November 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 1 |
| On Telegram | t.me/Angelski999 |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 23:22 | 574 | first reading |
10 posts held, back to 17 October 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.
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 7 November 2026 |
|---|---|
| Posts held | 10 (17 October 2026 – 7 November 2026) |
| Views total | 2,936 |
| Reactions total | 167 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 23:22 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 7 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 2 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.
167 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 26.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5424964043297303089 | 44 | 26.3% | |
| ❤ | 44 | 26.3% | |
| custom 5397996197048757104 | 34 | 20.4% | |
| custom 5343951206223978707 | 24 | 14.4% | |
| custom 5334780708017679489 | 21 | 12.6% |
Custom emoji. 4 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 10 of the 10 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 167 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 17 October 2026 to 7 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: 0 of 10 posts held from the last 30 days (0%) 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).
Призы 1Футлока Russian street 2 Каска STG 3 наклейка+брелок 4 наклейка+брелок 5 наклейка+брелок Подписка на каналы обязательна! https://t.me/Angelski999 https://t.me/penisf3
custom 53439512062239787073custom 54249640432973030893❤2
Ссу на уебка
custom 53347807080176794895❤3custom 54249640432973030893
1й день без ультры разучился ходить
❤10custom 53347807080176794895custom 53979961970487571044
Ну что дороге друзья, сезон подошёл к концу, ультра отправляется на зимовку,хочу сказать спасибо всем кто был со мной,катался,помогал чинить пачифетку, всем желаю быстрой зимы.Контент не заканчивается,скоро будет большой розыгрыш и много всего интересного
custom 54249640432973030899custom 53347807080176794894custom 53979961970487571044
Сумашедшие стантики
❤9custom 53979961970487571045custom 54249640432973030895
Video, posted without a caption
❤5custom 54249640432973030895custom 53439512062239787074
Оно живое
❤5custom 53439512062239787072custom 54249640432973030892
Скоро будет контент, чем больше реакций,тем быстрее всё узнаете
custom 539799619704875710417custom 534395120622397870710custom 53347807080176794897custom 54249640432973030892
👍
custom 54249640432973030897❤4custom 53979961970487571044
😃👍
custom 54249640432973030898❤6custom 53439512062239787075
Showing the 10 most recent of 10 posts we hold for @Angelski999. 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.
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 1 registered channel — 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Ангельский 999.0” (@Angelski999), 574 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/Angelski999.
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.