Telegram RegisterThe public register of Telegram
Telegram profile photo for @rynjin

Channel

@rynjin

@Proofrynjin

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2subscribers

-1 since we began measuring on 6 October 2026

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

Register entry

Telegram ID-1004300345876
TypeChannel
Username@Proofrynjin
Created19 June 2026 — measured — dated from the channel’s first post
First recorded6 October 2026
Last confirmed live7 November 2026
Measurements held2
Confirmed unchanged5 times, most recently 7 November 2026
On Telegramt.me/Proofrynjin

Growth

232.56 October 2026 — 3 subscribers10 October 2026 — 2 subscribers6 October 202610 October 2026
2 measurements spanning 4 days, net -1. 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–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 21:192-1
6 Oct 2026, 21:223first reading

Engagement

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

Recent posts

6 Oct 2026, 04:14 UTCviews —

@rynjin pinned «HFW. Good afternoon everyone, siapapun yang keep @rynjin tolong balikin ke @tinnapate proof nya bisa diliat di @Proofrynjin Yang mau bantu minta tolong subscribe channelnya terus tolong pakai "return @rynjin to @tinnapate" yaa, thank you so much.»

6 Oct 2026, 04:13 UTC172 viewsread 6 October 2026

awalnya sempet gua pake di akun ini @Wjamesu terus mau gua keep lagi tu di ch dan posisinya wifi gua tiba tiba gangguan jadi ada sekitar 5 menit itu id ga di keep sama sekali, terus gua coba keep lah di ch masi muter-muter, gua pake lagi di akun ini @Wjamesu malah limit usn, gua tunggu lah sekitar 15menitan tetep gabisa tuh di keep, jadi gua coba mode ulang hp gua dan pas gua mau pake udah di keep sama @rynjin

6 Oct 2026, 04:08 UTC169 viewsread 6 October 2026
Photo

bukti siang tadi gua abis beli di https://t.me/RumahThai @RumahThaiBot

6 Oct 2026, 04:00 UTC165 viewsread 6 October 2026

⚠️ Channel Transferred to You: @rynjin The previous owner of channel @rynjin @rynjin has transferred it to you. You are the new channel owner and are responsible for its contents. If this was a mistake or you do not wish to own this channel, you can reject the transfer by simply pressing 'Reject Channel Transfer' below. If this was intended, no further action is required.

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

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.

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

“@rynjin” (@Proofrynjin), 2 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/Proofrynjin.

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.