Telegram RegisterThe public register of Telegram
Telegram profile photo for Arsip Twilight Force

Channel

Arsip Twilight Force

@ARSIPFORC

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

3subscribers

+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-1002162063297
TypeChannel
Username@ARSIPFORC
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live24 August 2026
Measurements held2
On Telegramt.me/ARSIPFORC

Growth

38 August 2026 — 3 subscribers13 August 2026 — 3 subscribers8 August 202613 August 2026
2 measurements spanning 5 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 14:323no change
8 Aug 2026, 09:013first reading

Engagement

17 posts held, back to 8 December 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 17 posts for this entry, the most recent from 9 December 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Links
11

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

9 Dec 2024, 09:29 UTC77 viewsread 13 August 2026

──── 𝗦𝗨𝗥𝗔𝗧 𝗜𝗭𝗜𝗡 𝗟𝗘𝗣𝗔𝗦 𝗔𝗧𝗕 ──── Tanggal : 00/00/0000 Perihal : Pelepasan Atribut Yth All Foi @TWILIGHTFORCEOFC Dengan hormat, ㅤㅤBersamaan dengan adanya surat ini, saya ingin meminta izin kepada seluruh foi @TWILIGHTFORCEOFC untuk saya agar diperbolehkan untuk melepas atribut resmi squad. Berikut data dan alasan : ⚚ nickname : ⚚ usename : ⚚ divisi : ⚚ durasi : dari 00/00/0000 hingga 00/00/0000 ⚚ alasan : ㅤㅤ…

9 Dec 2024, 09:29 UTC75 viewsread 13 August 2026

──── 𝗦𝗨𝗥𝗔𝗧 𝗜𝗭𝗜𝗡 𝗠𝗢𝗩𝗘 𝗔𝗖𝗖 ──── Tanggal : 00/00/0000 Perihal : Pemberitahuan Pergantian Akun Yth All Foi @TWILIGHTFORCEOFC Dengan hormat, ㅤㅤBersamaan dengan adanya surat ini, saya ingin menginformasikan kepada seluruh foi @TWILIGHTFORCEOFC bahwa saya memiliki akun baru. Berikut data dan alasannya : ⚚ nickname : ⚚ usename lama : ⚚ usename baru : ⚚ divisi : ⚚ alasan : ㅤㅤDengan dilampirkannya surat ini, saya h…

9 Dec 2024, 09:29 UTC78 viewsread 13 August 2026

──── 𝗦𝗨𝗥𝗔𝗧 𝗜𝗭𝗜𝗡 𝗥𝗘𝗦𝗧 / 𝗛𝗜𝗔𝗧 ──── Tanggal : 00/00/0000 Perihal : Permohonan Rest/Hiat Yth All Foi @TWILIGHTFORCEOFC Dengan hormat, ㅤㅤBersamaan dengan adanya surat ini, saya ingin meminta izin kepada seluruh foi @TWILIGHTFORCEOFC untuk meminta waktu rest/hiat sejenak. berikut data, durasi, dan alasan : ⚚ nickname : ⚚ usename : ⚚ divisi : ⚚ durasi : dari 00/00/0000 hingga 00/00/0000 ⚚ alasan : ㅤㅤDengan dilam…

9 Dec 2024, 09:28 UTC113 viewsread 13 August 2026

─── 𝗦𝗨𝗥𝗔𝗧 𝗣𝗘𝗡𝗚𝗨𝗡𝗗𝗨𝗥𝗔𝗡 𝗗𝗜𝗥𝗜 ─── Tanggal : 00/00/0000 Perihal : Pengunduran Diri Yth All Foi @TWILIGHTFORCEOFC Dengan hormat, ㅤㅤBersamaan dengan adanya surat ini, saya ingin meminta izin kepada seluruh foi @TWILIGHTFORCEOFC untuk mengundurkan diri dari squad. berikut data dan alasan saya : ⚚ nickname : ⚚ usename : ⚚ divisi : ⚚ alasan : ㅤㅤSaya mengirimkan surat ini dalam kondisi sadar dan tanpa paksaan piha…

9 Dec 2024, 09:26 UTC113 viewsread 13 August 2026
File

⌞ --------------- 𝗔𝗧𝗥𝗜𝗕𝗨𝗧 𝗔𝗗𝗠𝗜𝗡 ---------------⌝ ⌗ Put dn : pakai sesuai posisi (wajib) - ғorc ᶠᵒ - ғorc ᶜᶠᵒ - ғorc ᵒʷⁿ - ғorc ᶜᵒʷⁿ - ғorc ˡᵉᵃᵈ - ғorc ᶜᵒʳᵉ - ғorc ᵗᵉᵃᵐ [Tap auto copy ] ⌗Put dn : #FORCESLY (opsional) [ Tap auto copy ] Jika tidak bisa mengedit bisa minta bantuan @OFCTWILIGTH_BOT NB : Idc boleh dipakai di pfp (tidak wajib dijadikan utama) atau di channel khusus atribut tapi pemakaian put dn wajib unt…

9 Dec 2024, 08:19 UTC102 viewsread 13 August 2026

⌞ ---------- 𝗥𝗨𝗟𝗘𝗦 𝗨𝗧𝗔𝗠𝗔 𝗔𝗗𝗠𝗜𝗡 -----------⌝ ⌗ MINAT DIBARENGI NIAT YANG KONSISTEN ⌗ All gender dan all chara allowed. menggunakan akun utama dan bukan akun clone/mata-mata. ⌗ Dilarang melepas pdn selama tidak ada surat lepas pdn ⌗ Paham dengan pekerjaan divisi yang diambil ⌗ Betanggungjawab dan bisa menjadi contoh bagi member ⌗ Mampu membagi waktu antara RP dan RL dengan baik ⌗ Siap menerima kritikan, saran, m…

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

Citation-graph rank

Citation-graph rank — 1,604,124 of 1,624,174entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

BUBAR - 𝐓𝐖𝐈𝐋𝐈𝐆𝐇𝐓 𝐅𝐎𝐑𝐂𝐄
@TWILIGHTFORCEOFC · 2601 post

Names

Channels on the register whose handles appear in this channel's posts.

BUBAR - 𝐓𝐖𝐈𝐋𝐈𝐆𝐇𝐓 𝐅𝐎𝐑𝐂𝐄
@TWILIGHTFORCEOFC · 2604 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Arsip Twilight Force” (@ARSIPFORC), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ARSIPFORC.

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.