@ydilblin
Signed แย่ลง

Channel
@angelsjosh
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
26subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001670087560 |
|---|---|
| Type | Channel |
| Username | @angelsjosh |
| Description | КАМБЭК БРО |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/angelsjosh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 23:16 | 26 | no change |
| 14 Aug 2026, 23:03 | 26 | first reading |
17 posts held, back to 30 December 2023 — 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 pageof 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 17 posts for this entry, the most recent from 13 January 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 August 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.
571 reactions across 10 posts, in 20 distinct kinds. The most used accounts for 18.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5424861556787659034 | 104 | 18.2% | |
| custom 5424888636556458744 | 86 | 15.1% | |
| custom 5424942693014847225 | 73 | 12.8% | |
| custom 5319239579310506425 | 57 | 9.98% | |
| custom 5467427375635507008 | 44 | 7.71% | |
| custom 5348096403715404856 | 40 | 7.01% | |
| custom 5199751398702464530 | 35 | 6.13% | |
| custom 5474247491643779536 | 35 | 6.13% | |
| custom 5377820042714950146 | 18 | 3.15% | |
| custom 5352707686762827383 | 16 | 2.80% | |
| custom 5249310571064477109 | 13 | 2.28% | |
| custom 5469723074309928582 | 11 | 1.93% | |
| custom 5305572903180321520 | 10 | 1.75% | |
| custom 5379557786482911034 | 7 | 1.23% | |
| custom 5458544739022293889 | 7 | 1.23% | |
| custom 5467433006337634924 | 6 | 1.05% | |
| custom 5240187218714183271 | 5 | 0.876% | |
| custom 5411511462696863656 | 2 | 0.35% | |
| custom 5357250048470038177 | 1 | 0.175% | |
| custom 5411135932231334742 | 1 | 0.175% |
Custom emoji. Every 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 counts beside them areTelegram’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 17 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 571reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 30 December 2023 to 13 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
@ydilblin
Signed แย่ลง
погнал ч
Signed gnbanch'
еду по иоскве, как в Majestic RP 🌟 ты не могла летать, я покажу, как делать это. давай потратим все, давай, ведь я молодой 💣 мне хорошо одному, но, думаю, что мне лучше с тобой. 🤍
custom 54585447390222938894custom 54248886365564587441custom 54249426930148472251
Signed gnbanch #fucksm
прекрасный. 🪮
custom 54248886365564587445custom 54248615567876590343custom 54249426930148472253custom 54585447390222938893
Signed แย่ลง.
скромный, н!ебовый, 🖤 0̶балденный не!ъебенный, я богатый, я пизд!тый, все вокруг меня хотят. хейтер̶ы пиз!ят на меня что то в интернете, но когда и̶х вижу в жизни они похожи на ко̶тят. 🌟
custom 542486155678765903424custom 542488863655645874415custom 524931057106447710913custom 54249426930148472257custom 53192395793105064255custom 53778200427149501465custom 53527076867628273834
Signed кошатник. tfn.
уютный. 🫶
custom 542494269301484722520custom 542486155678765903416custom 542488863655645874415custom 53192395793105064259custom 53527076867628273835custom 53778200427149501464
Signed кошатник. tfn.
Sticker, posted without a caption
Signed #dnck'
🎀 21, wnk.
custom 531923957931050642521custom 542486155678765903415custom 542494269301484722515custom 54248886365564587449custom 53527076867628273831custom 53778200427149501461
Signed #dnck'
Sticker, posted without a caption
Signed #dnck'
[⭐🩹🤍🌟] we used to be close, but people can go. . from people you know to people you don't. and what hurts the most is people can go. from people you know to people you don't.
custom 542486155678765903431custom 531923957931050642517custom 542488863655645874416custom 542494269301484722511custom 53527076867628273834custom 53778200427149501464custom 53572500484700381771
Signed #dnck'
Sticker, posted without a caption
Signed #dnck'
아빠보다는 엄마 엄마보다는 ... 고를 수 없잖아 Imma 둘 다 좋아해요!! 겨울에 입는 반팔 여름엔 전기장판 🌟 굳이 꼭 그래야 함 적당히 좀 해요
custom 542488863655645874425custom 542486155678765903415custom 542494269301484722513custom 530557290318032152010custom 52401872187141832715custom 53192395793105064254custom 53527076867628273831custom 53778200427149501461
Signed #dnck'
Showing the 12 most recent of 17 posts we hold for @angelsjosh. 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.
Citation-graph rank — 830,208 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 3 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.
@angelsjosh named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“ангел в аду.” (@angelsjosh), 26 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/angelsjosh.
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.