Channel
@spillanjeizan
On this record: Growth · Engagement · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003923457310 |
|---|---|
| Type | Channel |
| Username | @spillanjeizan |
| Created | Between 1 April 2026 and 4 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 5 times, most recently 17 September 2026 |
| On Telegram | t.me/spillanjeizan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 02:03 | 3 | no change |
| 14 Aug 2026, 14:46 | 3 | first reading |
16 posts held, back to 4 May 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 16 posts for this entry, the most recent from 4 May 2026. An engagement rate over an empty window would be a number about nothing.
Kami harap dari kejadian ini, saudara Jeizan bisa belajar dan evaluasi diri sendiri agar lebih baik kedepannya. Apabila ingin dihargai, belajarlh menghargai sesuatu dulu, karena tidak ada sesuatu yang datang dengan instan.
Kalau memang sejak awal kamu gk siap, gk sanggup dengan tanggungjawab sebagai multifungsi, kamu bisa bilang dan komunikasikan ke tim kami. Tapi apa yg kamu lakukan? Menghilang dan malah membocorkan internal.
kami tau bahwa anda memiliki kesibukan di dunia nyata dan waktu anda tidak disini saja. tapi apa salahnya membuat klarifikasi dan surat permohonan maaf setelah apa yang anda lakukan? dan mengatakan bahwa anda ingin menjatuhkan nama instansi kami? tidak pantas anda seperti itu, anda di terima disini untuk berkerja dan petinggi mempercayai anda namun sikap anda sangat buruk selama disini? masuk ke multifungsi hanya ing…
Sticker, posted without a caption
Kemudian saat kami pertanyakan pada mediasi di tanggal 1 kemarin. Pada awalnya saudara Jeizan beralasan sibuk bolak balik rs. Tetapi kemudian dia tiba tiba mengatakan bahwa dia sudah terlalu sibuk menyiapkan hal hal terkait instansi lain yang mana menyebabkan kurangnya kehadiran dia di CHESSTA. Dari pernyataan diatas, kembali didapati sebuah tanggapan yang berujung blunder dari saudara Jeizan. Padahal pun jika yang …
Photo, posted without a caption
Selain itu, saudara Jeizan hanya mengisi 2 job dalam kurun waktu sebulan. Padahal list job di bulan April lumayan banyak di CHESSTA, dan kami sendiri sangat membutuhkan kehadiran saudara Jeizan. Namun saudara Jeizan tidak pernah ada dalam momen momen tersebut
Kemudian pada job party, kami sudah membagikan job mulai dari 13 april untuk acara ditanggal 16, yang mana rentang waktunya 4 hari. dan tim kami juga sudah mengingatkan mulai dari tanggal 14 (seperti pada tangkapan layar di atas). Bahkan saat gladi di tanggal 15, saudara Jeizan masih juga belum mengirimkan teks yang hanya tinggal copy dan meletakkan nama + foto. Dan diketahui kemudian saudara Jeizan mengirimkan teks …
Photo, posted without a caption
Photo, posted without a caption
Disini juga sudah tertera jadwal pfp (karena jeizan mendapat tugas pfp). Jadwal ini dibagikam dengan metode siapa cepat dia dapat. Tim kami juga tidak memberatkan untuk bertukar jadwal satu sama lain asalkan bilang. Tetapi pada pelaksanaannya, jeizan hanyamengerjakan 1 kali pfp dari 8 tugas yang harusnya dia lakukan selama april lalu.
Pada tangkapan layar ini, petinggi sudah membagi tugas mulfung pada bulan april sesuai dengan kebutuhan divisi masing masing. Dan apabila belum mengerti, para tim juga bersedia mengajarkan perlahan.
Showing the 12 most recent of 16 posts we hold for @spillanjeizan. 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.
Named by 1 registered channel — 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“.” (@spillanjeizan), 3 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/spillanjeizan.
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.