Telegram RegisterThe public register of Telegram
Telegram profile photo for collection

Channel

collection

@predikatif

On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

5subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001508840858
TypeChannel
Username@predikatif
Created6 July 2021 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live2 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/predikatif

Topic

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 2 October 2026 and assigned it the closest of 31 fixed categories, at 41% 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.

Growth

565.57 August 2026 — 6 subscribers12 August 2026 — 6 subscribers2 October 2026 — 5 subscribers7 August 20262 October 2026
3 measurements spanning 56 days, net -1. 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 5–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 12:175-1
12 Aug 2026, 21:176no change
7 Aug 2026, 18:346first reading

Engagement

15 posts held, back to 6 July 2021 — 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 15 posts for this entry, the most recent from 10 April 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Feb 2024, 06:45 UTC68 viewsread 12 August 2026

ih si ganteng di bawa pulang😍 papayy @.guianheng kuu❤️

1 May 2023, 19:25 UTC134 viewsread 12 August 2026

ini masi ufs semua ya guys xixixi yu di cek harganya ke @imlucasbot

3 Jan 2023, 00:09 UTC153 viewsread 12 August 2026

hai, yg kepoin ch ini yu di cek list nya siapa tau ada yg nyantol, murmer lohh☺️

20 Mar 2022, 17:07 UTC299 viewsread 12 August 2026

halo, semua username yg ada disini ufs ya. ada yang bisa negtip, negteb, dan nett. untuk harga atau lebih jelasnya bisa hubungi langsung ke bot @imlucasbot

16 Mar 2022, 17:00 UTC442 viewsread 12 August 2026

𝐖𝐀𝐍𝐓 𝐓𝐎 𝐒𝐄𝐋𝐋 𝐔𝐒𝐄𝐑𝐍𝐀𝐌𝐄 ────── ·  ·  · ✦ ·  ·  · ────── 𝗡𝗖𝗧 ㅤᜊ ִֶָ @nakamotohyuta ㅤᜊ ִֶָ @dkery ㅤᜊ ִֶָ @suhjotnny ㅤᜊ ִֶָ @chittaphonloe ㅤᜊ ִֶָ @huangguafheng ㅤᜊ ִֶָ @huangguatheng ㅤᜊ ִֶָ @huangguaiheng ㅤᜊ ִֶָ @huangguazheng ㅤᜊ ִֶָ @huanggualheng ㅤᜊ ִֶָ @fuangguanheng ㅤᜊ ִֶָ @suangguanheng ㅤᜊ ִֶָ @muangguanheng ㅤᜊ ִֶָ @luangguanheng ㅤᜊ ִֶָ @duangguanheng ㅤᜊ ִֶָ @huganghendery ㅤᜊ ִֶָ @huangguanhc…

15 Mar 2022, 21:16 UTC263 viewsread 12 August 2026

ㅤ❐ Username SOLD ! ──── ·  ·  · ✦ ·  ·  · ──── @.chaehyungwen @.chaehyungwrn @.chaehzungwon @.chaehyungwvn @.parvjisung @.brightcvachirawit @.uparkchanyeol @.lzetaeyong @.kanghyeawon @.jofhnny @.suhjshnny @.youngheuma @.jeoneonwoo @.jungjyeffrey @.uanloving @.kimminvyu @.suhjohnrny @.suhjosnny @.najeaemin @.joihnny @.drrummer @.wtonjok @.ccabe @.konwoo @.guianheng

Showing the 12 most recent of 15 posts we hold for @predikatif. 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 47 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. The 19 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“collection” (@predikatif), 5 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/predikatif.

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.