Telegram RegisterThe public register of Telegram
Telegram profile photo for 一

Channel

一

@Runisy8

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

78subscribers

+15 since we began measuring on 5 September 2026

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

Register entry

Telegram ID-1003317304068
TypeChannel
Username@Runisy8
Created24 November 2025 — measured — dated from the channel’s first post
First recorded5 September 2026
Last confirmed live12 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/Runisy8

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 1 October 2026 and assigned it the closest of 31 fixed categories, at 40% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

637870.55 September 2026 — 63 subscribers5 September 2026 — 63 subscribers8 September 2026 — 72 subscribers16 September 2026 — 75 subscribers1 October 2026 — 77 subscribers12 October 2026 — 78 subscribers5 September 202612 October 2026
6 measurements spanning 37 days, net +15. 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 61–80 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 08:5978+1
1 Oct 2026, 10:1577+2
16 Sept 2026, 20:5675+3
8 Sept 2026, 11:3672+9
5 Sept 2026, 17:2363no change
5 Sept 2026, 16:4763first reading

Engagement

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

Recent posts

24 Aug 2026, 18:55 UTC172 viewsread 5 September 2026

滴滴已经停掉了别问了还想做打车可以来找我报公网打车满5条收费保真不保漏可担保可以保证独家目前不做市场120u目前不包线

17 Aug 2026, 08:51 UTC645 viewsread 5 September 2026

独家源头业务 携程旅行订单😎😎😎😎 包含订单信息:历史行程轨迹/开房/机票/打车 等提供 三要素+人脸 没订单收15u 登上不接受扯皮 回单时间1-3天 随意埋雷 随意埋雷 随意埋雷 同行代理找我拿价 老合作伙伴拿底价

22 Jun 2026, 12:36 UTC383 viewsread 5 September 2026

车险名下车 🫡👌 实时无遗漏 对比市场车管所 无大档/小档 可出 车辆详情/车险详情/名下车牌 车辆必须要交强险,所以名下有车必出 保真无遗漏 空给图收费 秒/当天回 急单名下车的优选 报单格式 二要素+人脸

21 Jun 2026, 10:58 UTC308 viewsread 5 September 2026

过段时间开工恢复没跑该退的预存全退了滴滴出行过两天设备到了恢复市面两种版本都能做

27 Apr 2026, 15:37 UTC658 viewsread 5 September 2026
File

滴滴出行记录 🫡😉👌 无遗漏版本👌😉😉👌 注册至今所有打车记录公网直出 报单提供 三要素+人脸 文件回单:一年内打车记录 原先所有低价垃圾滴滴出行已被提交死透目前只有我一家能多条假一赔万支持一切打假 随便埋雷 源头直出 同行 代理找我拿价 联系方式:

4 Apr 2026, 05:57 UTC695 viewsread 5 September 2026

再说一万遍!老子本人直出 真正意义上的源头0手并不是什么傻逼代理

Showing the 12 most recent of 17 posts we hold for @Runisy8. 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 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“一” (@Runisy8), 78 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/Runisy8.

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.