Telegram RegisterThe public register of Telegram

Channel

LITERASI LNC

@infoLNC

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

389subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002420096203
TypeChannel
Username@infoLNC
Description@CLAIM_CNIT x @PISCESPP
Created6 October 2024measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/infoLNC

Growth

3896 Aug 2026, 22:38 — 389 subscribers6 Aug 2026, 22:46 — 389 subscribers6 Aug 2026, 22:386 Aug 2026, 22:46
2 measurements taken within a single day. 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 388–390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 22:46389no change
6 Aug 2026, 22:38389first reading

Engagement

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

What this channel posts

Photos
1

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

8 Jun 2025, 09:09 UTC≈3,820 viewsread 6 August 2026

format pp @claim_cnit username : usn ch/gc : tanggal : format rent admin username : req tittle : durasi : payment : send ke @lnchelpbot

8 Jun 2025, 09:06 UTC≈3,820 viewsread 6 August 2026
Photo

PAID PROMOTE @CLAIM_CNIT Rp 10.000 / hari RENTAL ADMIN @CLAIM_CNIT Rp 5.000 / 100kc (perhari)

31 Dec 2024, 17:24 UTC≈10,400 viewsread 6 August 2026

Yang bisa kirim chat saat modam hanya admin inti saja [@llurgy @bbtterflyz @masculines]

10 Oct 2024, 17:52 UTC≈17,600 viewsread 6 August 2026

cibu : 1kc goceng : 5kc ceban : 10kc noban : 20kc selawe : 25kc triban : 30kc tribanceng : 35kc fourban : 40kc gocap : 50kc cepe : 100kc nopek : 200kc tlipek : 300kc fourpek : 400kc gopek : 500kc cejuta : 1jtc tj : terima jadi

6 Oct 2024, 02:20 UTC≈16,500 viewsread 6 August 2026

LITERASI RULES 1. Jangan mengundang war maupun rusuh, apalagi saling sindir. Gunakan bahasa yang baik dan sopan 2. Dilarang promosi dalam bentuk apapun, baik tag ch store base maupun mengajak ke rc. 3. Berikan jeda apabila kirim pesan agar tidak spam dan tetap kondusif. 4. Dilarang WTS. 5. Dilarang malak hingga ke rc, jika ada harap laporkan ke bot. 6. Dilarang nimbrung menggunakan channel 7. Jangan OOT 8. Kr

Showing the 9 most recent of 9 posts we hold for @infoLNC. 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 — 830,560 of 1,151,006entries 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.

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

“LITERASI LNC” (@infoLNC), 389 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/infoLNC.

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.