Telegram RegisterThe public register of Telegram
Telegram profile photo for 别看

Channel

别看

@kurisu777

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

36subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002159985946
TypeChannel
Username@kurisu777
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/kurisu777

Growth

3537368 August 2026 — 35 subscribers10 August 2026 — 35 subscribers16 August 2026 — 36 subscribers31 August 2026 — 37 subscribers18 September 2026 — 36 subscribers8 August 202618 September 2026
5 measurements spanning 42 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 35–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 17:5536-1
31 Aug 2026, 05:2537+1
16 Aug 2026, 17:1436+1
10 Aug 2026, 23:4635no change
8 Aug 2026, 02:1635first reading

Engagement

20 posts held, back to 3 March 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 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1h 00m
Average length
30m 23s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

10 Aug 2026, 14:28 UTC2 viewsread 10 August 2026

Blog把vps测试独立出来了，不再作为正文发布 nah.ee/vps

21 Jun 2026, 18:07 UTC84 viewsread 10 August 2026
Forwarded from @hltvtelegramPhoto

🇸🇦 Falcons win their first Major trophy in Cologne

16 Jun 2026, 10:23 UTC118 viewsread 10 August 2026

🍌BOT更新🍌 1️⃣.支持群组使用bot 2️⃣.新增用户/群组周期报表：支持月报、年报、手动查看 报告使用富文本，请更新到最新版本的telegram查看 /reportsettings - 月报年报默认开启，群组中默认关闭 /myreport - 本月 /myreport week - 近 7 天 /myreport lastmonth - 上月 /myreport year - 今年 /myreport lastyear - 去年 （没有回填旧数据，统计从前几天开始的） 3️⃣.新增主播开播历史：支持按时间/时长排序，命令 /history 4️⃣.修了一些bug 有问题请在评论区反馈 #更新

26 May 2026, 21:24 UTC92 viewsread 10 August 2026

🍌BOT更新🍌 1️⃣.不再支持微博平台，因为没微博号没cookie 2️⃣.小红书风控太几把严了😡，没有国内代理也没号，暂时上了两家宽，只能最低限度的支持，不保证可用 3️⃣.快手现已恢复 4️⃣.新增discord开播提醒频道，有私信和频道两种通知方式，详见频道内说明 5️⃣.修正默认提醒逻辑 #更新

9 May 2026, 08:31 UTC109 viewsread 10 August 2026

https://discord.gg/eaXEECWKCc 整了个dc的，但是dc比较复杂，大概也许应该很大可能有挺多bug

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

HLTV | Counter-Strike News
@hltvtelegram · 25,9611 post

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.

Acero1a
@Acero1a · 7381 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. The line below cites the subscriber count as measured 18 September 2026 — this entry's latest reading, not the date you are reading this.

“别看” (@kurisu777), 36 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/kurisu777.

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.