Posted without readable text
Signed angular imp

Channel
@angular_imp_tg
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
144subscribers
-7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002256432574 |
|---|---|
| Type | Channel |
| Username | @angular_imp_tg |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/angular_imp_tg |
Other / unclassifiable — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 15:38 | 144 | -1 |
| 2 Sept 2026, 19:59 | 145 | +1 |
| 27 Aug 2026, 01:56 | 144 | -2 |
| 21 Aug 2026, 00:03 | 146 | -3 |
| 14 Aug 2026, 23:37 | 149 | -2 |
| 8 Aug 2026, 19:32 | 151 | no change |
| 6 Aug 2026, 18:49 | 151 | first reading |
20 posts held, back to 30 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 1 page 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 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
193 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 36.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249138016458410136 | 70 | 36.3% | |
| ❤ | 38 | 19.7% | |
| 🔥 | 21 | 10.9% | |
| custom 5249128696379375384 | 17 | 8.81% | |
| 💋 | 15 | 7.77% | |
| custom 5237836535868442360 | 13 | 6.74% | |
| custom 6003762421745851461 | 7 | 3.63% | |
| 💔 | 5 | 2.59% | |
| 😱 | 3 | 1.55% | |
| 🥰 | 3 | 1.55% | |
| 🙏 | 1 | 0.518% |
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 16 of the 20 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 193 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 July 2026 to 8 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.
Posted without readable text
Signed angular imp
Я ЗНАЮ ЧТО ВЫ БЕЗ ПОНЯТИЯ КТО ТАКАЯ ШАНГРИЛА НО НО ГОЛОСУЙТЕ ЗА НЕЁ–
Signed angular imp
Если вы вдруг подумали что админ зажрался и хочет денежек срубить, знайте, что все деньги уйдут на антивирус 🙄🙄🙄 (она увидела крутой мерч по рв) #щитпост
custom 52491380164584101364❤2💋1
Signed angular imp
под прошлым постом не флудить пж (я почищу чуть чуть прост чтоб примеры нацти было легче соррь) #щитпост
❤3custom 52491286963793753842custom 52491380164584101361
Signed angular imp
• угловатый чёрт • pinned a photo
КОММИШКИ ОТКРЫТЫ!!! (без слотов, вот просто открыты прикиньте) Примеры в комментах. Буду рада репосту :3 Писать сюды -> @angular_imp #инфа
❤10custom 52491380164584101363
Signed angular imp
Она становится всё ближе спасайте кто мо
custom 524913801645841013614🥰3😱3❤1
Channel photo updated
А вы знали что одному из самых старых клипов на моем твиче уже 2 года? Я тоже не знала- #щитпост
custom 524913801645841013610
Signed angular imp
Блл это должно было быть в отложке... Ладно будут ночные посты как всегда #щитпост
custom 52491380164584101364
Signed angular imp
Запись стрима с таймкодами! Раздумываю над тем чтобы сделать урезанную версию этого видео... Но пока так ":3 https://www.youtube.com/watch?v=u6KaTrfSlQs #видео
custom 52491380164584101364
Signed angular imp
Спасибо всем за стрим! И отдельно разрабу за то что так внезапно пришёл и поделился инсайдами ;3
🔥13💋4custom 52491380164584101363❤2
Signed angular imp
Showing the 12 most recent of 20 posts we hold for @angular_imp_tg. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“• угловатый чёрт •” (@angular_imp_tg), 144 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/angular_imp_tg.
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.