9 Jun 2023, 16:02 UTC341 viewsread 13 August 2026
Sticker
Sticker, posted without a caption
Channel
ARCHIVE LION
@lsgkarship
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
3subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001637326873 |
|---|---|
| Type | Channel |
| Username | @lsgkarship |
| Created | Between 1 December 2021 and 28 December 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 22 August 2026 |
| On Telegram | t.me/lsgkarship |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 10:24 | 3 | no change |
| 13 Aug 2026, 18:47 | 3 | first reading |
Engagement
20 posts held, back to 28 December 2022 — 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 9 June 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
9 Jun 2023, 16:02 UTC389 viewsread 13 August 2026
𝗥𝗨𝗟𝗘𝗦 𝗔𝗗𝗠𝗜𝗡 SEKRETARIS ━━━━━━━━━━━━━━━━━━ • niat bukan hanya sekedar minat • Dapat menguasai bidang sekretaris. • Memiliki attitude yang baik, ramah, sopan dan berbaur. • Wajib & siap mengerjakan tugas yang di berikan. • Cekatan, talk active, tidak lelet, dan insiatif. • Dapat membagi waktu Rl & Rp • Dapat bekerja di bawah tekanan. • Dapat membackup absen dan data kerja team. • Tidak dalam masa l/h/d ━━…
28 Dec 2022, 15:28 UTC≈1,070 viewsread 13 August 2026
Sticker
Sticker, posted without a caption
28 Dec 2022, 15:27 UTC≈1,140 viewsread 13 August 2026
𝐅𝐎𝐑𝐌𝐀𝐓 𝐏𝐄𝐍𝐃𝐀𝐅𝐓𝐀𝐑𝐀𝐍 : Nama + Username : Divisi yang diambil : Ch yang dipegang ( sebutkan ) + divisi : Khusus divisi edit sertakan minimal 3 contoh editannya. SEND KE : @dedelsgk_bot note : sistem wawancara.
28 Dec 2022, 13:55 UTC≈1,250 viewsread 13 August 2026
Sticker
Sticker, posted without a caption
28 Dec 2022, 13:55 UTC≈1,240 viewsread 13 August 2026
𝗥𝗨𝗟𝗘𝗦 𝗔𝗗𝗠𝗜𝗡 𝐄𝐃𝐈𝐓/𝐊𝐎𝐍𝐓𝐄𝐍 ━━━━━━━━━━━━━━━━━━ • Niat tidak hanya diawal. • Nolep. • Bisa membagi waktu antara rp/rl. • Bukan bagian dari sq perusuh. • Tidak dalam masa L/H/D. • Dapat berbaur dengan foi maupun member. • Bisa mengedit dan mempunyai banyak ide konten. ━━━━━━━━━━━━━━━━━━
28 Dec 2022, 13:55 UTC≈1,250 viewsread 13 August 2026
Sticker
Sticker, posted without a caption
28 Dec 2022, 13:55 UTC≈1,280 viewsread 13 August 2026
𝗥𝗨𝗟𝗘𝗦 𝗔𝗗𝗠𝗜𝗡 𝐌𝐏𝐏𝐒 ━━━━━━━━━━━━━━━━━━ • Niat tidak hanya diawal. • Bisa membagi waktu antara rp/rl. • Mengerti sistem mpps (media partner partner ship) dengan baik. • Bukan bagian dari sq perusuh. • Tidak dalam masa L/H/D. • Dapat berbaur dengan foi maupun member. • aktif serta dapat menghandle pembersihan, mengganti data yang keliru dan siap menanggung resiko jika lalai. • Dapat membuat beberapa data/list untuk konfi…
28 Dec 2022, 13:55 UTC≈1,230 viewsread 13 August 2026
Sticker
Sticker, posted without a caption
28 Dec 2022, 13:55 UTC≈1,220 viewsread 13 August 2026
𝗥𝗨𝗟𝗘𝗦 𝗔𝗗𝗠𝗜𝗡 𝐒𝐅𝐒 ━━━━━━━━━━━━━━━━━━ • Niat tidak hanya diawal. • Nolep. • Bisa membagi waktu antara rp/rl. • Mengerti sistem sfs dan pfp dengan baik. • Bukan bagian dari sq perusuh. • Tidak dalam masa L/HD. • Dapat berbaur dengan foi maupun member. • Sanggup sfs minimal 35s perhari dan pfp 20 format sehari ━━━━━━━━━━━━━━━━━━
28 Dec 2022, 13:53 UTC≈1,480 viewsread 13 August 2026
Sticker
Sticker, posted without a caption
28 Dec 2022, 13:53 UTC≈1,520 viewsread 13 August 2026
𝗥𝗨𝗟𝗘𝗦 𝐈𝐍𝐓𝐈 ━━━━━━━━━━━━━━━━━━ • Diutamakan niat bukan sekedar minat. • Bisa membagi waktu antara rp atau rl. • Asik, mudah berbaur, dan dapat ikut serta meramaikan, tidak baperan. • Paham dengan divisi yang diambil. • Dapat memahami minimal 1 divisi lain. • Dapat dipercaya. • Tidak gila jabatan dan tidak anti kritik. • Mempunyai banyak ide. • Dapat beropini dengan bahasa yang baik dan sopan dan memiliki argumen yang…
Showing the 12 most recent of 20 posts we hold for @lsgkarship. 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,600,553 of 1,623,166entries 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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@lsgkarship named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@dedelsgk_bot
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“ARCHIVE LION” (@lsgkarship), 3 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/lsgkarship.
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.