Channel
@Dufanarchive
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002050279969 |
|---|---|
| Type | Channel |
| Username | @Dufanarchive |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Dufanarchive |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 12:18 | 9 | no change |
| 7 Aug 2026, 14:45 | 9 | first reading |
20 posts held, back to 6 June 2024 — 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 20 posts for this entry, the most recent from 27 June 2024. An engagement rate over an empty window would be a number about nothing.
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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
8. Dilarang untuk menyebutkan produk boikot baik di dalam menfess atau pun di comment section, jika ingin menyebutkan brand boikot hanya bisa pada konteks "menanyakan alternatif" atau "menanyakan produk tersebut di boikot atau tidak" tetapi brand tersebut harus di sensor terlebih dahulu.
7. Dilarang menanyakan topik terkait username, kecuali hanya bertanya mengenai based on nya saja. Akan tetapi jika topik yang dikirimkan menyangkut tentang harga pasar, worth or not, lebih bagus username yang mana, atau yang berhubungan dengan menanyakan harga dan bagusnya suatu username untuk diperjualbelikan, maka menfess tersebut tidak bisa kami kirimkan.
HOW TO SEND MENFESS CORRECTLY
6. Saat ini, Dufan Fess belum memperbolehkan untuk menyebutkan username seseorang secara gamblang di menfess yang ingin dikirimkan ke base, kecuali jika ada sesi sesi khusus yang memperbolehkan kalian menyebutkan username seseorang secara gamblang contohnya sesi "Dart Pick"
5. Menfess yang berhubungan dengan fan art, fan site, editing, AI, dan sejenisnya yang merupakan hasil karya seseorang wajib menyertakan credit pada menfess yang ingin kalian kirimkan. Kami sangat melarang adanya klaim hasil karya orang lain menjadi hasil karyanya sendiri. Jika terdapat laporan/hal yang telah kami larang dikirimkan, maka kami akan menindak tegas seseorang yang telah mengirim menfess tersebut.
4. Dilarang mengirimkan menfess yang tidak ada konteksnya sama sekali atau hanya sekedar iseng/jahil saja ingin mengirim dan tidak terlalu jelas apa maksud dari menfess yang dikirimkan. Contoh: #Ponyo hi #Telour ndjsmxkdjcnsjdnjajdxjc :) #Telour eakk kenak #Ponyo p? Jika ada yang mengirimkan menfess seperti yang sudah dicontohkan di atas, maka mohon maaf menfess kalian tidak akan kami kirimkan. Menfess yang dikiri…
3. Untuk penyebutan "muse" bisa diganti dengan menggunakan kata "ava"
2. Dufan Fess melarang adanya Sell, Buy, dan Trade. Jika ada menfess yang mengandung salah satu atau ketiga hal tersebut, maka menfess tidak akan dikirimkan. Kecuali kalian konteksnya menanyakan rekomendasi store, baru diperbolehkan. Perlu diingat bahwa store yang direkomendasikan tidak boleh di tag langsung seperti ini '@DufanFess' cukup beri tanda titik '@.DufanFess' atau hanya sebutkan id store nya saja seperi ini…
1. Menfess yang akan kalian kirim harus sesuai dengan hashtag yang ada, contoh nya: #Telour aduh sumpah hari ini bete banget kucing aku kecebur got ✅ Ini benar yaa karena disitu posisinya kalian sedang curhat bahwa kucing kalian kecebur got. Tetapi jika menfess kalian mengandung sebuah pertanyaan, maka hashtag menfess yang digunakan bukan #Telour melainkan #Ponyo.
Sticker, posted without a caption
File, posted without a caption
File, posted without a caption
Showing the 12 most recent of 20 posts we hold for @Dufanarchive. 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.
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.
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.
“Dufan archive.” (@Dufanarchive), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Dufanarchive.
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.