Telegram RegisterThe public register of Telegram
Telegram profile photo for Archive milik @Ruootong.

Channel

Archive milik @Ruootong.

@oSangsang

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

2subscribers

+0 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1004474685016
TypeChannel
Username@oSangsang
Created11 July 2026measured — dated from the channel’s first post
First recorded31 August 2026
Last confirmed live9 September 2026
Measurements held2
On Telegramt.me/oSangsang

Growth

231 Aug 2026, 15:01 — 2 subscribers31 Aug 2026, 15:15 — 2 subscribers31 Aug 2026, 15:0131 Aug 2026, 15:15
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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 15:152no change
31 Aug 2026, 15:012first reading

Engagement

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

Recent posts

19 Jul 2026, 04:12 UTC17 viewsread 31 August 2026

ㅤㅤ𓉯ྀㅤ ꧇ Credit — 谢谢你! ᅠ⏝⏝ᅠ ֺ 藔 @Lenarine ᅠ⏝⏝ᅠ ֺ 藔 @Brezius ᅠ⏝⏝ᅠ ֺ 藔 @Tulipella ᅠ⏝⏝ᅠ ֺ 藔 @LEVI47H4N ᅠ⏝⏝ᅠ ֺ 藔 @Hamsterials ᅠ⏝⏝ᅠ ֺ 藔 @simfoyni ᅠ⏝⏝ᅠ ֺ 藔 @cawsite ᅠ⏝⏝ᅠ ֺ 藔 @zcatter ᅠ⏝⏝ᅠ ֺ 藔 @wishycraft ⏝⏝ᅠ ֺ 藔 @cleansevora ᅠ⏝⏝ᅠ ֺ 藔 @nekomami ᅠ⏝⏝ᅠ ֺ 藔 @arebonheur ᅠ⏝⏝ᅠ ֺ 藔 @ ᅠ⏝⏝ᅠ ֺ 藔 @ ᅠ⏝⏝ᅠ ֺ 藔 @

11 Jul 2026, 05:25 UTC27 viewsread 31 August 2026

ㅤㅤ𓉯ྀㅤ ꧇ Credit — 谢谢你! ᅠ⏝⏝ᅠ ֺ 藔 @Everclass ᅠ⏝⏝ᅠ ֺ 藔 @shamyse ᅠ⏝⏝ᅠ ֺ 藔 @Doulfy ᅠ⏝⏝ᅠ ֺ 藔 @typoplum ᅠ⏝⏝ᅠ ֺ 藔 @Mioonu ᅠ⏝⏝ᅠ ֺ 藔 @Inchedon ᅠ⏝⏝ᅠ ֺ 藔 @Theskiest ᅠ⏝⏝ᅠ ֺ 藔 @ctwine ᅠ⏝⏝ᅠ ֺ 藔 @Shapegemes ᅠ⏝⏝ᅠ ֺ 藔 @Horribble ᅠ⏝⏝ᅠ ֺ 藔 @Hexspurg ᅠ⏝⏝ᅠ ֺ 藔 @teksturr ᅠ⏝⏝ᅠ ֺ 藔 @SYMBOLH ᅠ⏝⏝ᅠ ֺ 藔 @KIAATCHI ᅠ⏝⏝ᅠ ֺ 藔 @louriette

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

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

“Archive milik @Ruootong.” (@oSangsang), 2 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/oSangsang.

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.