Telegram RegisterThe public register of Telegram
Telegram profile photo for payment @pKacak

Channel

payment @pKacak

@affraidh

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

15subscribers

+0 since we began measuring on 20 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003275778396
TypeChannel
Username@affraidh
CreatedBetween 1 October 2025 and 6 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 October 2026
Last confirmed live2 November 2026
Measurements held2
On Telegramt.me/affraidh

Growth

1520 Oct 2026, 08:47 — 15 subscribers20 Oct 2026, 09:22 — 15 subscribers20 Oct 2026, 08:4720 Oct 2026, 09:22
2 measurements taken within a single day. 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 14–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Oct 2026, 09:2215no change
20 Oct 2026, 08:4715first reading

Engagement

20 posts held, back to 6 December 2025 — 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 17 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3
Links
1

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

Reaction mix

16 reactions across 2 posts, in 8 distinct kinds. The most used accounts for 18.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5116648080787112958318.8%
custom 4904882772637648609212.5%
custom 5098265504796115765212.5%
custom 5116275208906343429212.5%
custom 5118861066981344121212.5%
custom 5172716095697584957212.5%
custom 5172843385643336752212.5%
custom 511615184885566755216.25%

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 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 2 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 16 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 6 December 2025 to 17 April 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

7 Mar 2026, 06:12 UTC779 viewsread 20 October 2026

payment wondr (bni), livin' ( mandiri ), bca bisa minta langsung rc yo

14 Jan 2026, 08:26 UTC≈1,250 viewsread 20 October 2026
Photo

👻 MODE : Steady . ‎يَنْسَابُ AURA──RAW & UNTOLD ( Vol ii ─ Deep Stillness ) ╰┈➤ [ QRISS ] literasi fee ✅ ╰┈➤ [ DANA ] ✅ ╰┈➤ [ SEABANK ] ✅ ╰┈➤ [ NITROSEEN ]✅ ╰┈➤ [ ALLOBANK ]✅ ╰┈➤ [ BRIMO ]✅ ╰┈➤ [ BANK JAGO ]✅ ╰┈➤ [ SHOPPE ] ╰┈➤ [ GOPAY ]✅ ╰┈➤ [ OVO ]✅ OWNER ✅ ╰┈➤ id : @pKacak ╰┈➤ back up acc : @jEmosi ╰┈➤ back up acc : - ╰┈➤ ch payment : @affraidh ╰┈➤ ch testie : @lampairan PRESENCE──CALM & UNTETHERED …

14 Jan 2026, 08:22 UTC733 viewsread 20 October 2026

MODE : Aware . ‎يُرَاقِبُ 🎵 FRAME──DEEP & TRACELESS ( Vol x ─ Silent Current ) OVO 💷 ╰┈➤ 082136056664 ╰┈➤ a.n F TONE──QUIET & UNRUSHED ( Vol ix ─ Silver Haze ) That One هُوَ بِثِقَتِهِ الْوَاثِقَة

14 Jan 2026, 08:21 UTC641 viewsread 20 October 2026

MODE : Aware . ‎يُرَاقِبُ 🎵 FRAME──DEEP & TRACELESS ( Vol x ─ Silent Current ) GOPAY 🛵 ╰┈➤ 082130223331 ╰┈➤ a.n Z TONE──QUIET & UNRUSHED ( Vol ix ─ Silver Haze ) That One هُوَ بِثِقَتِهِ الْوَاثِقَة

14 Jan 2026, 08:21 UTC509 viewsread 20 October 2026

MODE : Aware . ‎يُرَاقِبُ 🎵 FRAME──DEEP & TRACELESS ( Vol x ─ Silent Current ) SHOPPE 🏬 ╰┈➤ 088225345661 ╰┈➤ a.n F*** TONE──QUIET & UNRUSHED ( Vol ix ─ Silver Haze ) That One هُوَ بِثِقَتِهِ الْوَاثِقَة

14 Jan 2026, 08:16 UTC539 viewsread 20 October 2026

MODE : Aware . ‎يُرَاقِبُ 🎵 FRAME──DEEP & TRACELESS ( Vol x ─ Silent Current ) BANK JAGO 👻 ╰┈➤ 109919340637 ╰┈➤ a.n F**** TONE──QUIET & UNRUSHED ( Vol ix ─ Silver Haze ) That One هُوَ بِثِقَتِهِ الْوَاثِقَة

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

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

“payment @pKacak” (@affraidh), 15 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/affraidh.

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.