Telegram RegisterThe public register of Telegram
Telegram profile photo for Arsip Rover.

Channel

Arsip Rover.

@langschive

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

—subscribers

Risers and fallers across the register.

Register entry

Telegram ID-1001913455059
TypeChannel
Username@langschive
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live31 August 2026
Measurements held0
On Telegramt.me/langschive

Growth

Growth history is still building. We hold no measurements for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Engagement

10 posts held, back to 5 November 2025 — 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 10 posts for this entry, the most recent from 5 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
32

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

Showing the 10 most recent of 10 posts we hold for @langschive. 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.

Mentions

Named by 2 registered channels — 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.

Better than ur ex
@sexiestmff1 post‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎Ruru bilek
@Veyy13s · 241 post

Names

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

Keep.
@Aclhaitham · 11 postEarl K.
@Alipedem · 21 post.
@moondlicth · 11 post

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. This entry holds no subscriber measurement yet, so the line below cites the entry itself.

“Arsip Rover.” (@langschive). Telegram Register, tgregister.com/channel/langschive.

No subscriber measurement is held for this entry yet, so there is no history to download — a download that asserted zero readings would be a false statement, not an empty one.