Telegram RegisterThe public register of Telegram

Channel

Gepeng’s!

@Gepiess

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

12subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003348385714
TypeChannel
Username@Gepiess
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/Gepiess

Growth

128 August 2026 — 12 subscribers12 August 2026 — 12 subscribers8 August 202612 August 2026
2 measurements spanning 3 days. 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 05:3112no change
8 Aug 2026, 18:4512first reading

Engagement

20 posts held, back to 19 June 2026the 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 20 posts for this entry, the most recent from 21 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Links
2

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

Recent posts

21 Jun 2026, 12:07 UTC301 viewsread 12 August 2026

WARNING CROSSOVER Digunakan untuk menfess yang membahas atau melibatkan media maupun fandom di luar ranah 2D. Jenis fandom atau media yang di crossover wajib dicantumkan. CONTOH: WARNING CROSSOVER JUJUTSU KAISEN × KPOP ✅ CW // SPOILER BLUE LOCK , CROSSOVER JPOP ✅ CONTOH MENFESS CW // SPOILER BLUE LOCK , CROSSOVER JPOP ✅ (send foto K &team cosplay Nagi) #Gent aDUHHH GANTENG BANGET PACAR SENDER COSPLAY PACAR SENDE

21 Jun 2026, 10:18 UTC283 viewsread 12 August 2026

WARNING PAIRING Digunakan untuk menfess yang membahas ship atau pair tertentu. Wajib mencantumkan jenis pair: M/F, F/M, M/M, atau F/F. Nama pair dapat ditulis menggunakan nama karakter maupun nama ship. CONTOH: WARNING PAIR M/M PHAIDEI ✅ WARNING PAIR M/F BLADE KAFKA ✅ WARNING PAIR BXG LUFFY NAMI ❌ CW // M/M PAIRING SATOSUGU ❌ CONTOH MENFESS WARNING PAIR M/F BLADE KAFKA ✅ (send video editan Blade Kafka) #Gepeng

21 Jun 2026, 09:55 UTC269 viewsread 12 August 2026

PENGGUNAAN LEBIH DARI SATU WARNING Apabila terdapat lebih dari satu jenis warning dalam satu menfess, setiap warning ditulis pada baris yang berbeda. Hal ini bertujuan agar informasi lebih mudah dibaca dan tidak terlewat. Ketentuan ini berlaku untuk CW, TW, WARNING PAIR. CONTOH: CW // HARSHWORD TW // DEATH ✅ CW // SPOILER DR. STONE WARNING PAIR M/F SENKU KOHAKU ✅ CW // SPOILER CHAINSAW MAN TW // BLOOD , DEATH ✅

21 Jun 2026, 08:41 UTC260 viewsread 12 August 2026

CW SPOILER & LEAKS Penulisan judul karya harus ditulis secara lengkap dan tidak diperbolehkan menggunakan singkatan untuk menghindari kesalahpahaman. Ketentuan ini berlaku untuk anime, manga, manhwa, manhua, light novel, game, dan sejenisnya. Spoiler: Informasi dari konten yang telah dirilis secara resmi, seperti alur cerita, ending, kematian karakter, dan sejenisnya. Leaks: Informasi atau konten yang belum dirili

20 Jun 2026, 10:15 UTC254 viewsread 12 August 2026

TRIGGER WARNING (TW) Violence & Physical Harm Violence, abuse, physical assault, bullying, torture, murder, and others. Blood & Gore Blood, bleeding, gore, graphic injuries, exposed wounds, and others. Death Death, dying, dead bodies, mass death, animal death, and others. Mental Health Anxiety, panic attacks, depression, suicidal thoughts, self-harm, and others. Accidents & Disasters Car accidents, plane crashes

20 Jun 2026, 10:14 UTC351 viewsread 12 August 2026

TRIGGER WARNING (TW) MEANS TW digunakan untuk memperingatkan adanya topik sensitif yang dapat membuat sebagian orang merasa tidak nyaman atau terganggu secara emosional. TW membantu pembaca memutuskan apakah ingin melanjutkan membaca menfess tersebut atau tidak. CONTOH: TW // MENTIONING DEATH ✅ TW // GORE , BLOOD ✅ tw // blood ❌ TW / GORE ❌ TW // blood ❌ TW // Death ❌ TW // GORE, BLOOD ❌ TW // DEATH. ❌ CONTOH MEN

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

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

“Gepeng’s!” (@Gepiess), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Gepiess.

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.